Skip to main content
Interactive demo

Follow one ad click through SignalBridge

A 79-second walk through what happens to a single conversion: from the click on an ad, through your site and the SignalBridge edge, to the ad platforms and back into the learning that finds your next customers. Then switch on an ad blocker, a bot, denied consent or a platform outage and watch where the journey changes.

The interactive demo

The eight steps in plain words

Everything in the demo is taken from how the product behaves today. Each statement carries one of three labels, so you can tell what is running for every account from what needs setup, and from what is only a plan.

  • Shipped Running for every account
  • If configured Needs your setup first
  • Planned Designed, not built

  1. 1 · The click

    An ad is clicked. A signal is born.

    Before anything on your site runs, the ad platform stamps the landing URL with a click ID, the strongest proof of which ad produced this visit.

    • ShippedPlatform click IDs (gclid, fbclid, ttclid, msclkid, tblci and more) are captured from the URL.
    • ShippedA click ID outranks UTM tags when classifying the channel, because UTMs can be misconfigured.
    • If configuredSmart Tracking Links can mint an sb_click_id and record clicks that never convert.

  2. 2 · The visit

    The pixel wakes up, first-party from the first byte.

    pixel.js resolves consent and writes a few first-party identity cookies. A third-party pixel that an ad blocker stops is silent; this path is your own domain.

    • ShippedA server-set visitor ID lasts one year; first-touch lasts one year; click IDs 30 days; the touch log 90 days.
    • ShippedIf Meta's script is blocked and never sets _fbp, SignalBridge generates one in Meta's own format.
    • If configuredEvents travel to your own domain through a same-origin proxy, or a custom CNAME you configure.

  3. 3 · The journey

    Behaviour becomes events. The visitor becomes known.

    Page views, product views, carts, checkout and purchase are detected automatically. Identity a visitor volunteers in a form is carried to the thank-you page.

    • ShippedFifteen event types are detected automatically, plus any custom events you define.
    • ShippedEmail and phone typed into a form are kept for 30 minutes so the next page can attach them.
    • Shippedfbq, gtag and ttq calls are wrapped with one shared event ID so browser and server events de-duplicate.

  4. 4 · The edge gate

    Every event meets the gate.

    At the Cloudflare edge each event is validated, authenticated, consent-checked and screened. Bots and previews are filtered, visibly, with a reason.

    • ShippedPublic traffic must match a write key and an allowed origin; server traffic is bound by an HMAC signature.
    • ShippedIf marketing consent is denied, click IDs, UTMs and fbp/fbc are stripped and cached attribution is deleted.
    • ShippedFiltered events return HTTP 200 with a reason, and the dashboard shows what was filtered and why.
    • If configuredTraffic Quality exclusion can keep high-confidence fraud away from ad platforms.

  5. 5 · Enrichment

    A thin browser payload becomes a rich conversion.

    The Worker restores the click ID from the last 30 days, normalises and hashes identity, adds network context, validates value and currency, and labels the customer.

    • ShippedClick IDs and UTMs are restored from a 30-day memory keyed by visitor, then by IP.
    • ShippedEmail, phone, name and location are normalised to each platform's spec, then SHA-256 hashed.
    • ShippedCurrency is never guessed from a domain. With no authoritative currency, Meta receives no value rather than a wrong one.
    • If configuredNew versus returning customer comes from Shopify order history.

  6. 6 · Durable delivery

    Sealed first. Then delivered everywhere, in parallel.

    One atomic write stores the event and every provider's request. Each platform is then called through its official server API, and retried with backoff until it accepts.

    • ShippedThe event and all provider requests are accepted in one transaction; a retried duplicate returns duplicate:true.
    • ShippedRetries back off from 30 seconds with jitter (Meta caps at 6 hours, Google at 12). A bad token flags the integration for re-authorisation.
    • ShippedGreen appears only when the provider accepts. Dispatched is not accepted, and accepted is not attributed.
    • If configuredMicrosoft Ads and Taboola are sent only when the visitor has an msclkid or tblci.

  7. 7 · The learning loop

    Better signal in. Better customers out.

    Ad platforms optimise toward people who resemble the conversions they see. Complete, de-duplicated, valued conversions give them more and better examples, and keep fake traffic out.

    • ShippedSignalBridge builds no audiences. The platforms find similar customers; SignalBridge improves what they learn from.
    • ShippedValidated value and currency reach Meta and Google, the input that value-based bidding learns from.
    • If configuredWith Shopify, a new-customer flag and refund adjustments reach the platforms. With Klaviyo, lifecycle flows drive repeat purchase.
    • PlannedA merchant subscription-revenue ledger and renewal forwarding are designed, not built.

  8. 8 · The control room

    Every claim is checkable.

    Live events, per-platform delivery health, Meta match quality, reclaimed revenue with its evidence, and journeys. Fix a cause and the better signal flows back into the platforms.

    • ShippedAn event counts as reclaimed only with an accepted server delivery and an observed browser failure.
    • ShippedPer-platform delivery, retries, dead letters and re-authorisation needs are visible.
    • ShippedJourneys, assisted conversions and model comparison show which touches helped a purchase.

What the demo does not claim

  • SignalBridge builds no audiences. The ad platforms find similar customers; SignalBridge improves the conversions they learn from.
  • Green means a platform accepted the event. It does not mean the platform has attributed the sale to a campaign.
  • The dashboard numbers in the demo are sample data, not a promise of results.
  • Several steps need setup first: a custom domain, Smart Tracking Links, Shopify, Klaviyo, and Microsoft or Taboola click IDs.
  • Renewal forwarding and a subscription-revenue ledger are designed but not built, and the demo marks them as planned.

For the mechanics behind a single step, read about server-side tracking, bot filtering and reclaimed traffic insights.

See it on your own store

Install the pixel, connect your ad platforms, and watch your own events move through the same steps in the dashboard.