In short
Connect Meta in one sign-in: Tagbreeze sends each conversion through the pixel and the Conversions API with the same event ID, and reads your ad spend.
01
Connect
Sign in and pick the dataset (the pixel). No dataset yet? Tagbreeze can create one in your own business account, after you confirm. A test button sends an event you can watch arrive in Events Manager.
02
What is sent
Each conversion leaves from the browser, as the pixel would send it, and from Tagbreeze's servers through the Conversions API, with the same event ID. Meta keeps one copy. E-mail and phone are hashed on the visitor's device, which is what raises the match quality of server events.
03
Spend and reporting
Choose the ad account that pays for the site: Tagbreeze reads spend and reported conversions per ad, read-only, to compute return on ad spend next to what your site recorded.
Questions
Before you ask.
I already have the Meta pixel. Do I remove it?
No need. When the same pixel ID is already on the page, Tagbreeze leaves the browser side to it and adds the server side.
Do I need an access token?
No. The sign-in creates the access; there is nothing to copy or paste.
Understand it
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 · 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 · 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.
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