Integrations / Analytics
Convert
Conversion and experiment event tracking for Convert.
Datafly Signal delivers first-party events to Convert server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Convert expects.
Why route Convert through Datafly Signal
Your numbers stop depending on what the browser allows
Client-side analytics loses every visit where the tag is blocked or the page unloads early. Signal delivers from the server, so Convert receives the complete event stream.
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 Convert needs to attribute the event to the right session.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Convert rate limit, and retries on 429 or transient failure rather than dropping the event.
Token lifecycle is handled for you
Signal obtains and refreshes the OAuth credentials Convert requires, so nothing expires quietly in the middle of a campaign.
One consent decision governs every destination
Convert 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
pagepurchaseview_itemVertical presets
Retail. 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 Convert documentation.
Frequently asked questions
Does Datafly Signal integrate with Convert?
Yes. Datafly Signal delivers first-party events to Convert server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Convert expects. The integration is included in every deployment at no additional cost.
How is server-side Convert tracking different from the Convert tag?
The Convert 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 Convert from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Convert?
The blueprint ships with mappings for page, purchase, view_item. Any event in your schema can be mapped to Convert through pipeline configuration without a code change.
Do I need to keep the Convert tag on my site?
No. Signal delivers to Convert from the server, so no client-side Convert script is required on your site.
Other analytics integrations
Ready to move Convert server-side?
See how Datafly Signal delivers first-party events to Convert from infrastructure you control, with hashed identity and consent enforcement built in.