Integrations / Attribution
Dreamdata
Server-side B2B revenue-attribution tracking via the Dreamdata Events API (Segment tracking spec). Delivers page, track, and identify events to https://api.dreamdata.cloud/v1/batch with first-party anonymousId/userId identity stitching, raw email/name traits, campaign attribution, and IP/User-Agent context. No PII hashing (Dreamdata stitches identity on raw traits); consent is enforced via Signal integration consent categories since the Dreamdata API has no consent field.
Datafly Signal delivers first-party events to Dreamdata server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Dreamdata expects.
Why route Dreamdata 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 Dreamdata optimises against are not filtered by the browser.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what Dreamdata needs to attribute the event to the right session.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Dreamdata rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Dreamdata 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
content_viewedgenerate_leadloginpagesign_upsubscription_startedtrial_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 Dreamdata documentation.
Frequently asked questions
Does Datafly Signal integrate with Dreamdata?
Yes. Datafly Signal delivers first-party events to Dreamdata server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Dreamdata expects. The integration is included in every deployment at no additional cost.
How is server-side Dreamdata tracking different from the Dreamdata tag?
The Dreamdata 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 Dreamdata from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Dreamdata?
The blueprint ships with mappings for content_viewed, generate_lead, login, page, sign_up, subscription_started, trial_started. Any event in your schema can be mapped to Dreamdata through pipeline configuration without a code change.
Do I need to keep the Dreamdata 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 Dreamdata deduplicates, then remove the tag once server-side volume matches.
Other attribution integrations
Ready to move Dreamdata server-side?
See how Datafly Signal delivers first-party events to Dreamdata from infrastructure you control, with hashed identity and consent enforcement built in.