Does LeadJourney import my existing Podium history?

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

Connect Podium

Connect your Podium organization in minutes with no API keys to copy. Authorize once, then map contacts, messages, calls, reviews and payments onto your conversions, and write LeadJourney data back into Podium.

Connecting Podium turns contact, message, call, review and payment events into LeadJourney conversions, attributed to the campaign, ad set and ad that earned them. You authorize Podium once (no keys to copy, no webhook URLs to paste by hand), then map each Podium event onto one of your conversion types. 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 send LeadJourney clicks, conversions and leads into Podium.

Before you start

Have these ready so the connection works end to end:

An active LeadJourney workspace and a Podium organization you can sign in to and authorize apps for.
Tracking is live, so clicks are recorded before Podium events arrive. See Install the tracking script.
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 Podium card to open the integration. While you're not connected you'll see a "Connect your Podium account" card; once connected, the same screen shows your organization, locations, triggers and the Send to Podium section.

Step by step

Authorize LeadJourney from Podium

On the Connect your Podium account card, click Connect with Podium. You'll be redirected to Podium to approve LeadJourney's access, then sent back once you do.

LeadJourney requests read access to contacts, messages, reviews and payments, so it can read records and register a webhook that picks up new activity in real time. After you approve, you'll see a "Podium connected" confirmation.

Check the connection details

Once connected, the header shows a Live pill (or Needs reconnect if something breaks), your Organization, how many Active triggers you have, and Connected since. Next to the pill you'll find Re-authorize (re-run the authorization to refresh granted permissions, keeping your triggers and settings) and Disconnect.

Choose your locations

If your Podium organization has more than one location, a Locations panel appears. Podium sends events for the whole organization, so tick the locations this workspace should track: events from the others are ignored, and each lead records the location it came from. At least one location must stay selected (Keep at least one). Single-location organizations don't see this panel.

Add a trigger

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

App: Podium (already selected).
LeadJourney Event: the conversion type this Podium event should record.
Trigger: pick a Podium event from the grid (use Search triggers… to narrow it down). Each card summarizes what the delivery carries and where the contact sits, e.g. Contact at data.contact. A stub tag means the event only references the contact, so its status isn't included.

Click Continue.

Receive data and confirm the mapping

The dialog opens a three-tab flow:

Receive Data: click Find latest data to load the 3 most recent records for the event. If nothing appears, create one in Podium and try again, then select a record.
Configure Mapping: map the record onto Email, Name, Phone, click_id, Revenue and Currency. On contact events you also get Contact status, which records the contact's current Podium status on the lead. Each row can combine several paths or take a literal with static:value, and Add custom field adds more.
Filtering (optional): fire only when every filter matches. Use Add filter, or Filter by contact status on contact events to fire on one funnel stage. Statuses are read from your recent Podium contacts; if one isn't listed you can still type it.

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

How Podium records link to the right campaign

Most Podium activity (a text, a call, a webchat) doesn't carry LeadJourney's click ID, so Podium conversions are usually matched to the visitor by email or phone. Map those rows carefully on the Configure Mapping tab. If you store the click ID on your Podium records yourself, point click_id at that path for an exact match. Mapping click_id is recommended but optional.

Managing your triggers

Each trigger appears as a row (Podium 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.

Sending data to Podium

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

WRITE THIS PODIUM OBJECT: what to write, such as a contact, a message or a review invite. A short description of the object appears under the picker.
WHEN THIS HAPPENS: the LeadJourney event. For conversions you can narrow it with CONVERSION TYPE or keep Any conversion type.
PODIUM LOCATION (multi-location organizations only): which location this writes into. Default follows the connection's default location.
WRITE MODE: the modes offered depend on the object. If you choose an update, set the MATCHING FIELD that identifies the existing Podium contact.
MAP FIELDS: pick the Podium field on the left and the LeadJourney value 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 Podium.

Missing permission for an object?

If your connection was authorized before an object's write permission existed, the dialog warns that it was authorized without the required scope. Click Re-authorize in the header to grant it.

Reconnecting

If something breaks, the header flips to Needs reconnect and a banner explains why: "Podium disconnected your app" (access was revoked on Podium's side), "Webhook subscription is gone" (your access still works, but the webhook is missing) or "Podium is unreachable" (often a temporary outage). Click Reconnect to re-run the authorization.

Disconnecting

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

Disconnect deletes your triggers

Disconnecting permanently removes the Podium connection and deletes every trigger. Podium events stop flowing into your conversions immediately. You can reconnect later, but your trigger configuration won't be restored.

Troubleshooting

No records when you click “Find latest data”?

Nothing recent exists in Podium for that event yet. Create matching activity (a new contact, a message, a payment), then click Find latest data again.

Events from one location never show up?

Check the Locations panel. Events from locations that aren't ticked are ignored.

Contact status stays empty?

Only contact events carry the status. Message and call events only reference the contact (the stub tag on the trigger card), so use a contact event for status-based triggers.