Skip to main content
TrackingConsulting
Now booking · 2–4 day turnaround

gbraid and wbraid attribution issues · Conversion tracking

Why do gbraid and wbraid break my Google Ads attribution?

gbraid and wbraid are Google click identifiers that arrive in place of gclid on iOS traffic where Apple's privacy rules prevent the usual user-level identifier. They are not drop-in replacements: they identify a group of clicks rather than an individual, they cannot be combined with user-provided data the way gclid can, and capture code that names only gclid ignores them entirely. The result is a growing share of iOS conversions that never get uploaded, which looks like iOS performing badly rather than iOS not being measured. The fix is to capture all three parameters, store whichever arrived, and upload against the right one.

Get my free audit & recovery planQuick question? WhatsApp

✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.

Built in 2–4 daysOne-time fee95% accuracy guaranteed400-day cookie lifetime1st-party server-side

Written guarantee

95%+ conversion accuracy on gbraid and wbraid attribution issues

Measured against your own order records at handover. Miss it and we keep working at no cost until it’s met.

Built on — and certified for — the platforms that matter

Stape

Pro Partner

Meta

Tech Provider

Google

Tag Manager

TikTok

Events API

Microsoft

UET Partner

LinkedIn

CAPI Partner

Pinterest

CAPI Partner

Built on the same partner stack used by enterprise DTC brands.

Ariful Islam — Founder, Tracking Consulting

Meet your consultant

Ariful Islam

Founder · 8+ years in paid media & tracking

Verified earnings

$200K+

earned on Upwork

Top Rated Plus
4.9/5 on Upwork · 300+

Verify the receipts

You work directly with Arif — no SDR, no account manager.

By the numbers

No fake testimonials.Just the math.

70+

Platforms supported

Shopify · Woo · Magento · BigCommerce · 65 more

8+ / 10

Meta EMQ guaranteed

in writing — keep working free until hit

2–4d

Build to live

accurate data flowing within 7 days

$0

Monthly fees, ever

one-time fixed price · you own the stack

400d

Cookie lifetime

max RFC 6265bis allows · 57× Safari ITP

9

Ad channels covered

Meta · Google · TikTok · MS · LI · Pin · Snap · Reddit · X

95%+

Tracking accuracy

verified vs Stripe · GA4 · ad-platform reports

30 min

Free founder call

no SDR · no pitch deck · written remediation plan

Every figure above is either a commitment we put in writing or a countable fact. What your own setup is losing is not on this list, because we haven’t measured it yet — that happens on the call, against your own order records.

Real clients · real videos · real outcomes

Don’t take our word for it. Watch the receipts.

Founders, marketers, and agency owners describing the before-and-after of their gbraid and wbraid attribution issues tracking rebuild — in their own words, on camera.

