Does LeadJourney import my existing Patch data?

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

Connect Patch Retention

Connect Patch Retention with an API token, turn purchases, check-ins, bookings and form submissions into attributed conversions, and push LeadJourney guests and events back into Patch.

Connecting Patch Retention turns Patch purchases, check-ins, bookings, contacts and form submissions into LeadJourney conversions, attributed to the guest by click ID where you have one and by email or phone otherwise. Patch has no OAuth, so you connect with an API token. Mapped events flow through the same postback pipeline as your offline conversions, so they pick up every ad postback you've already configured. You can also push LeadJourney guests and events back into Patch, for example to start a thank-you automation.

Before you start

Have these ready so the connection works end to end:

An active LeadJourney workspace and access to your Patch account's Settings.
Your Patch API token, found in Patch under Settings → API Access.
Tracking is live, so clicks are recorded before guests convert. See Install the tracking script.
At least one conversion type to map onto (e.g. Purchase). 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 Patch Retention card to open the integration. While you're not connected you'll see a "Connect your Patch account" card with a setup guide (How do I set up Patch for attribution?); once connected, the same screen shows your account, click ID field, automation URLs, triggers and the Send to Patch section.

Step by step

Connect with your API token

On the Connect your Patch account card, paste your token into Patch API token. The Click ID field key (optional) can stay blank for now; you can pick the field from your real Patch fields after connecting.

Click Connect. LeadJourney validates the token by listing the accounts it can see, and you'll see a "Patch connected" confirmation. Polling of your orders, check-ins and bookings starts straight away.

Pick your Patch account

If your token can see more than one Patch account (an operator running several venues), a Patch account panel appears. Choose the venue this workspace belongs to from Select a Patch account…. Until you do, nothing is polled and nothing converts, and everything LeadJourney reads and writes is scoped to the account you pick.

Set up the click ID field

Patch's API can read fields but not create them, so this one is on you:

In Patch, go to Settings → Fields and add a contact field called lj_click_id.
Put that field on the forms and waivers guests fill in, populated from the lj_click_id value the LeadJourney tracking script puts on the page URL.
Back in LeadJourney, choose the field in the Click ID field panel and click Save field. Just created it? Click Refresh fields to re-read the list from Patch.

If you skip this, choose Don't use a click ID field: conversions still land and are matched to the guest by email or phone, which is how most venue traffic arrives anyway.

Build one Patch automation per event

Patch has no webhook settings to fill in. The Automation URLs panel lists one URL per event. For each event you want to convert, build an automation in Patch: trigger it on that event, end it with an HTTP Request action block, set the method to POST and paste the matching URL.

Copy the Request body from the same panel into the block's parameters and replace each value with the matching Patch field. Only the contact ID is required, because LeadJourney reads the rest of the guest's details from Patch.

Events marked polled are also read from Patch's API every ten minutes, so they convert even without an automation; the automation just makes them immediate. The rest have no API event, so an automation is the only way they reach LeadJourney. Click Pull now to fetch recent orders, check-ins and bookings right away; the header shows the Last pull time.

Add a trigger

In the Triggers panel ("Each trigger maps a Patch event to one of your conversions.") click Add trigger. In the New Patch trigger dialog:

App: Patch (already selected).
LeadJourney Event: the conversion type this Patch event should record.
Trigger: pick a Patch event from the grid (use Search triggers… to narrow it down).

Click Continue.

Receive data and confirm the mapping

The dialog opens a three-tab flow:

Receive Data: click Find latest data to load the most recent records for the event, then select one. If nothing exists yet, create a test record in Patch first, or type the field names on the next tab.
Configure Mapping: map the record onto Email, Name, Phone, click_id, Revenue and Currency. Guest details sit under contact. (e.g. contact.email), and the click ID arrives as lj_click_id, filled from your click ID field. Rows can combine several paths or take a literal with static:value; Add custom field adds more.
Filtering (optional): click Add filter to fire only when every filter matches the incoming record.

Click Save & Continue to finish, or Save and continue later to keep a draft.

How Patch guests link to the right campaign

Guests reach a venue through waivers, kiosks and the POS as often as through a web form, so Patch conversions match on email or phone by default. For click-level attribution, fill lj_click_id on the contact and map click_id from lj_click_id on the Configure Mapping tab. Every conversion then ties back to the exact ad click, and therefore the campaign, ad set and ad.

Managing your triggers

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

Pause / Resume: use the switch to stop a trigger temporarily without deleting it.
Edit: change the event, mapping, filters or target conversion.
Delete: type delete to confirm. Other triggers keep running.

Pushing guests and events back into Patch

The Send to Patch section writes LeadJourney clicks, conversions and leads into Patch. Click + Add destination and set:

CREATE THIS PATCHRETENTION RECORD: Contact or Event (purchase, check-in, booking). Writing an event is how a LeadJourney conversion can start an automation in Patch.
WHEN THIS HAPPENS: the LeadJourney event. For conversions you can narrow it with CONVERSION TYPE or keep Any conversion type.
WRITE MODE: Create or update (update the matching guest, or create them), Update only (contacts only; skip if the guest doesn't exist) or Create (events only; record the event against a guest Patch already has).
MATCHING FIELD: always required, because every Patch write is attached to a guest. It must also be one of the mapped fields.
MAP FIELDS: pick the Patch field on the left and the LeadJourney values on the right. Click Find latest data to see real example values, or type a fixed value.

Click Create destination. The Sync history table lists every delivery with its status (Success, Failed, Skipped), and failed or skipped ones can be sent again with Retry. Deleting a destination doesn't affect records already in Patch.

Reconnecting

If something breaks, the header flips to Needs reconnect and a banner explains why: "Patch rejected your API token" (the token was rotated or revoked), "Pick a Patch account" (choose one in the account panel) or "Patch is unreachable" (often a temporary outage). Click Reconnect, or Update API token in the header, to enter a fresh token. Your triggers and settings are kept.

Disconnecting

To remove Patch, click Disconnect in the header and type disconnect to confirm.

Disconnect deletes your triggers

Disconnecting permanently removes the Patch connection, deletes every trigger and drops the stored API token. Patch events stop flowing into your conversions immediately. You can reconnect later, but your trigger configuration won't be restored. Remove the automations you built in Patch if you no longer need them.

Troubleshooting

Nothing converts after connecting?

Check for a Pick a Patch account banner and choose your venue. Then confirm the trigger is Active and, for events that aren't polled, that the Patch automation posts to the right URL.

“Patch has no field with the key …”?

The click ID field you entered doesn't exist in that Patch account. Create it under Settings → Fields in Patch, click Refresh fields, then pick it and click Save field.

A purchase or check-in shows up late?

Without an automation, polled events are read every ten minutes. Click Pull now to fetch them immediately, or add the automation for real-time delivery.