Demo: Edge-to-Activation — Attribution Gap & Signal Recovery

Purpose: How we show this service — run steps, key features, story flow, proof.
Notion: Demos database
Service / Offer: Edge-to-Activation — offer.md

Description

This demo shows the gap between what client-side tracking (GA4, Segment, etc.) sees and what actually reaches the site at the Edge. We run Edge capture at the CDN (before the pixel fires) in parallel with the existing stack — we’re adding a fuller data stream, not replacing pixels or server-to-server. We walk through a discrepancy report: traffic and conversions the client layer missed, by source. The prospect sees concrete numbers (e.g. X% of conversions unattributed) and how Edge data flows into the warehouse and then into their tools (e.g. via Segment or reverse ETL) so they get one source of truth without ripping anything out.

Takeaway (one line for the prospect): You can get 95%+ reporting accuracy before client-side tracking fails — and we prove the gap first with a side-by-side comparison.

When to use

Demo type: [x] Discovery (first call, high-level) · [x] Deep-dive (technical / stakeholder) · [ ] Campaign / webinar (recorded, scripted)
Audience: Head of Marketing, CMO, Head of Growth, VP E‑commerce / Paid Media / Omnichannel; optionally analytics/engineering for technical deep-dive.
Vertical (if relevant): E‑commerce, CPG, B2B SaaS (digital acquisition–driven).
CTA: Schedule Signal Recovery Audit (Phase 0) or send proposal for audit → pilot.

Demo link

URL: [Add stable link when available — e.g. Edge vs. client-layer discrepancy report demo or attribution gap visualization.]

(Campaign and services doc reference “Edge vs. client-layer discrepancy report (demo), attribution gap visualization” — link here when the live demo is published.)

How to run it (presenter steps)

Click-by-click so anyone can run the demo without guessing.

Open discrepancy report or demo dashboard (client vs. Edge view).
Show overall gap: e.g. “Client-side saw X visits/conversions; Edge saw Y — here’s the delta.”
Break down by source/channel: which traffic sources have the largest gap (e.g. paid, social, direct).
Show sample of “recovered” conversions: conversions Edge captured that had no or wrong attribution in the client layer.
Show how Edge data connects to existing tools (GA4, Segment) — bridge, not replace.
Optional: show Level 2 — attribution of specific actions; or Level 3 — link to warehouse/transaction data if that’s in scope.

Key features & what to show/say

Feature	What to show	What to say (or so what)
Edge vs. client comparison	Side-by-side or overlay of client-layer vs. Edge traffic/conversions	”This is the gap you’re making decisions on today — we’re not replacing your stack, we’re showing what’s missing.”
Gap by source	Table or chart of unattributed % by channel/source	”Paid and social often have the biggest gaps — ad blockers, iOS, script failures. Here’s yours.”
Recovered conversions	List or count of conversions Edge attributed that client layer missed	”These conversions happened but your current tools didn’t attribute them — we recovered them at the Edge.”
Identifier bridging	How Edge session/ID maps to _ga, Segment, etc.	”We plug into what you already use — GA4, Segment — so you get one source of truth without ripping anything out.”
No replacement message	Same slide or callout	”Edge is an additional stream — we don’t kill pixels or server-to-server; partners and platforms still need those. We add a fuller picture and plug it into your warehouse and then into Segment or reverse ETL so you get one source of truth.”

Workflow (story for the prospect)

The problem — “You’re judging performance on 70–85% of the picture; 15–30% is invisible to client-side tracking.”
Show the gap — Discrepancy report: client vs. Edge totals, then by source. Make the gap concrete (e.g. 17% unattributed).
Recovered signal — “Here are conversions we see at the Edge that your current stack missed or misattributed.”
How it plugs in — “We connect to GA4, Segment, your warehouse — you keep your tools; we make the data accurate.”
Proof — “With Eden we got to 95% accuracy and recovered ~17% of customers with no prior attribution; they corrected six-figure partner misallocations.”
Close — “Next step: we run a Signal Recovery Audit (about a week) and give you your own discrepancy report — then we can scope the pilot.”

Proof to reference

Metric to call out: “17% attribution recovery” or “95% reporting accuracy” or “six-figure misallocations corrected.”
Case name (if allowed): Eden ($6.2M MRR).
One-liner: “We recovered ~17% of customers that had no attribution before and corrected six-figure partner overpayments.”

Tags (optional)

Service: Edge-to-Activation
Vertical: E‑commerce, CPG, B2B SaaS
Tech / theme: Attribution, signal recovery, edge computing, GA4, Segment

Brainforge Knowledge

Explorer

demo