"Ariful is one of the best tracking experts in the industry. I had previously worked with many other experts in this field and Ariful outperformed everyone else for a better rate, higher quality work, and much better communication. He is clear and honest when it comes to communication, terms, and payment. I'd highly recommend Ariful if you have a big project and need someone you can trust."
Verbatim Upwork review· DTC · Server-side rebuild
"Ariful helped me enormously. I had a bad META pixel issue and he diagnosed it and helped get me back on track. I am not crash hot with technology and he walked me through the process so I understood what he was doing and that I felt confident moving forward. I recommend Ariful, he is quick, professional and knows what he is doing."
Verbatim Upwork review· Meta Pixel · debug
"If you want 100% transparency and communication on the work they are doing to fix your accounts, set up, ect.. this is the guys for you. He was efficient, didn't waste any time, and got the job done quickly. He explained exactly what he was going to fix, why the problems were there, how long it was going to take and how he was going to fix it. He made it very clear and made sure i understood the process. So grateful i found him."
Verbatim Upwork review· Ad accounts · setup
"Ariful did an outstanding job! He was not only quick but also very professional in setting everything up exactly to my satisfaction. His communication throughout the process was clear and timely, and he went the extra mile to ensure all details were handled efficiently. I'm extremely pleased with the results and would highly recommend him for any project. Looking forward to working with him again in the future!"
Verbatim Upwork review· Full tracking setup
"Working with Ari was great. He was efficient, quick, helpful, and patient as we worked through some complicated technical details. I would happily recommend him to anyone looking for technical support with pixels, tracking, and ad builds as he was especially talented in that arena."
Verbatim Upwork review· Pixels · ad builds
"Contacted Ariful to help setup proper tracking for my website. He immediately understood my issue and made some great suggestion on how we could tackle the problem. He was excellent with communicating the steps to resolve the problem and showed a great deal of knowledge in his field. Work was done promptly and he even followed up to make sure everything was working perfectly after the work was done. I would highly recommend hiring him."
Verbatim Upwork review· Site tracking · setup
"Really thorough breakdown of tracking issues on our website, and explaining server side tracking, he was able to resolve the issue and get us back on track. I would highly recommend Ariful for any tracking issues you may be having."
Verbatim Upwork review· Server-side · audit
"Ariful solved my tracking issue in no time with the highest quality work! He is very skilled, and you can trust him to provide the best tracking method for your business. I totally recommend him!"
Verbatim Upwork review· Tracking · fix
"Ari is a true pro, if you need ANYTHING done in regards to tracking — Google Tag Manager, Google Ads, Google Analytics 4, Meta Ads, TikTok Ads, Klaviyo, you name it — he will get it done to standard, and extremely fast. My third time hiring him, I always recommend."
Verbatim Upwork review· GTM · GA4 · Meta Ads · TikTok Ads · Klaviyo
"Arif demonstrated an extraordinary level of skill and expertise in everything related to conversion tracking. He delivered some efficient solutions for us. We will want to keep working with him in future projects. Highly recommended."
Verbatim Upwork review· Conversion tracking
"Ariful was a pleasure to work with. He quickly helped me identify the issues with my Meta Pixel and Google Tag Manager setup and was eager to make the fixes immediately. I appreciated his explanations throughout the process which helped me understand what he was doing and most importantly, why. I look forward to working with him again on future projects!"
Verbatim Upwork review· Meta Pixel · GTM
"Arif was a pleasure to work with and truly is a genius when it comes to tracking. I would never have been able to complete this type of work without him. His passion for his work shines through and you can clearly tell that he is a master of his craft. Not only did he help me with tracking, he helped me optimize my sales funnel so that I will get higher conversions and make more money which will pay for itself many times over. If you're looking for a tracking expert — Do not look any further, Arif is your man!"
Verbatim Upwork review
"Arif did an excellent job implementing server-side tracking for Google Ads, Facebook Ads, and GA4. He demonstrated strong expertise in setting up tracking pixels and ensuring accurate data collection. Arif's attention to detail and proactive communication throughout the project were highly appreciated. He completed the task efficiently and delivered high-quality results."
Verbatim Upwork review· Server-side · Google Ads · Meta · GA4
"Arif demonstrated exceptional skills in implementing server-side tracking for Google Ads conversion in our SaaS product. His expertise in configuring tracking mechanisms and ensuring precise data collection was invaluable. Arif's meticulous attention to detail, proactive communication, and efficient task completion were commendable. The high-quality results he delivered exceeded our expectations."
Verbatim Upwork review· Server-side · SaaS · Google Ads
"Mr. Arif managed our custom conversion very well through Stape.io and GTM. He tracked everything meticulously. His communication and dedication to work are remarkable. I highly recommend him."
Verbatim Upwork review· Stape.io · GTM
"Highly recommended freelancer. I've worked with a lot of tracking professionals and Ariful is one of the best if not the best. He has deep expertise and understanding of what is needed to improve ad conversions, attribution and Facebook event quality score! Hiring him is the best investment you can make for your ads."
Verbatim Upwork review· Attribution · Meta EMQ
The problem

What this looks like when it's happening to you

gbraid and wbraid attribution issues-specific issues
Leak #01

iOS campaigns look far worse than Android

Not because they perform worse, but because a share of their conversions never gets recorded at all.

Leak #02

Offline uploads rejecting rows with no clear reason

Rows uploaded against the wrong identifier type fail, and the error text does not always make the cause obvious.

Leak #03

Identifier coverage that fell over time with no code change

As iOS traffic share grew, the proportion of clicks arriving with gclid shrank.

Architecture

Why your conversion data was wrong in the first place

