> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# ON24

> Register people for ON24 webinars from Conversion, and sync their registrations, attendance, and engagement back.

Connect ON24 to register people for your ON24 webinars from Conversion and bring their registrations, attendance, and engagement back onto each member. Everything in [Webinar Platform Sync](https://docs.conversion.ai/product-docs/campaigns/webinars/platform-sync/overview.md) applies to ON24.

## Set up ON24

**Before you begin:**

* You're a workspace Administrator in Conversion.
* The **ON24** card is turned on for your workspace. It isn't enabled for every workspace, so if you don't see it under **Webinars** in **Settings → Integrations**, contact Conversion.
* Your ON24 contract includes **Connect**, which lets ON24 issue API tokens. Your ON24 account manager can confirm this.
* Someone in ON24 has the **Manage Integrations** permission to create the token.

An ON24 token belongs to the user who creates it. It can only reach that user's events, and it stops working if that user is removed. Create it from a dedicated integration user that can see every event, not from a teammate's own login.

Conversion tests the token before saving it and detects whether your account is in ON24's US or EU region.

### Create a token in ON24

1. Go to **Platform Tools** → **Integrations** → **API Tokens**.
2. Create a token with access to all endpoints. Conversion reads events, registrants, and attendees, and registers people.
3. Copy the **Access Token Key** and **Access Token Secret**.
4. Note your **Client ID**.

### Connect it in Conversion

1. Go to **Settings → Integrations**.
2. Under **Webinars**, click **Connect** on the **ON24** card.
3. Enter the **Client ID**.
4. Enter the **Access token key**.
5. Enter the **Access token secret**.
6. Click **Connect**.

Once connected, the card shows **Connected** and your ON24 account name.

> [!NOTE]
>
> ON24 disables a token after 60 days without use. Conversion checks your token every week, so it stays active even when no webinar is connected.

## Manage the connection

Open the **⋮** menu on the **ON24** card:

* **Manage connection** asks for the token again. Use it to replace the token.
* **Manage fields** maps registration questions and engagement to fields. See [Registration questions](#registration-questions).
* **Disconnect** removes the integration. Webinars stop registering contacts on ON24 and stop syncing registrations and attendance from it.

## Choosing a webinar

You can connect a webinar to any ON24 webcast in the connected account that has a live session between one month ago and five months from now.

These don't appear in the list:

* Engagement Hub and Target content, which aren't webinars.
* Events in ON24 sub-accounts. Connect the sub-account's own token in a separate workspace.

When you connect a webinar, Conversion imports its ON24 registrants and attendance right away.

## Registration

When a member moves to **Registered**, Conversion registers them on ON24 with their email, name, and job title. ON24's reports show Conversion as the source.

* ON24 accepts the registration even if its form marks other fields as required, so a missing field never blocks it.
* Registering someone who is already registered updates their details instead of failing.

ON24 doesn't create personal join links. Instead, Conversion saves the event's audience page with the person's email filled in, which signs them straight in. Add it to your emails with `{{campaign_member.webinar_url}}`.

> [!TIP]
>
> If people only register through Conversion, turn on **Login Only** in the event's registration settings so the link skips ON24's form. If Conversion sends the confirmation email, turn off ON24's confirmation under the event's **Email Notifications** so people don't get two.

ON24 doesn't tell Conversion when someone registers on ON24's own page, so Conversion imports those registrations every 6 hours.

## Attendance

| What ON24 reports | Member status |
| - | - |
| Watched the live session | **Attended** |
| Watched only the replay | **Attended On-Demand** |
| Registered but didn't watch | **No Show**, once attendance is final |

ON24 can take up to 2 hours after a session ends to finish reporting attendance. Until then, anyone who hasn't joined stays **Registered**.

Conversion keeps checking each webinar for 48 hours after it ends:

* A no-show who watches the replay in that window moves to **Attended On-Demand**.
* Replays watched after that window aren't picked up.
* Someone who watched live stays **Attended**, even if they also watch the replay.

Each attendee's join time, leave time, and minutes watched are saved on their member record.

## Registration questions

When you connect ON24, its standard questions are mapped for you:

| ON24 question | Fills |
| - | - |
| **Company** | Company name |
| **Job Title** | Contact job title |
| **Work Phone** | Contact phone |
| **Country** | Contact country |

Like every registration mapping, these only fill empty fields.

Each event's custom questions show up as registration fields named after the question, ready for you to map. A dropdown question keeps its choices. When two events ask the same question, they share one field.

### Engagement

ON24 also reports each attendee's **Engagement Score**, **Live Minutes**, and **On-Demand Minutes**. These aren't mapped by default. Map them to a campaign member field to keep the latest value on each member.

### Map a question to a field

1. Go to **Settings → Integrations**.
2. On the **ON24** card, open the **⋮** menu.
3. Click **Manage fields**.
4. Map the question the same way as for Luma. See [Map a question to a field](https://docs.conversion.ai/product-docs/campaigns/field-events/platform-sync/luma.md#map-a-question-to-a-field) and [How answers are written](https://docs.conversion.ai/product-docs/campaigns/field-events/platform-sync/luma.md#how-answers-are-written).

## Troubleshooting

| Problem | Likely cause |
| - | - |
| A new token won't connect | The **Client ID** is from a different account than the token, or the token has no access to events. |
| The ON24 card no longer shows **Connected** | The token was deleted, or the user who created it was removed. Create a new token and use **Manage connection**. |
| An event is missing from the list | It's Engagement Hub or Target content, it's in a sub-account, it has no live session, or its session is outside the one-month-back to five-months-ahead window. |
| Members are stuck at **Registration Error** | ON24 rejected the registration. This usually means a dropdown got a value its form doesn't offer, or the event was deleted. |
| Someone who registered on ON24's page isn't in Conversion | ON24 registrations are imported every 6 hours. They'll appear after the next sync. |
| **No Show** wasn't set right after the session | ON24 can take up to 2 hours after the session ends to report attendance. |
| A question is missing from **Manage fields** | Conversion hasn't seen it yet. It appears once a webinar is connected to an ON24 event that asks it. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.