Recover GCLID for Velocify→Encompass lead attribution (Zapier/Make playbook)
Lost paid-search attribution in your Velocify–Encompass handoff? This playbook shows how to recover GCLID and fire offline conversions with Zapier or Make.
TABLE OF CONTENTS
If your ads are generating leads but you can’t tie closed revenue back to the click, it usually comes down to one missing field: the GCLID (Google Click ID). In Velocify→Encompass handoffs, that value often gets dropped during the API push—so conversions can’t be attributed, budgets can’t be optimized, and revenue reporting becomes a guessing game.
This playbook shows a practical way to recover the GCLID from Velocify and then fire conversions when Encompass hits key milestones (e.g., Locked and Closed) using either Zapier or Make.
Why GCLID gets lost in Velocify → Encompass
Most “lost attribution” problems are not a marketing tracking issue—they’re a field-mapping and system-boundary issue.
Common reasons the GCLID disappears:
- The website captures GCLID, but the form/CRM mapping stores it in a custom field that isn’t included in the Velocify→Encompass payload.
- The Velocify integration is SOAP-based and the Encompass side is REST-based, so the “default” connector only carries a limited set of fields.
- There’s no reliable “feedback loop” from Encompass back to Velocify once the loan progresses—so even if marketing has the click ID, sales/ops never sends milestone events back.
The high-level fix (architecture)
You’ll build a small “attribution bridge” that does two things:
- Store and preserve the click ID early (Velocify is the source of truth for GCLID).
- Trigger milestone conversions later (Encompass is the source of truth for deal status), while looking up the GCLID when you need it.
Event flow
- Lead hits website (GCLID captured)
- Form submits → Velocify lead created (GCLID stored in Velocify custom field)
- Lead gets pushed into Encompass (GCLID may be dropped)
- Encompass status changes to Locked or Closed
- Automation runs:
- Find the matching Velocify lead (via a shared “unifying lead ID”)
- Pull the GCLID from Velocify
- Send conversion event(s) downstream (Google Ads and/or GA4)
- (Optional) update Velocify status so marketing automation stays aligned
Step 0: Confirm the “unifying lead ID” (required)
Before you build anything, confirm there is one identifier you can use to match records across systems.
You need a field that exists in both systems, such as:
- Velocify Lead ID stored in Encompass as a custom field
- Encompass Loan ID stored in Velocify
- A shared external ID generated at form submit (best practice)
If there isn’t a shared ID, your automation will devolve into fuzzy matching (email/phone/name), which is fragile and risky.
Step 1: Verify where GCLID is stored in Velocify
Checklist:
Confirm the Velocify custom field name that stores GCLID
Confirm the field is writable from the form or web capture step
Confirm the Velocify API can read that custom field (including via list/search endpoints)
Tip: Treat GCLID as sensitive operational data—log it only where needed and avoid copying it into too many systems.
Step 2: Decide which milestones become conversions
The most common approach is to track two separate milestones:
- Locked (leading indicator; helps optimize faster)
- Closed (final outcome)
Map each milestone to:
- Conversion name
- Value (Locked usually lower than Closed)
- One-time vs repeatable behavior (typically one-time per lead/loan)
Step 3: Trigger on Encompass status change
Your automation needs a reliable trigger when Encompass status changes.
Common patterns:
- Webhook out of Encompass (ideal)
- Scheduled polling (works but adds delay)
- Middleware event stream (if the org has one)
When the trigger fires, capture at minimum:
- Unifying lead ID
- New status
- Timestamp of the status change
Step 4: Look up the lead in Velocify and retrieve GCLID
In your automation (Zapier or Make):
- Search Velocify by the unifying lead ID.
- Retrieve the lead record.
- Extract the GCLID custom field.
Validation rules:
- If GCLID is empty, stop and flag for investigation.
- If multiple Velocify leads match, stop and flag for investigation.
Step 5: Send the conversion (Google Ads and/or GA4)
You have two common options:
Option A: Google Ads offline conversion import
Use this when the goal is to optimize Google Ads bidding/targeting based on downstream milestones.
Implementation notes:
- Google Ads offline conversion import typically expects GCLID and a conversion timestamp.
- If you also pass email/phone identifiers, ensure you handle empty optional fields correctly (many Zapier actions fail if a required field is blank).
Option B: GA4 measurement (event-based)
Use this when GA4 is your analytics “system of record” for reporting and experimentation.
Implementation notes:
- Standard GA4 events don’t accept GCLID as a direct parameter the same way Google Ads offline imports do.
- GA4 is still useful for funnel reporting—just be clear whether your goal is analytics or ad optimization.
Practical recommendation: In most paid search attribution projects, optimize ads in Google Ads and use GA4 as a reporting layer.
Step 6: QA checklist (don’t skip)
Attribution fixes fail most often at QA.
Data QA
Confirm the GCLID is captured on the landing page
Confirm the GCLID is stored on the Velocify lead
Confirm the unifying lead ID is present in both systems
Confirm the automation finds exactly one lead
Conversion QA
Fire a test conversion for a known GCLID
Verify the conversion is received/accepted (not rejected)
Verify the conversion shows up under the correct conversion action
Verify Locked and Closed don’t double-count
Operational QA
Add logging for “missing ID”, “missing GCLID”, and “multiple matches”
Create a lightweight exception queue (even a spreadsheet) so issues can be handled without digging through task history
Implementation blueprint (Zapier vs Make)
Use the tool that best matches the client’s constraints.
Zapier blueprint
- Trigger: Encompass status changes → Locked/Closed
- Action: Find Velocify lead by unifying ID
- Action: Send offline conversion to Google Ads
- (Optional) Action: Update Velocify lead status
Make blueprint
- Trigger: Encompass webhook / polling module
- Router: Branch on status (Locked vs Closed)
- HTTP: Fetch Velocify lead + extract GCLID
- Google Ads: Send conversion
- Data store: Log exceptions
Common pitfalls (and how to avoid them)
- No shared ID: decide the ID strategy first; don’t start building without it.
- GCLID captured too late: capture at the first touch (landing page/form), not after sales engagement.
- Blank optional fields break actions: build guardrails so empty email/phone/GCLID doesn’t hard-fail a step.
- Double-counting conversions: dedupe by lead ID + milestone.
Fix your GCLID attribution across Velocify and Encompass
If you’re losing paid-search attribution across CRM and LOS handoffs, Connex Digital can help you map the fields, build the automation, and QA the conversion flow end-to-end.
Book a free discovery call to walk through your specific Velocify and Encompass setup — we'll map the fields and show you exactly where attribution breaks.
