Meta Ads (Conversions API)
The server event carries what the browser never saw.
Pixel-only tracking loses the customer who converts on another device or after the cookie died. This connection sends the confirmed outcome through the Meta Conversions API while the Pixel stays in the loop for deduplication.
Pages marked Planned are complete specifications written before the connector ships. They validate demand. Connectors with real delivery logs are marked Production or Beta.
The Pixel sees less every year
Browser limits, consent prompts, and cross-device journeys break cookie-based attribution. Meta optimizes on partial signals while your CRM holds the complete story.
One event_id, two channels, zero double counting
Apointoo sends lead and purchase events with fbp and fbc identifiers plus a stable event_id. Meta matches server events against Pixel events and counts each customer once. The CRM outcome becomes a signal bidding can use.
What it sends to Google Ads
How the data flows
- Ad click (fbclid, _fbp / _fbc cookies)
- Apointoo Capture stores the click
- Your CRM or checkout confirms the outcome
- Apointoo sends the server event
- event_id deduplicates against the Pixel
How the connection works
Capture stores fbclid and the _fbp and _fbc cookies on first touch.
Your CRM confirms qualified leads and sales.
Apointoo posts server events with hashed identity fields and stable event ids.
Logs show every accepted, rejected, and retried delivery.
Attribution identifiers
Event mapping
| From | Apointoo |
|---|---|
| Form or lead captured | Lead server event |
| Qualified lead stage | QualifiedLead custom event |
| Purchase confirmed | Purchase server event (value + currency) |
Frequently asked questions
The server event carries what the browser never saw.