Connect Close

Connect your Close organization in minutes – no API keys, no webhooks to wire by hand. Authorize once, then map CRM events like new leads, new contacts, new opportunities and closed-won deals straight onto your conversions.

Connecting Close turns CRM events – new leads, new contacts, new opportunities, closed-won deals – into LeadJourney conversions, automatically attributed to the campaign, ad set and ad that earned them. You authorize Close once (no keys to copy, no webhook URLs to paste by hand), then map each Close event onto one of your conversion types. Mapped events flow through the same postback pipeline as your offline conversions, so they automatically pick up every ad postback you've already configured.

Before you start

Have these ready so the connection works end to end:

An active LeadJourney workspace and a Close organization you can sign in to.
Tracking is live – clicks have to be recorded first so records can be matched back to a campaign. See Install the tracking script.
A way to capture the click ID on your Close records – typically a custom field on the lead or opportunity that stores LeadJourney's click ID (see the callout below).
At least one conversion type to map onto (e.g. WonClient). Set these up first in the Events Manager.

Where to find it

Open Settings → Apps, or go to app.leadjourney.io/settings?slug=apps. Click the Close card to open the integration. While you're not connected you'll see a “Connect your Close organization” card; once connected, the same screen shows your organization and triggers.

Step by step

Authorize LeadJourney from Close

On the Connect your Close organization card, click Connect with Close. You'll be redirected to Close to sign in and approve LeadJourney's access.

The grant gives API access to your leads, opportunities and contacts, plus offline access so LeadJourney can read records and register a webhook subscription to pick up changes in real time – there are no keys to copy and no webhook URLs to paste. After you approve, Close sends you back and you'll see a “Close connected” confirmation.

Check the connection details

Once connected, the header shows everything at a glance: a Live pill (or Needs reconnect if something breaks), your connected organization, how many triggers are active, and the date you connected. A Disconnect button lives in the same header for later.

Add a trigger

In the Triggers panel – “Each trigger maps a Close record event to one of your conversions.” – click Add trigger. In the New Close trigger dialog:

App – Close (already selected).
LeadJourney Event – pick the conversion type this Close event should record, e.g. WonClient. (No options? Create one under Settings → Events first.)
Trigger – choose the Close event that should fire it, such as a new lead, a new contact, a new opportunity or a closed-won deal.

Click Continue.

Fire only on a specific status

To narrow an opportunity event further – for example, fire only when an opportunity reaches a particular status – add a condition on the Filtering tab (e.g. status equals Won).

Receive data and confirm the mapping

The dialog opens a three-tab flow:

Receive Data – click Check for data to load the most recent records for the event you picked. If nothing appears, create a matching record in Close and refresh, then select a record to map against.
Configure Mapping – map the Close record onto LeadJourney columns – Email, Name, Phone, click_id, Revenue and Currency – using Add custom field for anything extra. Mapping click_id is recommended but optional (see the callout below).
Filtering (optional) – add conditions so the trigger only fires for matching records.

Click Save & Continue to finish.

How Close records link to the right campaign

Close doesn't capture LeadJourney's click ID on its own – you store it on the record and map it here. The usual setup is a custom field on the lead or opportunity that holds the visitor's click ID. On the Configure Mapping tab, point click_id at that field (or use a static: value for testing) so every record arrives already tied to the click – and therefore the campaign, ad set and ad – that earned it. No click ID? LeadJourney falls back to matching on email or phone.

Managing your triggers

Each trigger appears as a row – Close event → conversion type – with an Active / Paused pill and a summary of how many fields and filters it uses.

Pause / Resume – temporarily stop a trigger without deleting it.
Edit – change the mapping, filters or target conversion.
Delete – remove a single trigger; others keep running.
Add another – use Add trigger again to map more Close events (new leads, contacts, opportunities, closed-won deals) onto different conversions.

Reconnecting

If Close revokes the app, the webhook subscription goes missing, or Close is unreachable, the header flips to Needs reconnect and shows a banner explaining why. Click Reconnect to re-run the authorization – your triggers stay in place.

Disconnecting

To remove Close, click Disconnect in the header and type disconnect to confirm. This is deliberate because it's destructive:

Disconnect deletes your triggers

Disconnecting permanently removes the Close connection, deletes every trigger and revokes the webhook subscription. Close events stop flowing into your conversions immediately. You can reconnect later, but your trigger configuration won't be restored – you'll set them up again.

Troubleshooting

No records when you click “Check for data”?

Nothing recent exists in Close for that event yet. Create a matching record – a new lead, contact or opportunity – then click Check for data (or Refresh sample) again. The record should appear so you can finish the mapping.

Records come in but aren't attributed to a campaign?

LeadJourney needs to know which click the record belongs to. Check that (1) the tracking script is installed and recording clicks, (2) your records carry the click ID in a custom field and the trigger maps click_id to it, and (3) the trigger is Active. As a fallback, email or phone can be used to match.

Header shows “Needs reconnect”?

Close has revoked the grant, the webhook is gone, or the API is unreachable. Click Reconnect in the banner to re-authorize. Your triggers are preserved.