Patch Retention attribution, wired in minutes, from first touch to repeat order

Patch credits an order to the text or email sent before it, which is the right answer for the retention side and stays exactly as it is. LeadJourney answers the question before that one: which ad, search or referral made the person a contact, what it cost, and how much every order since is worth against that spend. The two sit on the same contact, so a report can show both the acquisition channel and the campaign that drove each order.

With LeadJourney, yes. Every visit is tracked server-side before the contact exists, the first click is stitched to the contact at form submit or at checkout, and source, campaign and ad are written onto the contact automatically. From then on every order Patch records, first and repeat, is credited to the journey that started it as well as to the message that preceded it.

On the contact: first and last touch channel, source and campaign, the ad, ad set and creative, every UTM parameter, the click ID from each platform, the landing page and referrer, the acquisition channel as a field your segments can key off, the ad spend attributed to the first order, and a link to the full journey. You choose which of those are in scope before anything is written.

No. Nothing is written to a field you have not mapped, and the direction of every mapping is yours to set. By default attribution goes to dedicated LeadJourney custom fields, and your existing fields, segments and automations are left untouched, so the reports you already run stay comparable.

Every order. The first order is sent to Meta through the Conversions API, to Google Ads as an offline conversion import matched on gclid, to LinkedIn through the Conversions API and to Microsoft Ads matched on msclkid, with the order value attached. Each repeat order follows as a further purchase event with its own value, so value based bidding learns which ads bring customers who come back rather than customers who buy once.

As it happens. An order Patch records, a contact opting in, a refund, each reaches LeadJourney straight away and fires the matching conversion to the platform that produced the click. Transparent Logs show every event that was sent and when.

Yes. The journey in LeadJourney has no attribution window, so a repeat order in month nine is credited to the ad that brought the customer in month one, and the report shows revenue per acquisition channel growing over time. The ad platforms apply their own windows to the events they receive, so a late order mainly improves their optimisation; the report that matches lifetime revenue to the ad lives in LeadJourney and on the Patch contact.

LeadJourney reads the orders Patch holds, whichever store, checkout or point of sale they came from, so nothing else has to be connected for the revenue side. If you also run Shopify or Stripe, those integrations can sit alongside and the same order is never counted twice.

No. Connecting Patch Retention is a sign in and a field mapping screen, and most accounts are live in about 21 minutes. The one line of code goes into your site or store theme, or into your GTM container, and our team will do the mapping with you on a call if you prefer.

Yes. Data is processed and stored in the EU, we sign a data processing agreement, and tracking runs first-party and server-side so it respects consent decisions rather than working around them. Opt-in and opt-out decisions stay in Patch and are read, never changed. Financial, legal and other regulated industries are a core part of our customer base.

The Patch Retention integration is part of the platform rather than a paid add on. Plans are priced on tracked events instead of seats, so your whole team and your agency can share one workspace, and every plan starts with a 14 day free trial without a credit card.