PerfectPay sales attributed to the right ad, no guesswork
The buyer clicks your ad but pays on PerfectPay's checkout — another domain, another context. That's where the Meta pixel stumbles: browser tracking gets lost in the domain change and takes further hits from iOS and ad blockers. In the end, Ads Manager undercounts your conversions and you can't say for sure which creative is paying the bills.
With IzeAds, confirmation travels a different route: PerfectPay sends every purchase event by webhook straight to the IzeAds server, which rebuilds the journey using the tracking code (SCK) carried since the first ad click. Your dashboard records the sale the gateway approved — no counting thank-you-page pixels as if they were cash in the register.
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
From click to sale, in real time
Approved on PerfectPay, visible in your dashboard — already linked to the responsible campaign, ad set and ad.
Metrics net of reversals
Refunds and chargebacks automatically reduce attributed revenue: the ROAS you see is the true net.
A clean signal for Meta's algorithm
Confirmed sales return via Conversions API to Meta and up to 7 other platforms — optimization on real conversions, not estimates.
Pix generated, you know about it
A pending Pix or boleto notification the moment the buyer generates the payment — even before approval.
~4-minute setup
Two steps and done: connect Meta and paste a link. No code, no developer needed.
Frequently asked questions
Why doesn't the Meta pixel track PerfectPay sales well?
Payment happens on PerfectPay's domain, and the pixel only sees what happens in the browser: the domain switch cuts the attribution chain, iOS and blockers drop events, and the thank-you-page fire can even count declined payments. IzeAds' server-to-server webhook receives confirmation straight from the gateway, immune to all of that.
Is pointing a webhook at IzeAds safe?
It is. The link is exclusive to your account and every incoming notification goes through origin validation before becoming a record — forged notifications are rejected and never pollute your metrics.
Which PerfectPay events does IzeAds process?
Approved purchases, which become attributed sales; refunds and chargebacks, which adjust revenue and ROAS; and the alert for a Pix/boleto generated but not yet paid.
I use PerfectPay plus another gateway — does it work?
It does. IzeAds generates one webhook link per connected platform and consolidates all sales in the same dashboard, each tied to its source campaign.
More integrations
Connect in ~4 minutes
Create your account, connect Meta and paste one webhook link. Free trial, no lock-in.