Integrations / Marketing Automation
Leanplum
Server-side event tracking via the Leanplum track API. Delivers page views, sign-ups, logins, and the full e-commerce funnel (product views, cart, checkout, purchase) to Leanplum for cross-channel engagement and analytics. Identity via userId/deviceId; monetization events use Leanplum's reserved value + currencyCode fields; all other event metadata is flattened into Leanplum params.
Datafly Signal delivers first-party events to Leanplum server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Leanplum expects.
Why route Leanplum through Datafly Signal
Profiles update from the server, not the browser
Events reach Leanplum even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
One consent decision governs every destination
Leanplum 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_to_cartbegin_checkoutloginpagepurchasesearchsign_upview_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 Leanplum documentation.
Frequently asked questions
Does Datafly Signal integrate with Leanplum?
Yes. Datafly Signal delivers first-party events to Leanplum server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Leanplum expects. The integration is included in every deployment at no additional cost.
How is server-side Leanplum tracking different from the Leanplum tag?
The Leanplum 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 Leanplum from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Leanplum?
The blueprint ships with mappings for add_to_cart, begin_checkout, login, page, purchase, search, sign_up, view_item. Any event in your schema can be mapped to Leanplum through pipeline configuration without a code change.
Do I need to keep the Leanplum tag on my site?
No. Signal delivers to Leanplum from the server, so no client-side Leanplum script is required on your site.
Other marketing automation integrations
Ready to move Leanplum server-side?
See how Datafly Signal delivers first-party events to Leanplum from infrastructure you control, with hashed identity and consent enforcement built in.