The Segment Builder allows you to enhance your personalization and audience targeting by leveraging account‑level intelligence from 6sense. With this integration, you can build smarter, data‑driven segments that deliver the most relevant content, calls to action, and experiences to your attendees.

Find more information on how to access your token in this 6sense article.  

After saving your credentials a new Data Source called 6sense Scores becomes available in ON24 Segment Builder. If your 6sense instance uses multiple product configurations, you can also specify the Product Name. 

6sense users will have these options under Data Source: 

ON24 can connect to client Marketo instances to create ON24 Segments from Marketo program members.

Marketo programs can be populated with people from smart lists via smart campaigns. The Marketo smart lists can include all the applicable filter criteria for segmentation with Marketo.

The Marketo programs can then be associated with ON24 segments, so that Marketo segmentation via smart lists can flow through ON24 Segments for personalization.

To add Marketo API Credentials:

1. Configure a Marketo API‑Only user with the following Access API permissions:
   • Read‑Only Activity
   • Read‑Only Campaign
   • Read‑Only Person
2. Use the API‑Only user to create a Custom LaunchPoint Service in Marketo. This service will generate the Client ID and Client Secret.
3. Add Marketo API Credentials in your integration settings.  Enter the Client ID, Client Secret and your Web Services Identity URL, then click Save.

Note: Any version of the Marketo Identity URL is accepted as long as it includes the correct root domain.

Once these credentials are added, the Marketo Program ID option will become available within the ON24 Segment Builder.  

The Value for the Program ID can be pulled from the URL when you are in the Marketo program. See this article from Marketo on how to reference the Program ID from a URL.

In this example, we've built a segment based on registrant business goals.

First, we added a custom registration field to our registration form and updated the field to reflect business goals.

Choose the Data Source option that matches the registration field used to create the question. In this example, we used Custom Field #10 to create our question. The Condition will be contains, and the Value will be based on one of the choices from the registration field.

In this example, we would create three different segments, one for efficiency, one for growth, and one for customer experience, so we could capture segments of our audience based on their answer to this question.

These three segments will then be used to configure personalization tools. Here, we've set up the Take Action by Segment tool for each of the three segments, so the correct version of the tool appears to attendees based on their answer on the registration form.

In this example, we'll build a segment based on a yes/no question and personalize experiences based on a positive response. This example uses the pre-populated Positive Response segment, but can be created as its own segment if necessary.

Using a custom registration field, we built the question "Are you currently evaluating providers?" and added answer options of Yes and No.

Next we'll create the segment. Choose Custom Field #10 as the Data Source. The Value we'll use is Yes.

Finally, we'll personalize the Related Content tool using our evaluation segment. Those that answered Yes to the "Are you currently evaluating providers?" question will see the additional content.

Pro Tip: In this example, attendees who have answered Yes to this question in any of the events in your account will see this additional content.  If you want the content to only show for those who answered Yes in this event, use the Event Specific Segment toggle when creating the segment.

For this example, we're going to build and use a segment based on a pre-populated field in the registration form.

We've added the Title field to our registration form, then we'll create a segment for those that choose Manager.

Once the segment is created, we'll use it to personalize a category in the Engagement Hub. Only those that choose Manager when registering will see this category.

For this example, we're building a segment capturing contacts in specific countries using the "is in list" Condition within a Rule.

You can use the "is in list" Condition to add multiple values (up to 50) in a single rule.

To capture contacts in United Kingdom, France, Germany, and Italy, we'll select Country for Data Source, is in list for Condition, and add United Kingdom, France, Germany, and Italy under Value.

Using the "is in list" Condition allows you to easily add multiple values, instead of adding each value individually with +OR (Country is United Kingdom, OR Country is France, OR Country is Germany, OR Country is Italy).