Connect Attio

Connect your Attio workspace in minutes – no API keys, no webhooks to wire by hand. Authorize once, then map CRM record events like new people, new deals, new companies and stage changes straight onto your conversions.

Connecting Attio turns CRM record events – new people, new deals, new companies, stage changes – into LeadJourney conversions, automatically attributed to the campaign, ad set and ad that earned them. You authorize Attio once (no keys to copy, no webhook URLs to paste by hand), then map each Attio 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 an Attio workspace 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 Attio records – typically a click_id attribute on your People (or Deals) object (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 Attio card to open the integration. While you're not connected you'll see a “Connect your Attio workspace” card; once connected, the same screen shows your workspace and triggers.

Step by step

Authorize LeadJourney from Attio

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

The grant gives read access to your records (people, deals, companies) and object configuration, plus read/write access for webhook subscriptions (so LeadJourney can subscribe to record changes) – there are no keys to copy and no webhook URLs to paste. After you approve, Attio sends you back and you'll see an “Attio 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 workspace, 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 an Attio event to one of your conversions.” – click Add trigger. In the New Attio trigger dialog:

App – Attio (already selected).
LeadJourney Event – pick the conversion type this Attio event should record, e.g. WonClient. (No options? Create one under Settings → Events first.)
Trigger – choose the Attio event that should fire it, such as a new person, a new deal, a new company or a stage change. The object (people, deals or companies) is set by the trigger you pick.

Click Continue.

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 Attio and refresh, then select a record to map against.
Configure Mapping – map the Attio record onto LeadJourney columns – Email, Name, Phone, click_id, Revenue and Currency – using Add custom field for anything extra. On Deal triggers, prefix paths with person. to pull from the associated person. Mapping click_id is recommended but optional (see the callout below).
Filtering (optional) – add conditions so the trigger only fires for matching records. This is also where you pin a stage, e.g. only fire when stage equals Won.

Click Save & Continue to finish.

How Attio records link to the right campaign

Attio 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 click_id attribute on your People (or Deals) object that holds the visitor's click ID. On the Configure Mapping tab, point click_id at that attribute and 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 – Attio 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 Attio events (new people, deals, companies, stage changes) onto different conversions.

Reconnecting

If Attio revokes the app, the webhook subscription goes missing, or Attio 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 Attio, 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 Attio connection, deletes every trigger and revokes the webhook subscription. Attio 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 Attio for that object yet. Create a matching record – a new person, deal or company – 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 click_id attribute 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”?

Attio 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.