Podium attribution, wired in minutes, from first touch to collected payment

Podium records the channel a conversation arrived on, which is the right answer for the Inbox and stays exactly as it is. LeadJourney answers the question before that one: which ad, search or referral brought the person to your website before they opened the webchat, what it cost, and how much the payment Podium collected is worth against that spend. The two sit on the same contact, so a report can show both the acquisition channel and the channel the conversation came in on.

Yes, and it is the case the integration is built for. The LeadJourney script tracks every visit on the pages where the webchat sits, so the ad click, the organic session and the click ID are already recorded when the person types their name and number. The contact is stitched to that journey the moment the webchat starts, and source, campaign and ad are written onto it automatically.

They still count. Podium records them and LeadJourney reads them, so they appear in the lead overview under the channel Podium gives them, and their payment is reported like any other. What they do not have is a web journey, because there was none to track. A call tracking integration such as CallRail adds the call itself to the journey, with the number the caller dialled.

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 campaigns and reports can key off, the ad spend attributed to the lead, 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 and tags are left untouched, so the reports you already run stay comparable.

Yes, and it is the point of the integration. A won lead and a collected payment are 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 amount attached so value based bidding has a real number to optimise against. A refund takes the revenue back out. Events reach LeadJourney as they happen rather than in a nightly batch, and Transparent Logs show each conversion that was sent and when.

Yes. Every location in your Podium account can sit in one LeadJourney workspace, reported on its own and rolled up, and each one can be mapped to its own ad accounts so the payment collected in one branch goes back to the campaign that branch paid for.

Yes. The journey in LeadJourney has no attribution window, so the payment is credited to the campaign and ad that started the conversation however long the quote took to close. The ad platforms apply their own windows to the events they receive, so a late payment mainly improves their optimisation; the report that matches revenue to the ad lives in LeadJourney and on the Podium contact.

No. Connecting Podium 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 your GTM container, next to the webchat you already have, 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. Financial, legal and other regulated industries are a core part of our customer base.

The Podium 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.