Attribution model

Cosmic Insights attributes every pageview to:

1. A traffic source (UTM params, referrer, or "direct")
2. A Cosmic object (the post, page, or product the user landed on)

Source attribution always works. Object attribution depends on which signals reach the tracker.

Source attribution

The tracker derives source/medium/campaign in this order:

1. UTM params (utm_source, utm_medium, utm_campaign) on the current URL.
2. Referrer host: known search hosts (google, bing, yahoo, duckduckgo, baidu, yandex) get medium="organic"; everything else gets medium="referral".
3. No referrer (or same-host referrer) → empty source/medium, which the dashboard renders as "direct".

Object attribution

Three layers, in order of precedence:

1. <script> tag attributes (default for every event on the page). Set data-bucket, etc. on the snippet tag.
2. <meta name="cosmic-context"> tag (manual, recommended for static / server-rendered pages). One JSON tag per page covers object_id, object_type, and any other promotable key.
3. Per-event call (highest priority on a single event). Pass object_id directly to cosmicInsights('view', { object_id: '...' }).

<meta name="cosmic-context"
      content='{"object_id":"OBJ_ID","object_type":"posts"}'>

Cosmic AI Build also uploads a routes.json map (path -> object_id) at deploy time so the dashboard can resolve per-object views for paths you didn't tag manually. Server-side resolution against that map at ingest time is on the v1.5 roadmap; for v1, render the meta tag (or pass object_id per event) on any page where you want object attribution.

Precedence summary

For object fields, the resolved value is:

script tag attrs  ->  cosmic-context meta tag  ->  per-event props

(low to high.)

Where it shows up in the dashboard

• Overview: visitors, pageviews, sessions, and bounce rate as headline tiles, each clickable to drive a Vercel-style time-series chart. Period-over-period deltas on every tile.
• Pages: per-path rollup.
• Content: per-Cosmic-object rollup, sorted by views.
• Events: raw event explorer with all promoted fields and event_props.
• Custom events: per-event-name rollup, including conversions and revenue.
• Sources: source / medium / campaign rollup.
• Per-object Performance card: appears on every object detail page in the Cosmic dashboard.

Note on per-author analytics: rolling up traffic by the human, AI agent, or automation that authored each object is not in the initial release. Add object_id to your tracking now and per-author views will work automatically when they ship in a later release; you do not need to render dashboard user IDs into your page source.