Close

OVERVIEW

A native Close integration — no Zapier in the middle

The Close integration uses OAuth and a webhook subscription LeadJourney registers and manages on your Close organization automatically. Approve Close, pick the trigger, map a few fields — and from that moment, every Lead Created, Lead Updated, Opportunity Created, Opportunity Updated, or Contact Created event in Close arrives in LeadJourney within a second, stitched back to the original visitor journey and forwarded to Meta CAPI, Google Ads, LinkedIn, TikTok, and Bing as a server-side conversion. No middleware, no API keys, no engineers.

USE CASES

What you can do with Close and LeadJourney

Six things that go from "needs an engineer and a Zapier seat" to "configured in five minutes" the moment you connect Close.

1. 01

   One-click OAuth — no engineers, no API keys

   Connect from LeadJourney's Integrations page and approve your Close organization. No API keys to paste, no webhook secret to rotate, no Zapier seat to buy.

2. 02

   Native real-time webhook

   LeadJourney auto-registers a webhook subscription on your Close organization the moment you save a trigger. Events arrive in 1–2 seconds — no polling, no batching delay.

3. 03

   Leads, Contacts, and Opportunities — any object that matters

   Track Lead Created, Lead Updated, Opportunity Created, Opportunity Updated, and Contact Created. Build separate triggers: Lead Created → Lead, Opportunity won → WonClient, Contact Created → Contact.

4. 04

   Map any Close field — including custom fields

   The mapping UI fetches a live sample record so you can pick field paths — email, name, phone, opportunity value, and any custom fields — from a dropdown with the resolved sample value shown inline.

5. 05

   Filter to only the events that matter

   Add filters like "only fire when status_type = won" to capture closed-won revenue, or "only when lead_source = Paid", so you don't pollute your conversion stream with every status flip.

6. 06

   Server-side forwarding to every ad platform

   The same Close event lands in Meta CAPI, Google Ads, LinkedIn, TikTok, and Bing — server-to-server, so iOS 14.5+, ad blockers, and cookie loss don't touch it.

WHY IT MATTERS

Close shows you the pipeline. LeadJourney shows you which ads built it.

Close is built for high-velocity inside-sales teams who live in the CRM all day — but nothing in Close knows which Meta or Google campaign produced the lead that just turned into a won opportunity. Without that link, your ad algorithms optimise for form-fills and your CAC numbers are guesses dressed up as dashboards. LeadJourney closes the loop server-side: every lead, contact, and opportunity event in Close is matched back to the click that originally created the lead, then forwarded to your ad platforms as a real conversion. Filter the Opportunity Updated trigger to status_type = won and your ad platforms optimise toward closed-won revenue — not raw leads.

COMPARISON

Close alone vs Close with LeadJourney

Same CRM. Two very different views of what your paid acquisition is actually closing.

HOW TO CONNECT

Live in minutes

One OAuth approval, one trigger, one field map. No middleware, no developer, no API tokens to rotate.

1. 01

   Setup Step 1

   Open Settings → Apps → Close in LeadJourney and click Connect. You'll be redirected to Close to approve the organization you want LeadJourney to read from.

2. 02

   Setup Step 2

   Add a trigger. Pick a Close event — for example Lead Created, Opportunity Updated, or Contact Created — and the LeadJourney conversion type it should fire (Lead, WonClient, Contact, etc.).

3. 03

   Setup Step 3

   Check for data. On the Receive Data tab, click "Check for data". LeadJourney pulls your most recent Close records so you can map against real values.

4. 04

   Setup Step 4

   Map fields. On the Configure Mapping tab, pick the Close field path for Email, Name, Phone, Opportunity Value, and any custom fields. The resolved value from your sample record shows next to each row so you can confirm before saving.

5. 05

   Setup Step 5

   (Optional) Add filters. On the Filtering tab, restrict the trigger to records matching specific criteria — for example, only fire WonClient when status_type equals "won".

6. 06

   Setup Step 6

   Save. LeadJourney registers the webhook in Close automatically. Update a matching record in Close — the conversion lands in LeadJourney within seconds and is forwarded to every ad platform you've connected.

FAQ

Frequently asked questions about Close

Quick answers about how the native Close ↔ LeadJourney integration works under the hood.