Hybrid tracking

Your pixel sees the journey. Only the order proves the sale.

Tracyn runs both. The browser pixel you already have keeps doing what only a browser can, and a second copy of every purchase is read straight from your Shopify order, server to server. Both carry the same event ID, so Meta, Google Ads and TikTok count one conversion — the one that actually happened.

Start your free 14 days See the live demo
Purchases sent with full customer identity
95%
Up from about half. The reference travels on the Shopify order, so identity is resolved server-side rather than read from browser storage Safari has already cleared.
Time to first event
5 min
Install, approve scopes, connect platforms. No developer, no theme edits.
Attribution models per order
6
Last click, first click, linear, time decay, reversed time decay and U-shape, each sent as its own event.
Ad platforms live
3
Meta, Google Ads and TikTok, each through its own server-side API. Klaviyo in development.

Why not one or the other

Choosing a single source is choosing a blind spot.

Browser against server is sold as a choice of tool. It is a choice of what you are willing to lose — and the two lose opposite things, which is the whole reason the pair works.

Browser only

Rich data, unreliable delivery.

  • The script sits on a domain that is on every blocklist. uBlock, Brave and AdGuard drop it before it runs.
  • Safari and iOS cap script-written cookies at seven days, often twenty-four hours. Returning buyers look brand new.
  • It is fire-and-forget. A closed tab, a dead connection or a slow theme loses the event with no error and no retry.
  • What is missing is not noise: it is purchases, and your bidding model learns from the ones that survived.

Server only

Reliable delivery, thinner data.

  • The click that started it never touches your server. fbclid, gclid and ttclid arrive in the browser, at the landing page.
  • The identifiers Meta scores match quality on are browser cookies. No browser, no _fbp and no _fbc.
  • There is no server-side version of a customer browsing. Product views and add-to-carts simply do not exist.
  • Conversions arrive complete and anonymous, which is exactly the shape that scores badly on every platform.

Hybrid keeps the browser’s detail and the server’s certainty, and pays for neither with the other.

On the wire

What each half actually carries.

Not a diagram of arrows. These are the fields that leave your store, and which of the two sources is the only one that can produce them.

From the browser

_fbp, _fbc
Meta’s browser identifiers, read from cookies on your own storefront. They are a large part of how Meta scores a match.
gclid, gbraid, wbraid, ttclid
The click IDs the ad platform stamps on the landing URL. Captured at the visit and held against the session.
event_source_url, user agent
Page context. Small fields, and among the ones that decide whether a conversion is matched to a person or discarded.
Product Viewed, Product Added, Checkout Started
Everything before the purchase, under the names Tracyn puts on the wire. The funnel platforms optimise against exists only in the browser.

From the order

value, currency
Read from the Shopify order itself — the amount that was actually charged, not what a page script inferred from the DOM.
sha256(email), sha256(phone)
Customer identifiers from the order, hashed before they leave. Plain-text contact data is never sent to an ad platform.
orderId
Your Shopify order ID, sent as the conversion’s order ID — the same key gtag spells transaction_id, and what Google Ads deduplicates against.
contents, num_items
The line items exactly as the order recorded them: products, quantities and prices, which is what catalogue-level optimisation runs on.
consent verdict
Your storefront banner’s verdict rides along with the event and is translated into each platform’s restricted-processing flag before the send.

Deduplication

One identifier is what makes running both safe.

Point two sources at one ad account and you normally double-count every purchase: reported revenue inflates and the bidding model optimises against a number that never happened. Tracyn stamps both copies with the same identifier, and each platform collapses them.

Meta
event_id · Conversions API
Both copies of the purchase carry the same event_id and the same event name, so Meta keeps one and discards the duplicate.
Google Ads
orderId · Enhanced Conversions
The Shopify order ID goes up as the conversion’s order ID — the key Google already deduplicates web conversions on.
TikTok
event_id · Events API
Same identifier on both copies. TikTok merges them into the single conversion the campaign gets credited with.

And when the browser copy never arrives — blocked, tab closed, connection dropped — the server copy simply becomes the conversion. Nothing is counted twice, and nothing is missing.

End to end

One purchase, both paths.

  1. 01

    Click

    A visitor arrives from an ad. The landing URL carries the platform’s click ID; the pixel records it against the session before anything else happens.

  2. 02

    Browse

    Product views and add-to-carts leave the browser as usual, carrying the identifiers only a browser holds.

  3. 03

    Checkout

    The customer buys. The browser copy of the purchase fires — assuming the tab is still open and nothing blocked it.

  4. 04

    Order

    Shopify tells Tracyn, server to server. This is the copy no ad-blocker, closed tab or cookie policy can reach.

  5. 05

    Merge

    The consent verdict is attached, the click ID from step one is stitched to the order, and both copies go out under one event ID. Google Ads sends are held in a durable outbox and retried until Google accepts them.

The honest part

What hybrid tracking does not do.

Four things you would otherwise find out in week one. Every vendor in this category has the same four limits; not all of them print them.

  • It does not unblock the browser copy

    A blocker still drops it, and sometimes does. The sale survives because the order is the source — but the browser-only signals for that particular visitor are gone, and no vendor can tell you otherwise.

  • It does not decide consent for you

    Your banner does. Tracyn carries that verdict to every platform as its own restricted-processing flag — data_processing_options at Meta, CONSENT_DENIED at Google, limited_data_use at TikTok — so a refusal follows the event instead of being quietly forgotten between systems.

  • It does not move bidding overnight

    The platforms need days of clean conversions before their models retrain and spend shifts. Day one is when the data gets correct, not when the ROAS does.

  • It does not replace what you have

    Your pixel, your GA4 and your tag manager keep running untouched. Installing Tracyn cannot break reporting it never took over.

Before you install

What media buyers ask about hybrid.

Will running two sources double-count my revenue?

No — that is the specific problem the shared event ID solves. Both copies of a purchase carry the same identifier, so Meta and TikTok collapse them into one conversion and Google Ads deduplicates on the order ID. Bolting a second source onto a pixel without that is what inflates reported revenue, and it is the first thing to check with any vendor selling server-side tracking.

Do I have to remove my Meta pixel, GA4 or tag manager?

No, and you should not. The browser pixel is half of the pair — it is the only thing that can see on-site behaviour and the browser identifiers Meta scores against. Tracyn runs beside it and shares an event ID with it. Nothing in your current setup is removed or rewritten.

What happens if a customer blocks the pixel completely?

The purchase is still captured, because it is read from your Shopify order rather than from the page. What is lost for that visitor is the browser-side context — the on-site events and the browser identifiers — so the conversion is forwarded with the order data and whatever click ID was recorded when they landed.

Does the server-side copy carry customer data in plain text?

No. Email and phone from the order are SHA-256 hashed before anything is sent, which is what the platforms expect and all they can use. Your storefront banner’s consent verdict is attached to the event and translated into each platform’s restricted-processing flag, EU traffic is processed in the EU, and you get a data processing agreement.

How long does hybrid tracking take to set up?

Open the install link we send you and approve the scopes; capture starts immediately. Each ad platform is one OAuth click. No theme edits, no container changes, no developer.

Keep reading

Ready to scale on numbers you can trust?

Run Tracyn free for 14 days. We do not charge at all in that window, so if your tracked revenue and match quality have not moved, you walk away having paid nothing.

  • Five-minute setup, no developer
  • Tracking live the same day
  • No contract, cancel anytime
Start your free 14 days See the live demo