Fixing this specific fault is worth doing. But it is worth understanding why it happened, because the same underlying weakness produces a different symptom every few months — and the reason your conversion data is wrong is almost never the tag itself.

  1. Step 1

    Your conversion depends on a browser that is being restricted on purpose

    A browser-side tag has to survive the page loading, the visitor staying, the script executing and the request leaving. Every one of those is now contested. The order in your database is certain; the browser event reporting it is not, and that gap is where wrong numbers come from.

  2. Step 2

    Safari caps the cookie your attribution depends on

    Intelligent Tracking Prevention limits cookies written by JavaScript to seven days, whatever expiry you set. Any customer who takes longer than a week to decide comes back as a stranger, so the sale is recorded and credited to nobody. A cookie your own server writes in an HTTP response is not subject to that cap — which is the single largest practical difference between browser-side and first-party server-side tracking.

  3. Step 3

    Ad blockers remove the tag before it can run

    A blocked pixel does not error, retry or warn anyone. The visitor buys, the order lands in your store, and no platform ever hears about it. First-party events sent from your own subdomain aren't filtered the same way, because they are not a third-party request.

  4. Step 4

    Consent banners stop tags, sometimes when they didn't need to

    Where consent is genuinely required, losing the event is correct. What is not correct — and what we find repeatedly on US-majority accounts — is an EU-style prior-consent banner applied to every visitor, discarding conversions no law asked you to discard. A server container enforces the real decision at the container rather than hoping each vendor script honours a flag.

  5. Step 5

    The checkout can end somewhere your tag isn't

    Wallets and hosted payment pages can be abandoned after the money moves. The customer paid; the confirmation page never rendered; the browser event never fired. Sending the purchase from the order record instead means the conversion arrives whether or not anyone came back to your site.

  6. Step 6

    What that adds up to

    Each of these is a separate route to gbraid and wbraid attribution issues, and they compound. First-party server-side tracking doesn't patch them one at a time — it moves the money event off the browser entirely, so the order in your backend is what gets reported. That is why we reconcile against your own order records and put 95%+ accuracy in writing: with the event sourced from the order, the number is checkable rather than hopeful.

Diagnose it honestly

Some of this is supposed to happen

Half the time nothing is broken and the number is being read wrong. Knowing which is which stops you paying to fix something that was never a fault.

Normal — not a fault

  • Working

    Records carry whichever of the three identifiers arrived, with the type stored alongside, and uploads route by type.

  • Broken

    Records carry gclid or nothing. iOS conversions look like they did not happen.

  • Broken but invisible

    Coverage looks acceptable overall because desktop traffic dominates the average, while the iOS segment specifically is close to zero.

Actually broken

  • Capture code written before gbraid and wbraid existed

    The overwhelmingly common cause. The code works, has always worked, and quietly stopped covering a growing share of traffic.

  • A third-party plugin or tag template that only knows gclid

    Plenty of form and CRM integrations still capture one parameter. Check what yours actually reads rather than what its documentation implies.

  • Auto-tagging disabled

    No identifier of any kind arrives. Worth ruling out first because it takes thirty seconds and explains everything at once.

  • Uploads sent with the value in the gclid field regardless of type

    Rows fail and the failure is reported as unmatched rather than as a format problem.

  • Redirects or a landing page framework stripping query parameters

    The parameter arrives and is discarded before anything reads it.

Diagnostic sequence

How we find out why do gbraid and wbraid break my google ads attribution

Always in this order. Each step eliminates a class of cause, so by the last one there is usually a single explanation standing.

  1. 1

    Confirm auto-tagging is on in every Google Ads account

    One setting, and switching it off removes conversion attribution, enhanced conversions and offline import together.

  2. 2

    Pull your last few hundred records and count identifier types

    How many carry gclid, how many gbraid, how many wbraid, how many nothing. That distribution is the whole diagnosis.

  3. 3

    Read the capture code and check which parameter names it reads

    If gbraid and wbraid are not in it, you have found the cause and can stop.

  4. 4

    Compare the identifier distribution against your iOS traffic share

    They should be broadly consistent. A large iOS share with almost no gbraid or wbraid means capture, not traffic.

  5. 5

    Check the upload's failure rows, not its success count

    A file can upload successfully and match nothing. The per-row errors say which.

  6. 6

    Test a live iOS click end to end

    Click an ad from an iPhone, complete a conversion, and follow the identifier through to the record.

Source-of-truth validation

How we prove it's actually fixed

The tag firing again proves the tag fires. These prove the numbers are right.

