Sources & Attribution — three lenses, one defensible row per channel

Why three lenses (not one)

Every paid-acquisition team has had this week. You open the platform's dashboard. ROAS reads 4x. You open your pixel-side analytics. ROAS reads 2x. You open Shopify's Marketing Reports. Channel revenue says something else again. Three numbers. Three different stories. Most analytics tools resolve this by picking one number and calling it canonical — and if the operator doesn't trust it, that's the operator's problem.

Admaxxer's premise is the opposite: render all three side by side, per row, with the gap explicitly auditable. The pixel lens is conservative (deterministic UTM clicks only — the number your accountant will trust). The Shopify customer-journey lens is post-checkout truth (the version Shopify itself credited the channel for). The platform-reported lens is what the platform's optimizer is using (includes view-through and modeling — inflated, but the number you must use for in-platform pacing). All three are correct in their own coordinate system. None agrees with the other two. The gap is the most useful signal — and Admaxxer is the only DTC tool at the $9/month price point that surfaces every gap with a plain-English Why drawer.

The three lenses

Each lens reads a different source of truth and is correct in its own coordinate system. The drill-down lets you toggle between them at the top of the table — same channel, same campaign, same adset, same ad row, just a different lens applied per cell.

The All synthesis lens

The All lens picks best-of-three per cell:

• Spend — always from platform (only source that has it).
• Attributed revenue — Shopify journey when momentsCount > 0 and journey_status='ready', else pixel when pixel_revenue > 0, else platform-reported.
• Orders / conversions — Shopify journey when ready, else pixel, else platform.
• CTR / CPC / CPM / CPA — derived from the above.

Each All cell renders with a small provenance chip (Sho / Pix / Plt) so you can see at a glance which lens won. The Why drawer (next section) shows the per-cell decision tree.

The All lens is the default for first-time users; you can change the workspace-wide default via Settings → Defaults. Pixel-only workspaces see the All lens collapse to best-of-two (Pixel + Platform); the page never breaks.

True ROAS — the column nobody else shows

True ROAS = Shopify-attributed revenue ÷ ad spend per cell. It's the column nothing else in the merchant's stack can compute:

• Shopify's own admin doesn't ingest ad spend, so it can't divide by it. Shopify Marketing Reports show channel revenue but never channel ROAS.
• Meta / Google / TikTok dashboards divide their own revenue (platform-reported, view-through-inflated, model-padded) by their own spend. Their ROAS is by construction higher than reality.
• Triple Whale + Northbeam compute a similar number (TW calls it Pixel ROAS or Sonar ROAS, NB calls it Probabilistic ROAS), but both gate it behind a $129/month minimum (TW Sonar) or a $1k+/month enterprise quote (NB).

Admaxxer's True ROAS column ships on AD_STARTER ($9/month), no extra connection charge. The math is simple — Shopify-attributed revenue divided by platform spend, per (channel, campaign, adset, ad), with FULL OUTER JOIN so a campaign that exists in only one source still shows up. The join key is marketing_event_remote_id (Shopify's ID for the platform campaign), with fallback to a normalized UTM tuple when the platform doesn't surface a remote ID.

The Why drawer — auditable per-cell reasoning

Click any cell in the drill-down and the Why drawer slides over with three rows:

1. Pixel saw — count of pixel-attributed conversions or revenue with the active attribution model applied (e.g. "Pixel saw $4,210 via time-decay H=7d on the visitor's UTM-tagged path").
2. Shopify journey credited — Shopify-resolved attributed revenue and the moments-array source (e.g. "Shopify credited $5,830 via UTM source=facebook campaign=ww-prospecting-v3").
3. Platform reported — what the platform's own attribution graph claims (e.g. "Meta reported $7,210 via 7-day-click + 1-day-view including modeled conversions").

Plus a fourth row when you're on the All lens: which lens won the synthesis and why ("Sho — momentsCount > 0 and journey_status='ready'"). Plus a pre-computed plain-English reasoning summary for the row's gap ("Platform claims much more than Shopify journey — likely view-through + modeling" / "High direct/untagged share — likely UTM hygiene issue" / "Within 10% — reconciliation clean").

