RadiusRankPlatform

Verified product capability

AI Referral and Visitor Measurement

RadiusRank does not ship a separate website visitor tracker. AI-referred sessions should be measured in a consented analytics system or server logs, then joined to RadiusRank answer observations without pretending that every influenced visit is attributable.

Updated 5 minute evidence brief

Scope and boundaryGoogle Analytics documents traffic acquisition as session-scoped and identifies referral domains when that information is present. Missing referrers can appear as direct traffic.

Data as of August 14, 2026. Next scheduled review: September 14, 2026.

0native visitor trackers claimed
2recommended evidence sources
4metrics in the minimum view

What the evidence supports

  1. Referral sessions are observable when a click carries source information; answer influence without a click is not.
  2. Session source, landing page, engaged session and conversion are a safer minimum than pageviews alone.
  3. Direct traffic should not be relabeled as AI traffic based on timing or intuition.

What is available, assisted and outside the product

This boundary table is based on the shipped product specification and the public offer. It is designed to prevent a recommendation from being mistaken for automation.

LayerRadiusRank doesRadiusRank does not
AnalyticsUse authorized GA4 acquisition data by session source and landing pageInstall a second tracker through RadiusRank
Server evidenceUse request logs when available to validate landing URLs and referrersIdentify a human's prior chat exposure
AttributionReport observable referrals plus an explicitly modeled influence rangeConvert all direct traffic into claimed AI traffic

Create a minimum viable AI referral view

01

Segment known sources

Group documented AI referrer domains while retaining the raw source values.

02

Inspect landing pages

Compare engaged sessions and conversions by the cited or linked destination page.

03

Label uncertainty

Keep attributable sessions separate from a modeled influence scenario.

Methodology

  1. Checked the current public RadiusRank offer against the authenticated product specification on August 14, 2026.
  2. Classified each capability as available in product, recommendation only, service methodology or not native.
  3. Preserved the August 12 capability snapshot and published the changed subscription terms in a separate August 14 offer record.

Limitations

  • Some assistants do not expose a clickable source for every answer.
  • Browser, app and privacy behavior can remove referral context.
  • No visitor-level identity should be inferred from RadiusRank answer observations.

Questions

Is ai referral and visitor measurement fully automated?

Only the functions marked available in product are automated. Recommendations, implementation and external-system measurement require a person or an authorized integration.

Does RadiusRank change a live website automatically?

No. RadiusRank diagnoses and produces prioritized outputs, but it does not publish to a CMS or change a production site without a separate implementation workflow.

Sources and data

Found a changed price, product limit or source? Email team@radiusrank.com with the official URL. We preserve the snapshot date instead of silently rewriting historical data.

Start with the evidence

Start with an inspectable baseline.

The free diagnostic shows the questions, public technical issues and citation-readiness gaps before you start a subscription or scoped service.

Run the free diagnostic