Source of truthYour own records, counted by identifier type, next to your Google Ads traffic split by device and platform
  • The identifier type distribution measured across your last few hundred conversions, before and after the fix.
  • A live iOS click followed end to end, with the parameter that arrived confirmed on the record and in the upload.
  • Reconciled against your own records, counted by identifier type, next to your google ads traffic split by device and platform for a fully closed window, matched on ID rather than on totals.
  • No record counted twice, checked across the whole window rather than spot-checked.
  • The same check repeated 30 days later, because a fix that holds once and drifts is the harder failure to catch.

Straight talk

When you don't need us for this

Most of these you can do yourself, and we would rather you did.

  • Confirm auto-tagging is enabled in every account. Thirty seconds, and it is a surprisingly common cause.
  • Search your capture code for the string gbraid. If it is not there, you have your answer without any further investigation.
  • Count the identifier types on your last hundred conversions. That single number tells you the size of the problem.

Who this is for

Honest about who we’re a fit for.

We don’t take every project. Here’s how to tell if we’re right for you.

Good fit

You’re a great fit if…

  • You run gbraid and wbraid attribution issues (or are migrating to it)
  • You spend $5K+/month on paid ads (Meta, Google, TikTok, Microsoft, LinkedIn)
  • Your reported ROAS doesn’t match what your bank account is saying
  • You want to own your tracking stack — no monthly SaaS fees forever
  • You have 2–4 days to do this once and never think about it again
Not a fit

Skip us if…

  • You spend less than $500/month on paid ads (browser pixel is fine)
  • You want a SaaS dashboard with monthly fees forever (Triple Whale, Hyros)
  • You need attribution modeling — we fix the data foundation, not multi-touch reports
  • You want a 6-month enterprise consulting engagement (we ship in 4 days)
  • You expect us to manage your ad accounts (we don’t — that’s a different service)

If you’re still unsure,book the call anyway— we’ll tell you straight whether we can help.

Our position

If yourreported ROASdisagrees with your bank account, you don’t have an attribution problem.You have a data foundation problem.No SaaS dashboard fixes that — only a rebuilt 1st-party server-side stack does.

Ariful Islam — Founder
The outcome

What changes once it's fixed

All three identifiers captured

Server-side

gclid, gbraid and wbraid, with whichever arrived stored on the record.

Uploads sent against the correct identifier

8+ EMQ

Each row using the parameter that actually arrived, not a guess.

Honest reporting of what cannot be joined

Deduped

gbraid and wbraid do not identify a person. Enhanced conversions for leads does not apply to them the way it does to gclid, and pretending otherwise produces silent failures.

The full transformation report

Before vs after — built in 2–4 days, accurate data within 7 days

This is what changes structurally, not a promise about your numbers. The figures specific to your account come from the reconciliation we run against your own order records before the build and again after — the two commitments below are the ones we put in writing.

Attribution accuracy

  • Reported conversions vs your order records
    BeforeWhatever today's reconciliation shows — most have never run one
    After95%+ match, guaranteed in writing
  • Where the purchase event comes from
    BeforeThe browser, if it survives the redirect
    AfterYour backend order record
  • Click IDs across redirects and domains
    BeforeCommonly dropped at the first hop
    AfterCaptured at first touch, persisted first-party
  • Server-attributed conversions
    BeforeNone — browser only
    AfterEvery order, sent server-side

Audience quality

  • Meta Event Match Quality
    BeforeWhatever Events Manager shows you today
    After8+ / 10, guaranteed in writing
  • Cookie lifetime in Safari
    Before7 days — ITP's cap on JavaScript-set cookies
    AfterUp to 400 days — the RFC 6265bis maximum
  • Identity sent with a purchase
    BeforeWhatever the browser happened to hold
    AfterEmail, phone, name, city, state, zip, external ID — hashed
  • Lookalike and retargeting seeds
    BeforeBuilt from the conversions that survived
    AfterBuilt from every order in your backend

Bidding performance

  • What bidding optimizes toward
    BeforeThe events that happened not to be blocked
    AfterEvery conversion, including offline outcomes
  • Conversion value
    BeforeOften missing, or a total that doesn't match your revenue
    AfterThe amount actually charged, with currency
  • Refunds and cancellations
    BeforeNever reported back, so ROAS stays inflated
    AfterReversed at every destination
  • Duplicate conversions
    BeforeUndetectable without an order ID
    AfterDeduplicated on a shared event ID

Compliance & ownership

  • Consent behavior under audit
    BeforeUntested — tags commonly fire before consent is set
    AfterVerified: nothing leaves before consent
  • Consent Mode v2 wiring
    BeforeNot configured
    AfterFully wired + verified
  • 3rd-party cookie deprecation ready
    BeforeNo
    AfterYes
  • Data ownership
    BeforeVendor-locked
    After100% yours

