Stop scaling blind: trace every Braip sale back to the ad
If you sell supplements or info products through Braip you know the scene: Braip shows one sales number, Ads Manager shows a much smaller one. The cause is structural — checkout runs on Braip's domain, and the Meta pixel depends on the buyer's browser to close attribution. The domain switch, iOS and ad blockers eat events along the way, and you're left deciding affiliate and traffic budgets on incomplete data.
IzeAds solves it at the server layer: Braip fires a webhook to IzeAds on every purchase event, and the tracking code (SCK) that followed the buyer from the ad ties the sale to the click that originated it. Attribution is born from the sale approved in the gateway, not from a script that maybe loaded on a thank-you page.
How to set it up
The connection is done inside IzeAds in a few minutes: you connect Meta, generate the notification link and enable it in the platform panel. The full, always up-to-date walkthrough lives in the help center.
Open the guide in the help center →What the integration delivers
Sale in your dashboard within seconds
Approved on Braip, visible in IzeAds — with the source campaign, ad set and ad identified.
Reversals don't stay hidden
Refunds and chargebacks knock attributed revenue down immediately, so the ROAS you see is the operation's true net.
Pending Pix and boleto flagged
When a buyer generates a Pix or boleto without paying, IzeAds notifies you — you watch it move from pending to approved.
Conversions handed back to Meta
Every confirmed sale is resent via Conversions API to Meta and up to 7 other ad platforms, sharpening optimization.
Every gateway in one dashboard
Braip on one side, other gateways on the other — IzeAds unifies everything into a single view of sales per campaign.
Frequently asked questions
Why doesn't the Meta pixel match Braip's sales numbers?
Because the purchase completes on Braip's domain and the pixel only works inside the browser: the domain change breaks attribution, iOS and blockers suppress events, and a thank-you-page fire can't tell approved from declined payments. IzeAds' server-to-server webhook starts from the sale confirmed by the gateway — the browser is out of the picture.
Could someone push fake notifications into my dashboard?
No. Beyond the webhook link being exclusive to your account, IzeAds validates the origin of every incoming notification before recording it — anything that fails the check is discarded.
Which Braip events does IzeAds process?
Approved purchases (sale attributed to a campaign), refunds and chargebacks (automatic metric adjustments), and the alert for a Pix/boleto generated and awaiting payment.
What if I sell through more than one platform?
No problem. Each gateway connected to IzeAds gets its own webhook link, and sales from all of them meet in the same dashboard, each attributed to the right campaign.
More integrations
Connect in ~4 minutes
Create your account, connect Meta and paste one webhook link. Free trial, no lock-in.