Integrations

Connect WebinarJam

Connect WebinarJam or EverWebinar with your account API key and a custom webhook, then map registrations, live attendance and replay views straight onto your conversions.

Connecting WebinarJam (or EverWebinar) turns webinar activity, such as registrations, live attendance and replay views, into LeadJourney conversions, attributed to the campaign, ad set and ad that filled the seat. WebinarJam has no OAuth, so the connection works with your account API key plus a custom webhook you paste into WebinarJam once. After that you map each WebinarJam 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.

Before you start

Have these ready so the connection works end to end:

  • An active LeadJourney workspace and a WebinarJam or EverWebinar account you can sign in to.
  • API access enabled on that account. WebinarJam grants it per account, on request (see step 1).
  • Tracking is live, so registrations can be matched back to a click. See Install the tracking script.
  • At least one conversion type to map onto (e.g. WebinarRegistration). 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 WebinarJam card to open the integration. While you're not connected you'll see a “Connect your WebinarJam account” card; once connected, the same screen shows the webhook URL, the connection details and your triggers.

Step by step

Get your WebinarJam API key

In WebinarJam (or EverWebinar), open any webinar's Integrations step → Advanced integrationAPI custom integration. If an API key is shown, copy it.

If you don't see a key, you have to request API access first, because WebinarJam approves it per account. On the LeadJourney connect card, open How do I get WebinarJam API access?: it walks you through the request and gives a recommended answer for each question on WebinarJam's request form, each with a Copy button. Replace the app URL with your own if it differs, and add your contact details when WebinarJam asks.

Paste the key and connect

On the Connect your WebinarJam account card:

  1. Platform: choose WebinarJam or EverWebinar.
  2. WebinarJam API Key: paste the key.
  3. Click Connect.

LeadJourney validates the key by listing your webinars. The key is stored encrypted and is only used to read webinar data for the mapping screen. When it works you'll see a “WebinarJam connected” confirmation.

Only new data is synced

LeadJourney syncs new WebinarJam registrations from the moment you connect. Registrations from before the connection are not imported.

Paste the webhook URL into WebinarJam

Once connected, the Webhook URL panel shows a URL generated for your workspace. Click Copy, then paste it into WebinarJam → your webinarIntegrationsCustom webhook. WebinarJam has no API to register the webhook automatically, so this step is manual.

Because the webhook is set inside a webinar's own integration settings, add it to every webinar whose registrations you want to track.

Check the connection details

The header shows a Live pill (or Needs reconnect if something breaks), plus Connection, Platform (WebinarJam or EverWebinar), Active triggers and Connected since. The Update API key and Disconnect buttons live in the same header.

Add a trigger

In the Triggers panel (“Each trigger maps a WebinarJam event to one of your conversions.”), click Add trigger. In the New WebinarJam trigger dialog:

  1. App: WebinarJam (already selected).
  2. LeadJourney Event: pick the conversion type this event should record. (Seeing “No conversion types yet”? Create one under Settings → Events first.)
  3. Trigger: pick the WebinarJam event from the grid, such as a registration, live attendance or a replay view. Use Search triggers… to filter.

Click Continue.

Load data, map fields and filter

The dialog opens three tabs:

  • Receive Data: click Find latest data. If LeadJourney can read registrants back from WebinarJam, you'll see them listed and can pick one to map against. WebinarJam only returns registrants for a schedule that hasn't ended yet, so you may see your webinars instead. In that case, type the field names on the next tab (e.g. email, first_name, last_name, phone).
  • Configure Mapping: fill each LeadJourney column from a WebinarJam field. The default rows are Email, Name, Phone, click_id, Revenue and Currency. Pick one or more fields per row (several are joined with a space), type a field path and press Enter, or use static:value for a fixed value. Add custom field adds First name, Last name or any workspace field, or creates a new one.
  • Filtering (optional): click Add filter and set Path, Operator and Value (e.g. webinar_id equals 12345) so the trigger only fires for matching records.

Click Save & Continue on the last tab. At least one field has to be mapped. Save and continue later saves the trigger as it is. New triggers start Active.

How WebinarJam registrations link to the right campaign

Every event needs at least one identifier: a click ID, an email or a phone. Registrants always give an email, so map Email on every trigger and LeadJourney can match the registration to the visitor who clicked. If the click ID also reaches WebinarJam and arrives on the webhook (for example as lj_click_id), type that field name into the click_id row by hand. It won't appear in the Receive Data sample, because that sample is read from the WebinarJam API rather than from the webhook. The webhook-only fields are mapped by name.

Managing your triggers

Each trigger appears as a row, WebinarJam event → conversion type, with an Active / Paused pill and a line such as “3 field(s) mapped · 1 filter(s)”.

  • Pause / Resume: use the toggle to stop a trigger without deleting it.
  • Edit: change the event, mapping, filters or target conversion.
  • Delete: type delete to confirm. The mapping and filters of that trigger can't be recovered; other triggers keep running.
  • Add another: use Add trigger again, for example one trigger for registrations and a second one for live attendance.

Reconnecting

LeadJourney checks the connection whenever you open the integration. If WebinarJam rejects the key (“WebinarJam rejected your API key”, usually because it was rotated or revoked) or the API doesn't respond (“WebinarJam is unreachable”), the header flips to Needs reconnect and a banner explains why. Click Reconnect (or Update API key) and paste a fresh key. Your triggers and settings are kept.

Disconnecting

Click Disconnect in the header. In the Disconnect WebinarJam? dialog, type disconnect and confirm with Disconnect WebinarJam.

Disconnect deletes your triggers

Disconnecting permanently removes the connection, deletes every trigger and drops the stored API key. WebinarJam events stop flowing into your conversions immediately. You can reconnect later, but your trigger configuration won't be restored. You can also remove the custom webhook from your webinars in WebinarJam.

Troubleshooting

Only webinars (or nothing) show up in “Receive Data”?

WebinarJam returns registrants only for schedules that haven't ended. If you see webinars, the key works: type the field names on Configure Mapping instead. If nothing shows at all, check that API access is still enabled on your WebinarJam account and click Find latest data again.

No conversions arrive?

Check that (1) the Webhook URL is pasted into the Custom webhook of the webinar people are registering for, (2) the trigger is Active, and (3) any filters actually match the incoming records.

Conversions arrive but aren't attributed to a campaign?

Make sure the tracking script is installed on the pages visitors see before they register, and that Email (and, if available, click_id) is mapped on the trigger.

Common questions