Offline conversion tracking that optimises ads on deals, not form fills.

Anything that happens away from the browser and matters to the business: a lead marked qualified, a call booked, a phone call taken, a proposal accepted, an opportunity opened, a deal closed won. In LeadJourney each of those is a CRM stage or an event from a connected tool, and you choose which of them go back to which platform and which carry a value. A disqualified lead can be kept out of the signal on purpose.

Google Ads matches an imported conversion on the gclid, the click ID it appends to your landing page URL when auto-tagging is on. LeadJourney stores that gclid first-party at the click. When the mapped CRM stage changes, it imports a conversion against that gclid with the conversion action name, the conversion time, the value and the currency, server to server. Google's click-through window for imported conversions can be set up to 90 days, so the click ID has to be kept at least that long, which is why LeadJourney keeps it for months. A lead that came in without a gclid goes back through enhanced conversions for leads instead, matched on hashed email and phone from the CRM record.

Through the Conversions API. LeadJourney sends an event with the name your stage maps to (Lead, Schedule or Purchase), the event time, the fbclid captured at the click, hashed email and phone from the CRM record, and the deal value with its currency. A shared event ID means a pixel that is still running does not count the same lead twice. Meta accepts an event up to seven days after it happened, which is one reason the sync runs on the stage change and not as a monthly batch.

No. The CSV template is the manual version of the same thing: a gclid, a conversion name, a time and a value per row, exported from the CRM and uploaded to Google Ads or Microsoft Ads by hand. LeadJourney reads the stage change from HubSpot, Pipedrive, Close or Attio natively, from Salesforce and 100+ others by webhook, Zapier, Make or n8n, and sends the conversion itself. The guide to tracking offline conversions walks through both ways.

In LeadJourney the journey has no window: the deal is credited to the click that started it whatever the cycle length, and the report matches revenue to the ad. The platforms apply their own windows to what they receive (up to 90 days after the click on Google Ads, LinkedIn and Microsoft Ads, seven days on Meta's default click attribution), so a very late deal mainly improves optimisation and audience quality there rather than the platform's own conversion count. Sending the earlier stages, qualified and opportunity, is what gives the platform a signal inside its window.

Yes. A call through LeadJourney's call tracking is matched to the click that produced it, and a meeting booked in Calendly arrives as an event on the same lead. Both can be mapped to a conversion the same way a CRM stage is, so the campaign that makes the phone ring stops reporting zero conversions in the ads manager.

No. Events sent to Meta carry a shared event ID, so a conversion the pixel also saw is counted once in Events Manager. On Google Ads the imported conversions are their own conversion actions, separate from your website conversion actions, so you decide which of them count toward bidding, and the closed deal never duplicates the form submit unless you map it to the same action.

Identifiers are hashed before they leave, you control which stages and which fields are in scope, and nothing is sent that you have not mapped. Tracking is first-party and consent-aware, LeadJourney is hosted in Frankfurt, and a data processing agreement is part of every plan. The GDPR and security pages list the controls in detail.