Integrations / CRM
Totango
Server-side delivery of product-usage activities and account/user attribute updates to Totango's customer success platform via the SDR (pixel.gif) HTTP API. Activities land on the account timeline and feed health scores, SuccessPlays, and usage segments without a browser tag.
Datafly Signal delivers first-party events to Totango server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Totango expects.
Why route Totango through Datafly Signal
Profiles update from the server, not the browser
Events reach Totango 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
Totango 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
feature_usedloginpageplan_viewedsign_upsubscription_cancelledsubscription_startedsupport_ticket_createdtrial_startedVertical presets
B2B / SaaS. 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 Totango documentation.
Frequently asked questions
Does Datafly Signal integrate with Totango?
Yes. Datafly Signal delivers first-party events to Totango server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Totango expects. The integration is included in every deployment at no additional cost.
How is server-side Totango tracking different from the Totango tag?
The Totango 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 Totango from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Totango?
The blueprint ships with mappings for feature_used, login, page, plan_viewed, sign_up, subscription_cancelled, subscription_started, support_ticket_created, and more. Any event in your schema can be mapped to Totango through pipeline configuration without a code change.
Do I need to keep the Totango tag on my site?
No. Signal delivers to Totango from the server, so no client-side Totango script is required on your site.
Ready to move Totango server-side?
See how Datafly Signal delivers first-party events to Totango from infrastructure you control, with hashed identity and consent enforcement built in.