CRM sync
Send conversions and hot leads, with how each person found you, to your CRM through a signed webhook.
When a real person converts or becomes a hot lead, WysLeap can post a short summary of them to a webhook: where they first came from, how many times they visited, the pages they read, and what they did. Point the webhook at a Zapier, Make or n8n catch hook (or your own server) and write the summary onto the matching CRM contact.
WysLeap sends people, not traffic. Anonymous page views are never sent, and WysLeap never creates CRM contacts on its own. Your workflow decides what to do with each summary.
Before you start
-
Add the visitor ID to your forms, so your CRM can match the summary to the contact who filled in the form (see below). If your visitors sign in, Known People works too.
-
Update your consent banner and privacy policy. CRM sync uses the
activationconsent purpose. In the EU/EEA, UK and Switzerland, a visitor is only sent after they agree to it. For example:Marketing: we share how you found and used our site with our sales tools, so we can follow up on your request.
Elsewhere, visitors are sent unless they turned activation off or their browser sends Global Privacy Control. Check the wording with your privacy advisor.
Connect a webhook
- In WysLeap, open your site and go to CRM sync. Site owners and editors can set it up.
- Paste your catch hook URL and select Connect. It must be
https://. - Copy the signing secret. It's shown once. You can make a new one later with Rotate secret.
- Select Send test. A sample summary with
"test": truearrives at your hook, so you can map its fields. - Select Preview to see who the last 7 days would have sent, and why anyone was held back. Nothing is sent.
- Confirm the consent statement and select Start syncing. Past conversions aren't sent; only new ones from that moment.
WysLeap checks for new conversions and hot leads every 10 minutes and waits 2 minutes after each one, so bot scoring has settled. Expect a summary within about 12 minutes.
Match form submissions
Add a hidden field named wysleap_visitor_id to any form that feeds your CRM:
<form action="/contact" method="post">
<input type="hidden" name="wysleap_visitor_id" />
<!-- your fields -->
</form>The WysLeap script fills it in with the visitor's ID, including on forms added after the page loads. It stays empty for visitors who haven't consented, opted out or are measured without consent (exempt measurement).
Store the field on the CRM contact. In your workflow, find the contact whose wysleap_visitor_id equals visitor.id (or any of visitor.ids) and update it.
Who is sent
A conversion or hot lead is sent only when all of these hold:
- A real person. Bots, and visitors who are mostly bot traffic, are held back.
- Not you. Visitors you marked as internal in site settings are held back.
- Consented. See the consent rule above. Exempt-measurement visitors are never sent.
- Once. Each conversion and hot lead is sent once. Use
idto drop repeats if your receiver retries.
Each person is sent under their own device ID, plus the browsers they signed in on with Known People. Browsers WysLeap only estimated belong to the same person are never sent.
The CRM sync page shows how many were sent and how many were held back for each reason over the last 7 days.
What is sent
{
"id": "conversion:6b027700d6d813d4e561b259",
"type": "wysleap.conversion",
"version": 1,
"createdAt": "2026-11-22T05:11:35.140Z",
"site": { "id": "acme-com" },
"visitor": {
"id": "vis_53nu4ivt5tfx6np0tu1ed",
"ids": ["vis_53nu4ivt5tfx6np0tu1ed"],
"identityBasis": "device",
"firstSeen": "2026-04-25T19:38:51.000Z",
"firstSource": "google.com",
"firstMedium": "organic",
"firstCampaign": null,
"firstLandingPage": "/blog/pricing-guide",
"latestSource": "chatgpt.com",
"aiReferrer": "ChatGPT",
"visits": 6,
"pageviews": 21,
"keyPages": ["/pricing", "/contact", "/services"],
"country": "US"
},
"event": {
"name": "contact_form_submit",
"at": "2026-11-22T05:00:48.481Z",
"page": "/contact",
"daysToConvert": 12,
"properties": { "formType": "Demo" }
},
"links": {}
}| Field | Meaning |
|---|---|
type | wysleap.conversion or wysleap.hot_lead |
visitor.identityBasis | authenticated (signed in with Known People) or device |
visitor.firstSource, firstMedium | How they first found you. Medium is ai, organic, referral, none (direct) or your utm_medium |
visitor.aiReferrer | The AI assistant that sent them, if any |
visitor.keyPages | Their most-read pages (for hot leads, the pages that made them a lead) |
event.page | The page they converted on |
event.properties | Short values from the event, such as formType. Anything that looks like an email, phone number, name, address or message is left out |
hotLead | For hot leads: score, level, reason, discoveredAt |
links.hotLeads | For hot leads: the Hot leads page in WysLeap |
No IP address, raw page view list, email or name is ever sent.
Check the signature
Every request carries an X-WysLeap-Signature header: t=<unix seconds>,v1=<hex HMAC-SHA256>, signed over "<t>.<raw body>" with your secret. Check it against the raw request body, before parsing:
import crypto from "node:crypto";
function verify(rawBody, header, secret) {
const parts = Object.fromEntries(header.split(",").map((p) => p.split("=")));
if (Math.abs(Date.now() / 1000 - Number(parts.t)) > 300) return false;
const expected = crypto
.createHmac("sha256", secret)
.update(`${parts.t}.${rawBody}`)
.digest("hex");
const a = Buffer.from(expected);
const b = Buffer.from(parts.v1 || "");
return a.length === b.length && crypto.timingSafeEqual(a, b);
}Zapier and Make can't check signatures on their own; keep the catch hook URL private, or put a small checking step in front.
Delivery and retries
- Reply with any
2xxwithin 10 seconds. - Failures are retried after 1 minute, 5 minutes, 30 minutes, 2 hours and 12 hours, then marked failed. Retry them from the CRM sync page.
429waits 5 minutes before trying again.410 Gonepauses the connection until you resume it.- Pause stops sending; Disconnect deletes the connection and its history.