Skip to main content

5.5 How to send CRM sales data using webhooks with any CRM

Jonas Strambach avatar
Written by Jonas Strambach
Updated over 3 weeks ago

Once you've added your offline conversions inside your LeadJourney account, the next step is to ensure your CRM sends the right sales data to LeadJourney — and the most effective way to do this is through webhooks.

Webhooks allow your CRM to automatically notify LeadJourney when key sales events happen (like a lead becoming qualified or a deal being closed), so that these events can be tracked, reported, and sent back to ad platforms.


✅ What You’ll Need

  • At least one offline conversion set up in LeadJourney (e.g. Lead, QualifiedLead, WonClient)

  • A CRM that supports sending webhooks (either natively or via tools like Zapier or Make.com)

  • The Webhook URL provided by LeadJourney for each offline conversion


🔧 1. CRM Webhook Support

Most modern CRMs support webhook functionality. However:

  • Some platforms may require a Pro/Enterprise subscription tier

  • Others may only allow it via integrations like Zapier, Make, or custom API scripts

✅ CRMs known to support webhooks:

  • HubSpot (via workflows)

  • Salesforce

  • Zoho

  • Pipedrive

  • HighLevel

  • Custom-built CRMs

  • Airtable + automation tools

💬 If your CRM doesn’t support native webhooks, LeadJourney still works via Zapier or Make.com.


⚙️ 2. Define the Right Triggers in Your CRM

Before setting up the webhook, determine what should trigger the event.

Common examples:

  • Qualified Lead → When a custom field is updated to "Qualified"

  • Sales Call Booked → When a calendar link is triggered or status changes

  • WonClient → When a deal is moved to “Closed Won” stage

To do this, you’ll need to:

  • Use deal stages, custom fields, or statuses to track sales progress

  • Define clearly what counts as a conversion event

  • Ensure those fields or stages are consistently filled by your sales process


📤 3. Send the Webhook to LeadJourney

Each offline conversion in LeadJourney has a dedicated Webhook URL.

You’ll find it here:


LeadJourney Dashboard → Settings → Offline Conversions → [Your Conversion]

What your webhook must send:

At minimum, the following field is required:

{ "clickid": "lj-d3751853-8de7-4ecd-990f-c6cc7d7b81bd" }

Optionally, you can include for "WonClient" conversions.

{ "clickid": "...", "value": 2000 }

This data should be POSTed to the Webhook URL when your CRM trigger fires.


🧪 Example: HubSpot via Workflow

  1. Go to Automation → Workflows

  2. Choose a workflow based on a Contact, Deal, or Company

  3. Add a trigger (e.g., Deal Stage = "Closed Won")

  4. Add a "Webhook" action

  5. Paste your LeadJourney Webhook URL

  6. Set method to POST

  7. Add JSON payload with the clickid from a contact property

  8. Save & activate the workflow

💡 Make sure the Click ID exists on the object (e.g., Contact or Deal) at the time of the webhook.


✅ Final Checklist

  • Offline conversions are defined in LeadJourney

  • CRM contains the Click ID in the correct object (Lead, Contact, or Deal)

  • Trigger conditions are clearly defined (e.g., deal stage, custom field)

  • Webhooks are sending clickid and optional values

  • Workflow or automation has been tested


🧠 Summary

Sending sales data from your CRM to LeadJourney via webhooks enables:

✅ Full-funnel attribution
✅ Offline conversion syncing with Meta and Google Ads
✅ Smarter campaign optimization based on real outcomes

Don’t let your most valuable conversion events go untracked.


👉 Need help setting up your CRM or testing webhooks? Our support team is ready to help!

Did this answer your question?