Conversions to Meta —from the server, not the browser.
Adset.Pro sends PWA installs, registrations and deposits to Facebook and Instagram via the Conversions API — as soon as the affiliate network fires a postback. Ad blockers and iOS restrictions don't lose events, and Meta's algorithm optimizes on real deposits.
Why connect Meta CAPI
Independent of the browser
Events leave the Adset.Pro server on the affiliate postback — ad blockers, in-app browsers and iOS restrictions don't eat your conversions.
Optimize for deposits
A deposit goes out as Purchase with the real amount and currency, a registration as CompleteRegistration, a PWA install as Lead. Meta's algorithm learns from the people who pay.
Attribution from the ad click
fbc comes from the cookie or is built from fbclid and the original click time; external_id is a hash of the click id. The conversion is tied to the ad even if the deposit arrives days later.
Every event in sight
Pixel logs show the status and Meta's response for every send, and Test Events checks the setup before launch. Failed API calls are retried, and a malformed token switches the pixel off and notifies the owner.
What Adset.Pro sends to Meta
| Field | What it is |
|---|---|
| event_name | Event by mapping: Lead, CompleteRegistration, Purchase or another standard event |
| event_id | Unique conversion ID — re-sending doesn't create a duplicate |
| event_time | Conversion time |
| fbc | The _fbc cookie or a value built from fbclid and the original click time |
| fbp | The _fbp cookie, if present |
| client_ip_address · client_user_agent | User IP and browser from the original click |
| external_id | SHA-256 of the click id — a stable user identifier |
| country | SHA-256 of the user's country |
| value · currency | Deposit amount and currency from the postback — for Purchase |
| action_source | website |
Connect in 4 steps
Get the Pixel ID and token
In Events Manager open the pixel → Settings: copy the Pixel ID and generate a Conversions API Access Token.
Create the pixel in Adset.Pro
Tracker → Pixels → + Pixel, type Facebook. The Lead / CompleteRegistration / Purchase mapping is filled in for you.
Attach it to a campaign
Add the pixel to the campaign's stream set — up to 3 pixels per set. The Facebook source passes fbclid into the tracking link.
Check Test Events
Send a test event with a Test Event Code and make sure it shows up in Events Manager. Live send statuses are in the pixel logs.
Common questions
No. Conversions arrive as affiliate postbacks and go to Meta from the server. Every event has a unique event_id, so re-sending doesn't create a duplicate.
No. The tracker sends Meta conversions that happen within 7 days of the click — Meta's standard click attribution window. Later deposits stay in Adset.Pro stats and LTV reports.
Events Manager shows every accepted event, while Ads Manager shows only those Meta attributed to ads within its attribution window. Common causes are covered in the knowledge base.
Yes, as a separate integration: spend is pulled via a dev token, the browser extension or the antidetect agent, and ROI is calculated down to the ad level.
Connect Meta CAPI
on the free Starter plan
Included in every plan · Live support · No card required