Integrations / CRM
Close
Server-side lead capture into Close CRM. Identified lead, sign-up and demo-request events create a Close Lead with a nested Contact (name, email, phone, title) via the Close REST API (POST /api/v1/lead/). PII is sent unhashed because Close stores the real contact record; delivery is gated on marketing consent at the pipeline level. Lead name falls back from company to contact name to email so the lead is never created nameless.
Datafly Signal delivers first-party events to Close server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Close expects.
Why route Close through Datafly Signal
Profiles update from the server, not the browser
Events reach Close even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
One consent decision governs every destination
Close 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
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 Close documentation.
Frequently asked questions
Does Datafly Signal integrate with Close?
Yes. Datafly Signal delivers first-party events to Close server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Close expects. The integration is included in every deployment at no additional cost.
How is server-side Close tracking different from the Close tag?
The Close 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 Close from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Close?
The blueprint ships with mappings for demo_requested, generate_lead, sign_up. Any event in your schema can be mapped to Close through pipeline configuration without a code change.
Do I need to keep the Close tag on my site?
No. Signal delivers to Close from the server, so no client-side Close script is required on your site.
Ready to move Close server-side?
See how Datafly Signal delivers first-party events to Close from infrastructure you control, with hashed identity and consent enforcement built in.