Server-side

money events from your backend

8+ / 10

Meta EMQ guaranteed

95%+

tracking accuracy

A typical engagement

The shape of a typical gbraid and wbraid attribution issues rebuild

We’re not going to invent a fake testimonial here. Instead — here’s the realistic pattern of what happens, anonymized but accurate to engagements we ship.

Day 0 — They arrive

A 7-figure gbraid and wbraid attribution issues store spending ~$25K/month on Meta. Reported ROAS shows 4.1× in Ads Manager. Their bookkeeper’s number says 2.6×. The founder doesn’t know which is real, so they keep doubling down on what looks like a winning campaign — except cash flow tells a different story.

Day 1 — Audit

We screen-share. Within 20 minutes we’ve found the leaks: native pixel firing twice on iOS, CAPI dedup using the wrong event_id (Meta is double-counting), GA4 showing 38% (not set), and the Customer Events API never enabled. The 1.5× ROAS gap explains itself.

Day 2–3 — Build

Server-side GTM container goes live on data.theirstore.com. Meta CAPI rebuilt with full advanced matching. Google Enhanced Conversions wired. TikTok Events API turned on. All event_ids deterministic. iOS recovered.

Day 4 — Launch

Live-fire test purchases through every funnel step. Meta Event Match Quality goes from 4.5 to 8.7 — verified live in Events Manager. They get a Notion runbook + Loom walkthrough so their dev team can extend it.

Day 5–7 — Accuracy

Conversion data starts flowing cleanly. Day 7: reported ROAS reads 2.8× (matches Stripe within 5%). Lookalike audiences grow because Meta finally has clean seed data. Their CAC dashboard makes sense for the first time in a year.

Day 30 — The math compounds

Smart Bidding has 30 days of clean signal. CPA drops 18%. They scale Meta budget 40% because they finally trust the data. Net new revenue from the recovered tracking: roughly $14K/mo above what they were getting before.

Numbers above are realistic averages from engagements we’ve shipped. Your specific recovery depends on your iOS share, ad-blocker rate, and current setup — we’ll quantify it on the call.

The cookie window unlock

400-day cookie lifetime — the longest your browser allows

Default gbraid and wbraid attribution issues setups put cookies on a 7–30 day timer. Safari ITP caps client-set cookies at 7 days. That kills your retargeting windows, shrinks lookalike audiences, and starves Smart Bidding of historical signal.

We set 1st-party cookies via HTTP headers on your own subdomain — exempt from ITP’s 7-day cap. Lifetime: 400 days. The maximum Chrome, Firefox and Safari currently permit.

  • 57× longer retargeting window vs Safari default

    Reach users who saw your ad 6 months ago instead of last week.

  • Bigger lookalike seed pools

    More retained users in your custom audience = better lookalike quality on Meta, Google, TikTok.

  • Smart Bidding has 13× more signal history

    Algorithms optimize on 400 days of behavior, not 7 days. CPA stabilizes faster.

  • Critical for high-AOV / long-consideration purchases

    If your average buyer takes 30+ days to convert, default cookies miss them. 400-day cookies don’t.

Cookie lifetime — head to head

How long cookies survive in real-world traffic

Safari ITP (default)7 days
Chrome / Firefox (typical)30 days
Meta default retargeting window90 days
Google Ads default cookie540 days(but capped by browser)
Our 1st-party server-side400 days

400 days is the hard maximum enforced by RFC 6265bis (Chrome 104+, Safari 17+, Firefox 110+). We set it via HTTP Set-Cookie: Max-Age=34560000 on your subdomain. Survives Safari ITP’s 7-day client-side cap.

Under the hood

What’s actually happening on your server-side stack

Six capabilities your default gbraid and wbraid attribution issues setup doesn’t have. Built on the same Stape Pro stack used by enterprise DTC brands.

Cookie window

Cookie Keeper

400-day 1st-party cookies

Set via HTTP headers on your subdomain — the maximum browsers allow. Survives Safari ITP’s 7-day cap that kills retargeting.

Ad-block resistance

Custom Loader

Custom-loaded GTM scripts

Your gtm.js and analytics scripts load through a custom path on YOUR domain. uBlock, AdBlock Plus, Brave can’t identify them as trackers.

