Track every Hotmart sale back to the campaign that drove it
Hotmart's checkout happens outside your domain — and that's where the Meta pixel loses the thread. The browser chain breaks on the domain switch, iOS and ad blockers cut the rest, and Ads Manager ends up showing numbers that don't match your Hotmart dashboard. Without knowing which campaign drove each sale, you scale on guesswork.
The IzeAds integration solves this server-side: Hotmart notifies IzeAds of every purchase event via webhook, and IzeAds matches the sale to the original click using the tracking code (SCK) that followed the buyer from the ad. It's the APPROVED sale in the gateway — not a pixel fired on a thank-you page that counts even declined payments.
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
Approved sales in real time
Every approved purchase shows up the moment it happens, tied to the campaign, ad set and ad that drove it.
Refunds and chargebacks reflected
Refunded purchases, chargebacks and disputes update your metrics — the ROAS you see is net, not gross.
CAPI back to Meta
The approved sale is sent as a conversion to Meta via Conversions API (plus 7 other platforms), improving the algorithm's optimization.
Boleto and delayed payments on the radar
Printed-boleto, delayed and expired purchase events also arrive — you watch the whole payment funnel.
A push on your phone for every sale
iOS and Android apps send one notification per approved sale — with value, product and campaign.
Frequently asked questions
Why doesn't the Meta pixel track Hotmart sales well?
Because checkout runs on Hotmart's domain and the pixel's Purchase fires (when it fires) on the thank-you page — with no guarantee the payment was approved, and losing purchases to iOS, ad blockers and the domain switch. The IzeAds integration uses Hotmart's server-to-server webhook: only approved sales count, and nothing is lost in the browser.
What is the Hottok and why does IzeAds ask for it?
It's the credential Hotmart sends along with every webhook notification. IzeAds requires the Hottok to validate that the notification really came from Hotmart — without it, anyone could forge sales into your dashboard.
Which Hotmart events does IzeAds process?
Approved and completed purchases (become attributed sales), refunds, chargebacks and disputes (adjust metrics), plus printed-boleto, delayed and expired purchases (payment-funnel tracking).
Does it work alongside other platforms at the same time?
Yes. Each connected platform (Hotmart, Kirvano, Ticto, Cartpanda and more) gets its own webhook link, and all sales land in the same dashboard, attributed to your campaigns.
More integrations
Connect in ~4 minutes
Create your account, connect Meta and paste one webhook link. Free trial, no lock-in.