Integrations / CRM
Zendesk
Server-side delivery to the Zendesk Events API (POST /api/v2/user_profiles/events). Records first-party customer activity as custom events on the Zendesk end-user profile timeline, matched to existing end users by email (plus user_id as external_id), so support agents see pre-ticket context. Custom event data is carried under event.properties; the profile.identifiers array is assembled by a global reshaping script.
Datafly Signal delivers first-party events to Zendesk server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Zendesk expects.
Why route Zendesk through Datafly Signal
Profiles update from the server, not the browser
Events reach Zendesk 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
Zendesk 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
generate_leadloginpagepurchasesign_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 Zendesk documentation.
Frequently asked questions
Does Datafly Signal integrate with Zendesk?
Yes. Datafly Signal delivers first-party events to Zendesk server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Zendesk expects. The integration is included in every deployment at no additional cost.
How is server-side Zendesk tracking different from the Zendesk tag?
The Zendesk 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 Zendesk from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Zendesk?
The blueprint ships with mappings for generate_lead, login, page, purchase, sign_up, view_item. Any event in your schema can be mapped to Zendesk through pipeline configuration without a code change.
Do I need to keep the Zendesk tag on my site?
No. Signal delivers to Zendesk from the server, so no client-side Zendesk script is required on your site.
Ready to move Zendesk server-side?
See how Datafly Signal delivers first-party events to Zendesk from infrastructure you control, with hashed identity and consent enforcement built in.