Integrations / Advertising
Meta CAPI
Server-side event delivery via the Meta Conversions API.
Datafly Signal delivers first-party events to Meta CAPI server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Meta CAPI expects.
Why route Meta CAPI through Datafly Signal
Conversions survive ad blockers and tracking prevention
A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari's ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Meta CAPI optimises against are not filtered by the browser.
Phone number, email, first name, last name, city, address, postcode and country hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Meta CAPI receives match keys rather than raw personal data.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what Meta CAPI needs to attribute the event to the right session.
Click identifiers are captured and replayed
Signal stores fbp, fbc first-party at collection time and attaches them to the conversion later, so attribution survives even when the original landing cookie has expired.
One consent decision governs every destination
Meta CAPI is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_payment_infoadd_to_cartadd_to_wishlistapplication_submittedbegin_checkoutbooking_cancelledbooking_completedbooking_startedbrochure_downloadeddealer_contacteddestination_searcheddonation_madefinance_quote_requestedgenerate_leadlisting_savedlisting_viewedpagepurchasesearchservice_appointment_bookedsign_upsubscription_startedtest_drive_bookedtrade_in_valuedtrial_startedvehicle_comparedvehicle_savedvehicle_searchedvehicle_viewedview_itemVertical presets
Retail, Travel, B2B / SaaS, Automotive. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Meta CAPI documentation.
Frequently asked questions
Does Datafly Signal integrate with Meta CAPI?
Yes. Datafly Signal delivers first-party events to Meta CAPI server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Meta CAPI expects. The integration is included in every deployment at no additional cost.
How is server-side Meta CAPI tracking different from the Meta CAPI tag?
The Meta CAPI tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Meta CAPI from your server, so delivery does not depend on browser conditions.
What personal data is sent to Meta CAPI?
Phone number, email, first name, last name, city, address, postcode and country are normalised and SHA-256 hashed inside your own deployment before delivery, so Meta CAPI receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Meta CAPI?
The blueprint ships with mappings for add_payment_info, add_to_cart, add_to_wishlist, application_submitted, begin_checkout, booking_cancelled, booking_completed, booking_started, and more. Any event in your schema can be mapped to Meta CAPI through pipeline configuration without a code change.
Do I need to keep the Meta CAPI tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so Meta CAPI deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Meta CAPI server-side?
See how Datafly Signal delivers first-party events to Meta CAPI from infrastructure you control, with hashed identity and consent enforcement built in.