Attribution

Click ID Restorer

Click ID restoration

fbclid / gclid / ttclid / wbraid recovered from the URL and persisted server-side. Multi-redirect funnels stop dropping attribution. Safari user IDs restored.

Profit signal

POAS Data Feed

POAS — Profit on Ad Spend

Send actual profit data (not revenue) to Meta / Google. Smart Bidding optimizes for the metric that matters: net margin, not gross revenue.

Identity

User ID

Cross-session User ID

Stable userID generated server-side from IP + UA + SSL fingerprint. Stitches anonymous → known → returning visitors across 400 days.

Audience signal

GEO Headers

GeoIP enrichment

Country, region, city, postal code passed to Meta / Google CAPI from your server — without exposing the raw user IP to the browser.

Compliance

Anonymizer

PII hashing by default

Email, phone, name, address are SHA-256 hashed on your server before they leave for Meta or Google. Zero raw PII in transit.

Quality filtering

Bot Detection

Bot traffic detection

Bot/scraper traffic identified at the gateway and blocked from polluting your audiences. Smart Bidding optimizes against humans, not bots.

Reliability

Dedup logic

Browser ↔ server dedup

Deterministic event_id and event_time so Meta / Google never double-count. Your reported ROAS stops contradicting Stripe.

Reputation

Dedicated IP

Dedicated outbound IP

Your sGTM gets a dedicated static IP for outgoing CAPI requests. Better deliverability to Meta, Google, TikTok — no shared-IP noise.

Residency

Multi-region

EU / US region routing

GDPR-conscious stores route their CAPI traffic through EU regions (Stape EU or self-hosted GCR europe-west). No US data hop.

Data warehouse

BigQuery export

BigQuery + Looker dashboard

Server logs + GA4 raw events streamed to BigQuery. Looker Studio dashboard branded for your team. Premium tier.

We’re official Stape Pro partners — every Power-Up above is enabled and configured for you. Or we self-host the equivalent on your Cloud Run / GKE if your traffic justifies the cost crossover. You pick.

Live data flow

What your stack is doing —right now

Every conversion fires through your subdomain, gets enriched with hashed identity params, deduped against the browser pixel, then forwarded to Meta CAPI, Google EC, TikTok Events API and Microsoft UET in parallel.

You see this stream live in your sGTM debug console — not a SaaS dashboard you rent. It’s your data, on your server, on your subdomain.

  • p99 latency< 80ms
  • Avg. event payload9 identity params
  • Browser → Server dedupDeterministic event_id
  • Failure handlingRetry · queue · dead-letter
sgtm-debug · data.gbraid.com
streaming
10:42:18[INFO]evt=PageView | id=ev_a3f2.. | ua=ios17 | ip_hash=ok
10:42:18[OK]→ meta.capi status=200 emq_pred=8.6
10:42:18[OK]→ google.ec status=200 match=enhanced
10:42:24[INFO]evt=AddToCart | id=ev_b1c8.. | val=$84.00
10:42:24[DEDUP]browser↔server merged on event_id=b1c8..
10:42:24[OK]→ meta.capi status=200 emq_pred=8.7
10:42:24[OK]→ tiktok.eventsapi status=200
10:42:31[INFO]evt=Purchase | id=ev_c9d4.. | val=$184.00
10:42:31[POAS]profit=$58.42 sent (margin 31.7%)
10:42:31[OK]→ meta.capi status=200 emq=8.8 ✓
10:42:31[OK]→ google.ec status=200 ✓
10:42:31[OK]→ microsoft.uet status=200 ✓
10:42:33[BOT]blocked: ua=AhrefsBot · 1 evt suppressed
uptime: 99.98%all channels healthy
Every paid-media channel · 1st-party server-side

CAPI / Events API ready for every ad platform you run

One server-side gateway. Every major ad platform fed real conversion data, deduped, with full identity match.

Meta

Conversions API

Server-side

Google

Enhanced Conv.

Server-side

TikTok

Events API

Server-side

Microsoft

UET Server

Server-side

LinkedIn

CAPI

Server-side

Pinterest

CAPI

Server-side

Snapchat

CAPI

Server-side

Reddit

CAPI

Server-side

X / Twitter

Events API

Server-side
What you get

What we do about it

Item 01

Widen the capture to all three parameters

One line of logic instead of one parameter name. This alone recovers most of the loss.

Item 02

Store which type arrived

