Integrations / Marketing Automation
Cheetah Digital
Server-to-server delivery to Cheetah Digital by Marigold via the Standard Event Trigger API. Fires triggered campaigns and loads recipient activity using OAuth 2.0 password-grant auth, normalised-SHA256 email/phone hashing, and marketing-consent gating.
Datafly Signal delivers first-party events to Cheetah Digital server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Cheetah Digital expects.
Why route Cheetah Digital through Datafly Signal
Profiles update from the server, not the browser
Events reach Cheetah Digital even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Email hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Cheetah Digital receives match keys rather than raw personal data.
Token lifecycle is handled for you
Signal obtains and refreshes the OAuth credentials Cheetah Digital requires, so nothing expires quietly in the middle of a campaign.
One consent decision governs every destination
Cheetah Digital 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
pagepurchasesign_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 Cheetah Digital documentation.
Frequently asked questions
Does Datafly Signal integrate with Cheetah Digital?
Yes. Datafly Signal delivers first-party events to Cheetah Digital server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Cheetah Digital expects. The integration is included in every deployment at no additional cost.
How is server-side Cheetah Digital tracking different from the Cheetah Digital tag?
The Cheetah Digital 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 Cheetah Digital from your server, so delivery does not depend on browser conditions.
What personal data is sent to Cheetah Digital?
Email are normalised and SHA-256 hashed inside your own deployment before delivery, so Cheetah Digital receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Cheetah Digital?
The blueprint ships with mappings for page, purchase, sign_up, view_item. Any event in your schema can be mapped to Cheetah Digital through pipeline configuration without a code change.
Do I need to keep the Cheetah Digital tag on my site?
No. Signal delivers to Cheetah Digital from the server, so no client-side Cheetah Digital script is required on your site.
Other marketing automation integrations
Ready to move Cheetah Digital server-side?
See how Datafly Signal delivers first-party events to Cheetah Digital from infrastructure you control, with hashed identity and consent enforcement built in.