Which Close records can LeadJourney write to?

Destinations in Send to Close can write Leads, Contacts and Opportunities, using the Create or Update write mode.

Do I lose my triggers when I re-authorize?

No. Re-authorize and Reconnect keep your triggers and settings. Only Disconnect deletes them.

Connect Close

Q: Does LeadJourney import my existing Close records?

No. LeadJourney tracks new Close events from the moment you connect. Data from before the connection is not imported.

Connect your Close organization in minutes, with no API keys and no webhooks to wire by hand. Authorize once, map CRM events like new leads, new contacts, new opportunities and closed-won deals onto your conversions, and push LeadJourney data back into Close.

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. The same screen also lets you send LeadJourney clicks, leads and conversions back into Close as records.

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 (or use ?slug=apps&app=close). While you're not connected you'll see a “Connect your Close organization” card; once connected, the same screen shows your organization, your triggers and the Send to Close panel.

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.

Syncing starts when you connect

LeadJourney tracks new Close events from the moment you connect. Data from before the connection is not imported.

Check the connection details

Once connected, the header shows a Live pill (or Needs reconnect if something breaks), plus Re-authorize and Disconnect buttons. Below it you'll see the Connection status, your Organization name and ID, Active triggers (active out of total) and the Connected since date.

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. Search triggers… narrows a long list.
Attribute changed (optional, on update triggers): pick a field and a Target value so the trigger only fires when that field changes to the value. Fields with a fixed set of options (e.g. a status) show a dropdown; leave Any value (or the field blank) to fire on any update.

Click Continue.

Fire only on a specific status

To fire only when an opportunity reaches a particular status, use Attribute changed on an update trigger, or 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 Find latest data to load the 3 most recent records for the event you picked. If nothing appears, create a matching record in Close and check again, then select a record and click Continue with selected record.
Configure Mapping: map the Close record onto LeadJourney columns. New triggers start with Email, Name, Phone, click_id, Revenue and Currency, pre-filled where LeadJourney finds a likely path. Add custom field adds First name, Last name or one of your workspace's custom fields, or Create new field (type Text, Number or Currency). Select several paths to join them with a space, or prefix a literal with static:. Mapping click_id is recommended but optional (see the callout below).
Filtering (optional): click Add filter and set a Path, an Operator and a Value. The trigger only fires when every filter matches the incoming record; with no filters, every matching event fires it.

Click Save & Continue to finish (Save changes when editing), or Save and continue later to keep your progress.

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: use the toggle to stop a trigger temporarily without deleting it.
Edit: change the event, condition, mapping, filters or target conversion. The URL gets a trigger_id parameter, so you can share a link that opens that trigger directly.
Delete: type delete and click Delete trigger. The mapping and filters can't be recovered; other triggers keep running.
Add another: use Add trigger again to map more Close events (new leads, contacts, opportunities, closed-won deals) onto different conversions.

Send data back to Close

The Send to Close panel pushes LeadJourney clicks, conversions and leads into Close as records, no Zapier needed. Click + Add destination, then:

Create this Close record: choose Lead, Contact or Opportunity.
When this happens: pick the LeadJourney event. For a conversion event you can narrow it with Conversion type, or leave it on Any conversion type.
Write mode: Create always creates a new record, Update only updates an existing match and skips if none is found. Close has no upsert mode.
Matching field (Update only): the Close field used to find the existing record. It must also be one of the mapped fields below. Alternatively, pick Contact email or Contact phone: LeadJourney then matches using the LeadJourney email or phone (for leads and opportunities via the linked contact), with no extra mapping needed.
Map fields: pick a Close field (or type a custom field name and click Set), then the LeadJourney value to send. Select several values to join them with a space, or type a fixed value and click Add. Find latest data shows real example values (you can filter by click ID or lead ID); + Add field adds another row.

Click Create destination. Each destination row has Pause / Resume, Edit and Delete (deleting stops new records; existing Close records are not affected). The Sync history table lists every delivery with its Status (Success, Failed or Skipped), event, object, mode, time and detail, and a Retry button for failed or skipped ones.

Reconnecting

If Close revokes the app, the webhook subscription goes missing, or Close is unreachable, the header flips to Needs reconnect and a banner explains why (e.g. “Close disconnected your app” or “Webhook subscription is gone”). Click Reconnect to re-run the authorization. To refresh granted permissions while everything still works, use Re-authorize in the header. In both cases your triggers and settings are kept.

Disconnecting

To remove Close, click Disconnect in the header, type disconnect and confirm with Disconnect Close. 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 “Find latest data”?

Nothing recent exists in Close for that event yet. Create a matching record (a new lead, contact or opportunity), then click Find latest data 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.

A destination shows Failed or Skipped deliveries?

Open Sync history and read the Detail column. Update skips when no match is found, and the matching field must also be mapped. Fix the destination, then click Retry.