The upload needs to know whether it is sending a gclid, a gbraid or a wbraid. Storing the value without the type creates a problem later.

Item 03

Route uploads by identifier type

Google's import accepts each, in its own field. Mixing them produces rejected rows.

Item 04

Set expectations on what wbraid can and cannot do

It is a privacy-preserving aggregate identifier. Some user-level features are unavailable with it by design, and that is not a bug to work around.

The honest math

Three ways to fix your tracking. One of them makes sense.

Option 1

Hire a senior tracking engineer

$15K–$25Kin dev cost

or 2–4 weeks of senior FTE time

  • 2–4 weeks before anything ships
  • Misses iOS / Safari / dedup edge cases
  • No EMQ guarantee — it’s “done” when they say so
  • Pixel debugging is not their day job

Option 2

Triple Whale / Hyros / Northbeam

$300–$2,000/month forever

$18K–$120K over 5 years

  • You rent a dashboard — they own your data
  • Cancel and you lose attribution overnight
  • Per-event / per-visitor pricing surprises
  • Still doesn’t fix your underlying tracking
Recommended

Option 3 — us

Done-for-you 1st-party server-side

$400–$1,800one-time

pay once · own the stack forever

  • Live in 2–4 days · accurate data within 7
  • iOS / Safari / dedup all handled by default
  • Meta EMQ 8+ guaranteed in writing
  • You own everything — server, container, runbook

We’re upfront: if you have a senior in-house dev with capacity and 4 weeks, hiring is fine. If you spend $1M+/yr on ads and want a SaaS dashboard layered on top, Triple Whale works. For most paid-ad advertisers between, we’re the math that makes sense.

Pricing

Pick the package that fits your ad spend

Fixed-fee, no surprises. If your ad spend is meaningful,server-side tracking is what we recommend— it’s the only setup that survives iOS, Safari ITP and ad blockers.

Tier 01

Browser-side starter

$400One-time fee · lifetime ownership

We fix the fault in your existing browser-side setup and verify it on a live transaction. Honest disclosure: this repairs what you have, it does not make it durable. If you spend $1K+/month on paid media, the fault will recur the next time Safari, a consent banner or a checkout change moves under you — the server-side tier is what stops that.

  • Root cause found and fixed, not worked around
  • Verified on a live transaction, not in preview
  • Reconciled against your own order records
  • Written handover documenting what changed and why
Fix what I have
Tier 02
Recommended

1st-party server-side

$800One-time fee · most popular

Save $18K–$120K over 5 years vs Triple Whale / Hyros

The tier that removes the whole class of failure rather than this instance of it. Your money events stop depending on the browser: they are sent from your order records through a first-party server container on your own subdomain, so iOS, ad blockers, consent banners and interrupted payment redirects can no longer take them away. Built in 2–4 days. You own the stack outright — no monthly SaaS.

  • First-party server container on your own subdomain
  • Purchases sent from your order records, not the browser
  • Meta, Google, TikTok, Microsoft and LinkedIn all fed server-side
  • Deduplicated on a shared event ID, verified at every destination
  • First-party cookies beyond Safari's 7-day cap on JavaScript-set cookies
  • 95%+ conversion accuracy and 8+ Meta EMQ, guaranteed in writing
Rebuild it server-side
Tier 03

Full 1st-party stack

$1,800One-time fee · lifetime ownership

Every paid-media channel server-side, end to end, plus the offline loop. For advertisers whose spend makes an attribution leak more expensive than the build. Pay once, own everything.

  • Everything in 1st-party server-side
  • Pinterest, Snapchat, Reddit and LinkedIn CAPI
  • CRM and offline conversion loop, so closed revenue reaches bidding
  • Refunds and cancellations reversed at every destination
  • Klaviyo identity stitching, BigQuery and Looker Studio
  • Monitoring, so the next break surfaces in days rather than a quarter
Get the full stack

Not sure which tier fits?Book a 30-min scoping call— we’ll tell you straight, no upsell pressure.

From the founder’s desk
Ariful Islam — Founder
Available now

Ariful Islam

Founder & lead engineer

  • Experience8+ years in tracking
  • Engagements300+ DTC brands shipped
  • Specialty1st-party sGTM · CAPI
  • PartnerStape Pro · Meta Tech

“I’ll personally walk through your tracking on the call.No SDR.No sales pitch.”

