If you're sending CRM events to LeadJourney using webhooks or Zapier, it's important to ensure that you're only sending data when a valid CLICKID is present.
Without a CLICKID, LeadJourney cannot match the conversion to a tracked session—and this will trigger errors in your logs.
🧠 Why a CLICKID Might Be Missing
A CLICKID is only created when a lead visits your website and is tracked by the LeadJourney Tracking Script.
Here are common situations where a lead won’t have a CLICKID:
The contact was added manually in your CRM (e.g. through a sales call or import)
The lead came from a non-website channel (e.g. offline lead, cold call, trade show)
You’ve just started using LeadJourney and are sending historic CRM data from before tracking was installed
✅ How to Prevent Errors
To avoid webhook or Zapier errors, add a filter to your automation flow:
🛠️ In Zapier:
Add a Filter step before your Webhook action:
Condition:
CLICKID→Exists(or)Is Not Empty
This ensures that only leads who were actually tracked on your website are sent to LeadJourney.
⚙️ In Custom Webhook Setups:
Add a simple check in your backend or automation tool:
javascriptKopierenBearbeitenif (lead.click_id && lead.click_id.trim() !== '') { // Send POST request to LeadJourney }🚀 Best Practices
Always verify the
CLICKIDexists before sending dataAvoid sending legacy data without valid tracking context
Make sure your webhook/Zap only handles leads that came through your website
This keeps your integration clean and ensures that LeadJourney only receives accurate, matchable conversion data.
💬 Need help setting this up in your CRM or automation platform?
Just message us via the live chat in the bottom-right corner—we’re happy to help!