Integrations / Marketing Automation
Listrak
Deliver Signal events to Listrak's Cross Channel REST API as custom events into a Journey Hub journey. Contacts are matched by email (identifierType EmailAddress); event detail is sent in dataFields. OAuth 2.0 client_credentials auth; eventUid + companyId from integration config.
Datafly Signal delivers first-party events to Listrak server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Listrak expects.
Why route Listrak through Datafly Signal
Profiles update from the server, not the browser
Events reach Listrak even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Listrak 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 Listrak requires, so nothing expires quietly in the middle of a campaign.
One consent decision governs every destination
Listrak 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_cartpagepurchasesign_upview_itemVertical presets
Default. 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 Listrak documentation.
Frequently asked questions
Does Datafly Signal integrate with Listrak?
Yes. Datafly Signal delivers first-party events to Listrak server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Listrak expects. The integration is included in every deployment at no additional cost.
How is server-side Listrak tracking different from the Listrak tag?
The Listrak 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 Listrak from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Listrak?
The blueprint ships with mappings for add_to_cart, page, purchase, sign_up, view_item. Any event in your schema can be mapped to Listrak through pipeline configuration without a code change.
Do I need to keep the Listrak tag on my site?
No. Signal delivers to Listrak from the server, so no client-side Listrak script is required on your site.
Other marketing automation integrations
Ready to move Listrak server-side?
See how Datafly Signal delivers first-party events to Listrak from infrastructure you control, with hashed identity and consent enforcement built in.