Integrations / Advertising
Marin Software
Server-side conversion tracking via the Marin Tracker pixel (tracker.marinsm.com/tp). Delivers purchase/lead conversions with revenue, currency and a pipe-delimited UTM:T/UTM:I transaction string, stitched to the originating ad click by the first-party Marin UUID (_msuuid) and attributed via forwarded visitor IP and User-Agent.
Datafly Signal delivers first-party events to Marin Software server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Marin Software expects.
Why route Marin Software 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 Marin Software optimises against are not filtered by the browser.
Client IP and user agent are preserved
Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so Marin Software attributes the event to the right session.
One consent decision governs every destination
Marin Software 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_leadpagepurchaseVertical 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 Marin Software documentation.
Frequently asked questions
Does Datafly Signal integrate with Marin Software?
Yes. Datafly Signal delivers first-party events to Marin Software server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Marin Software expects. The integration is included in every deployment at no additional cost.
How is server-side Marin Software tracking different from the Marin Software tag?
The Marin Software 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 Marin Software from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Marin Software?
The blueprint ships with mappings for generate_lead, page, purchase. Any event in your schema can be mapped to Marin Software through pipeline configuration without a code change.
Do I need to keep the Marin Software 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 Marin Software deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Marin Software server-side?
See how Datafly Signal delivers first-party events to Marin Software from infrastructure you control, with hashed identity and consent enforcement built in.