Integrations / CRM
Outreach
Server-to-server prospect creation in Outreach via the v2 REST API (JSON:API). Identity-bearing events (Lead Submitted, Signed Up, Demo Requested, Form Submitted) become Outreach Prospect records with email, name, company, title, phone (E.164), location, and tags. Email/name/phone are sent in the clear because Outreach is a first-party CRM that dedupes on email. Analytics-only events (page, product funnel) are dropped — Outreach has no event ingestion API.
Datafly Signal delivers first-party events to Outreach server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Outreach expects.
Why route Outreach through Datafly Signal
Profiles update from the server, not the browser
Events reach Outreach even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Token lifecycle is handled for you
Signal obtains and refreshes the OAuth credentials Outreach requires, so nothing expires quietly in the middle of a campaign.
One consent decision governs every destination
Outreach 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
demo_requestedgenerate_leadsign_upVertical presets
Lead Capture. 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 Outreach documentation.
Frequently asked questions
Does Datafly Signal integrate with Outreach?
Yes. Datafly Signal delivers first-party events to Outreach server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Outreach expects. The integration is included in every deployment at no additional cost.
How is server-side Outreach tracking different from the Outreach tag?
The Outreach 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 Outreach from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Outreach?
The blueprint ships with mappings for demo_requested, generate_lead, sign_up. Any event in your schema can be mapped to Outreach through pipeline configuration without a code change.
Do I need to keep the Outreach tag on my site?
No. Signal delivers to Outreach from the server, so no client-side Outreach script is required on your site.
Ready to move Outreach server-side?
See how Datafly Signal delivers first-party events to Outreach from infrastructure you control, with hashed identity and consent enforcement built in.