Backfill + first-run delay (~24h)

When a workspace connects Shopify, Admaxxer enqueues a BullMQ backfill worker that walks the last 90 days of orders sequentially per shop using the existing read_orders access scope (the same scope that gates Order.customerJourneySummary per Shopify's GraphQL reference). Shopify Admin API rate limits are 2 req/s with a 40-call leaky bucket — concurrency >1 risks throttling, so the worker stays at concurrency=1 per shop. For a high-volume shop (5,000 orders/day × 90 days), that's ~1,800 GraphQL pages × ~1.5s wall-clock per page = ~45 minutes minimum, but the worker is concurrency-1 across the whole worker pool so a queue of 50 backfills bottoms out at ~24h.

The drill-down shows a Backfilling X% chip on the Shopify column header until the worker reports complete. Incremental updates flow through the existing Shopify webhook handler (orders/create + orders/updated); no additional cron is required after the initial backfill.

Why no extra Shopify scope is needed

Order.customerJourneySummary is gated by the existing read_orders access scope per Shopify's GraphQL reference. Admaxxer requests read_orders on every install (it is also what powers revenue, refunds, AOV, and returns elsewhere in the dashboard), so the customer-journey lens lights up the moment the 90-day backfill finishes — no merchant action, no re-authorization, no “App is requesting new permissions” dialog.

For the avoidance of doubt (GL#421, 2026-05-07): there is no read_customer_journeys scope in Shopify's canonical access-scopes table. If you have seen that name elsewhere — including in earlier drafts of this very page that promised a “Reconnect Shopify CTA” — it was a misreading of the field name; the actual scope-gate on this field has always been read_orders, and existing installs already have it.

Known limits

• 30-day Shopify journey window cap. Shopify only retains the moments array for 30 days post-order. Older orders return customerJourneySummary { momentsCount: 0, ready: true, moments: [] }. The drill-down's date-picker honors this — selecting a window >30 days back disables the Shopify lens with an inline tooltip.
• momentsCount nullable while Shopify processes. First ~10 minutes after order creation, journey_status='processing' and the moments array is empty. The pipe filters these rows out of the Shopify lens; the All lens falls back to Pixel for the affected cells.
• scope_missing sentinel row (legacy code path). The pipe still defends the scope_missing case for historical reasons, but it is effectively dead code per GL#421 — the journey query is gated by read_orders (granted on every install), so the sentinel will not fire in production. See “Why no extra Shopify scope is needed” above.
• Time-decay / position-based / Markov fall through to Pixel on the All lens. Shopify's moments array doesn't include touch timestamps with sufficient precision. The Why drawer explains the fallback.
• marketing_event_remote_id not always present. Platforms that don't expose a remote campaign ID fall back to a normalized UTM tuple for the join key.

Compared to alternatives

Admaxxer's 3-lens drill-down ships on every paid plan starting at $9/month. The closest equivalents either gate the post-checkout truth lens behind a $129+/month add-on, refuse to compute True ROAS, or limit the drill-down depth.

FAQ

What's the difference between the Pixel lens and the Shopify customer-journey lens?

Pixel is what Admaxxer's first-party pixel saw deterministically — UTM-driven click attribution, conservative, the most defensible number. Shopify customer-journey is what Shopify itself stitched into the order's post-checkout journey graph via the Order.customerJourneySummary GraphQL field — includes UTM-less server-side touches Shopify resolved (Shop Pay autofill, Shopify Audiences network, signed-in customer device-stitch). They will disagree on most rows; the Why drawer explains the gap per row. Pixel is the conservative truth; Shopify is the post-checkout truth your bookkeeper trusts.

What is True ROAS and how is it different from the ROAS Meta shows me?

True ROAS = Shopify-attributed revenue ÷ ad spend per cell. Meta's ROAS uses Meta's own revenue (platform-reported, view-through-inflated, model-padded) divided by Meta's own spend, which is by construction higher than reality. Shopify can't compute True ROAS because Shopify doesn't ingest ad spend — Shopify Marketing Reports show channel revenue but never channel ROAS. Admaxxer's True ROAS column ships on AD_STARTER ($9/mo) — the same number Triple Whale gates behind their $129+/mo Sonar add-on and Northbeam gates behind a $1k+/mo enterprise quote.

Why does the Shopify lens show empty cells right after I get an order?

Shopify's customerJourneySummary.ready field is false for the first ~10 minutes after order creation while Shopify computes the journey graph asynchronously. During this window momentsCount is NULL and the moments array is empty. The drill-down filters these rows out of the Shopify lens with WHERE journey_status='ready' and the All lens falls back to Pixel for the affected cells. The Shopify column lights up within 10 minutes.

Do I need to re-authorize Shopify or grant a new scope to enable the customer-journey lens?

No. Order.customerJourneySummary is gated by the read_orders access scope, which Admaxxer requests on every install. Shopify's GraphQL reference at https://shopify.dev/docs/api/admin-graphql/latest/objects/CustomerJourneySummary states the field requires read_orders or read_marketing_orders — there is no separate journey-specific scope in Shopify's canonical access-scopes table. Your existing connection already has the access required. Once the 90-day backfill worker runs (queue capacity-dependent, typically within ~24h of connection or a fresh deploy), the Shopify lens populates automatically — no merchant action needed.

How does the All lens decide which lens wins per cell?

Spend always from platform (only source that has it). Attributed revenue prefers Shopify journey when momentsCount > 0 and journey_status='ready', else falls back to pixel when pixel_revenue > 0, else falls back to platform-reported. Orders / conversions same priority. CTR / CPC / CPM / CPA derived from the above. Each cell gets a provenance chip (Sho / Pix / Plt) so you can see at a glance which lens won. The Why drawer expands the per-cell decision tree in plain English.

Does the drill-down support all 7 attribution models?

Pixel lens supports all 7 (last-click, first-click, linear-all, linear-paid, time-decay H=7d, position-based 40/20/40, Markov-chain). Shopify lens supports last-click, first-click, linear-all, and linear-paid (filtered to paid moments) — Shopify's moments array doesn't include touch timestamps with sufficient precision for time-decay, and the moments count rarely exceeds 3 so position-based and Markov are mathematically meaningless on this lens. Platform lens uses each platform's own model (Meta default 7d-click-1d-view, Google default last-click). The All lens delegates to whichever lens supports the active model — if you pick time-decay, All uses Pixel for that cell and the Why drawer explains.

Why is my drill-down slow on the first load?

The pipe runs FULL OUTER JOIN across three sources at the (channel, campaign_id, adset_id, ad_id) grain — for a workspace with 500+ campaigns × 5+ adsets × 5+ ads × 90 days, that's ~1.1M rows pre-aggregation. The Redis stale-while-revalidate cache layer absorbs the cost — first hit ~3-5s, subsequent hits ~80ms. The Refresh button triggers a forced re-fetch (throttled to 1 click / 10s).

Can I use the drill-down without connecting Shopify?

Yes. The page is source-additive — a pixel-only workspace sees the Pixel and Platform lenses (Shopify column hidden), the All lens collapses to best-of-two, and the page never breaks. Connecting Shopify unlocks the third lens and the True ROAS column on the same UI; nothing else changes. This is the same source-additive principle the rest of Admaxxer follows: 1 source = useful, more sources = better fidelity, missing sources = chip not break.

Related

• /marketing-acquisition — the page where the drill-down lives alongside the unified Sources & Attribution table.
• /dashboard/analytics — the Attribution tab inside AdvancedSection mounts the same drill-down.
• /integrations/shopify — connect Shopify to unlock the customer-journey lens and the True ROAS column.
• Documentation hub — back to the index of all Admaxxer docs.
• Attribution Models — the 7-model formula catalog and the original Reconciliation Panel that this drill-down extends.
• Marketing Acquisition deep-dive — the broader showcase of the /marketing-acquisition surface.
• UTM best practices — fix the "high direct/untagged share" reasoning by tagging your paid campaigns correctly.
• /pricing — every plan from AD_STARTER ($9/mo) up includes the 3-lens drill-down and True ROAS.