I’ve spent 8 years rebuilding tracking for DTC brands, SaaS founders, agencies, and one thing I’ve learned: most tracking problems aren’t technical — they’re trust problems. You don’t know who to believe. Your current vendor swears it’s fine. Meta’s reports look great. Stripe says otherwise.

On our call, I’ll personally show you exactly what’s leaking, exactly what it would cost to recover, and whether you should hire us at all. If your current setup is genuinely fine, I’ll tell you. If a $400 browser-side fix is enough, I’ll say so. No upsell pressure.

Book the call. Worst case, you walk away with a free 47-point audit checklist. Best case, we deliver your 1st-party server-side stack in 2–4 days and your data is fully accurate within 7 days.

Book the call with meOr WhatsApp me direct
Arif— Founder

How it works

Built in 2–4 days. Accurate data within 7.

We deliver the entire 1st-party server-side stack in 2–4 business days. You start collecting accurate, deduped conversion data the moment it goes live — and within 7 days every signal is flowing cleanly to Meta, Google, TikTok and the rest.

1Day 1

Kickoff + audit

30-min call. We map your current pixels, GTM, dataLayer, consent setup, and ad-platform integrations. You get a written report of every leak.

2Day 2–3

Build the stack

Server-side GTM container deployed on your subdomain. Meta CAPI · Google EC · TikTok Events API · Microsoft UET wired. Identity match + dedup configured.

3Day 4

QA + go-live

Live-fire test purchases across every funnel step. Meta EMQ verified at 8+. Tag Assistant + Pixel Helper passes. Side-by-side report delivered.

4Day 5–7

Verify accuracy

Your data flows clean. Within 7 days every signal — Meta, Google, TikTok, Microsoft — is fully accurate. Notion runbook + Loom walkthrough handoff.

Got questions?

The honestanswers.

No buzzwords, no upsell. If we don’t know, we say so.

01What is the difference between gbraid and wbraid?

Both arrive on iOS traffic where a user-level identifier is not available. In broad terms they cover different traffic contexts — gbraid on app-related traffic and wbraid on web traffic under those privacy constraints. For implementation purposes the important part is that both are aggregate rather than user-level, both must be captured, and each must be uploaded in its own field. Check Google's current documentation for the precise definitions, which have been refined over time.

02Can I use enhanced conversions with wbraid?

Not in the same way as with gclid. These identifiers are designed to avoid user-level joining, so combining them with user-provided data is restricted by design. Treat that as a constraint to report honestly rather than a limitation to engineer around.

03Will fixing this recover past conversions?

Only within the import window, and only if the identifier was actually stored at the time. If your code never read gbraid, the value was never captured and there is nothing to recover. This is a fix that starts working forward, which is a reason to do it sooner.

04Do the other ad platforms have the same problem?

They have their own iOS constraints, but not this specific one — this is a Google-specific mechanism. Meta's, TikTok's and Reddit's identifiers behave differently and fail differently.

Still have questions?Book a 30-min call— bring them all.

The call

What happens on your free 30-min call

No pitch deck, no SDR, no upsell pressure. Founder-led. Bring your ad-platform screens and yourgbraid and wbraid attribution issues setup — we’ll work through it together.

Min 1–5

We get the lay of your store

What you sell, what you spend on ads, who handles dev. Quick context-gathering — no questionnaire upfront.

Min 5–15

We audit your tracking live

Screen-share. We open your Meta Events Manager, GTM, and ad reports. You see exactly which conversions are leaking.

Min 15–25

We map a fix

What needs rebuilding, what stays. The exact gbraid and wbraid attribution issues setup we'd ship and what it would recover for you.

Min 25–30

Decide. Or don’t.

If we're a fit, we send a 1-page proposal in writing. If not, you walk away with a free remediation plan you can hand to anyone.

No pitch deckFounder-led, not SDRYou leave with a written planZero commitment
Free · 30 minutes · No commitment

Get gbraid and wbraid attribution issues diagnosed properly

Book a free 30-minute call. We diagnose it live on your own account and you leave with a written fix list, whether or not you hire us.

Book the free diagnosis callWhatsApp · urgent helpSend a message instead

Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp

You might also need

gbraid and wbraid missing

Why are gbraid and wbraid missing from my iOS traffic?

Read more

Google click identifiers

gclid, gbraid and wbraid

Read more

Call Tracking

Your bidding is optimizing for phones ringing. You get paid when a job gets book…

Read more

95% guarantee · from $400

Book