In short
Tagbreeze sends each conversion from the browser and from its own servers to Meta and TikTok, with one event ID, so ad blockers and expired cookies stop hiding your sales.
01
Why the browser is not enough
A pixel only reports what the visitor's browser lets through. An ad blocker stops the request, Safari shortens the life of the cookie, the buyer closes the tab before the confirmation page has finished loading. The sale happened; the ad platform never heard of it.
The platform then optimises on a partial picture, and your reports show a return that is lower than the real one.
02
Two roads, one event ID
With Tagbreeze each conversion leaves twice:
- from the browser, to Meta, Google Analytics 4, Google Ads and TikTok, the way their own pixels would;
- from our servers, to the Meta Conversions API and the TikTok Events API, carrying the same event ID.
Because the ID is the same, the platform recognises the pair and counts the conversion once. You do not rent a server, configure a tagging container or write code.
03
What is sent, and what is not
E-mail addresses and phone numbers typed at checkout are hashed on the visitor's device before anything leaves it. Tagbreeze never receives the readable value.
Server delivery follows consent exactly like the browser does: when a visitor refuses, nothing is forwarded to an ad platform by either road. Server-side delivery exists today for Meta and TikTok; Google Analytics 4 and Google Ads receive their events from the browser.
See also: Meta Conversions API · TikTok Events API
Questions
Before you ask.
Do I need Google Tag Manager server-side?
No. The server part runs on Tagbreeze. You install one tag on the site and connect your ad accounts.
Will conversions be counted twice?
No. The browser event and the server event carry the same event ID, which is what Meta and TikTok use to keep one copy.
Does it bring back sales from visitors who refused tracking?
No. A refusal is respected on both roads. Server-side tracking recovers what browsers lose by accident, not what a visitor chose not to share.
Understand it
Tracking basics · 5 min
What is server-side tracking?
Server-side tracking reports conversions from a server instead of the visitor's browser. Here is what it recovers and what it cannot fix.
Tracking basics · 5 min
Meta Conversions API explained
What the Meta Conversions API is, how browser and server events are deduplicated with event_id, and what raises your event match quality.
Tracking basics · 6 min
Why ad platforms miss conversions
Apple's tracking prompt, Safari cookie limits, ad blockers and consent refusals all hide sales from ad platforms. Here is how, and what it costs.
More of what the product does.
Know what your ads really bring in.
It takes a few minutes. Nothing is changed on your site until you install the tag.
Add your site