Integrations / Advertising
CM360
Floodlight conversion tracking for Campaign Manager 360.
Datafly Signal delivers first-party events to CM360 server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload CM360 expects.
Why route CM360 through Datafly Signal
Conversions survive ad blockers and tracking prevention
A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari's ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions CM360 optimises against are not filtered by the browser.
Email and phone number hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so CM360 receives match keys rather than raw personal data.
Click identifiers are captured and replayed
Signal stores gclid, dclid first-party at collection time and attaches them to the conversion later, so attribution survives even when the original landing cookie has expired.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the CM360 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 CM360 requires, so nothing expires quietly in the middle of a campaign.
One consent decision governs every destination
CM360 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_leadpurchaseVertical 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 CM360 documentation.
Frequently asked questions
Does Datafly Signal integrate with CM360?
Yes. Datafly Signal delivers first-party events to CM360 server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload CM360 expects. The integration is included in every deployment at no additional cost.
How is server-side CM360 tracking different from the CM360 tag?
The CM360 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 CM360 from your server, so delivery does not depend on browser conditions.
What personal data is sent to CM360?
Email and phone number are normalised and SHA-256 hashed inside your own deployment before delivery, so CM360 receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to CM360?
The blueprint ships with mappings for generate_lead, purchase. Any event in your schema can be mapped to CM360 through pipeline configuration without a code change.
Do I need to keep the CM360 tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so CM360 deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move CM360 server-side?
See how Datafly Signal delivers first-party events to CM360 from infrastructure you control, with hashed identity and consent enforcement built in.