Create a First Party Audience

Sample CREATE request

POST /backstage/api/1.0/demo-advertiser/audience_onboarding/create

{
  "audience_name": "Demo Audience Name",
  "ttl_in_hours": 1440,
  "integration_source": "Tealium"
}

{
  "audience_name": "Demo Audience Name",
  "ttl_in_hours": 1440,
  "audience_id": 49,
  "exclude_from_campaigns": false,
  "integration_source": "Tealium"
}

📘

Supported countries

See the overview (above) for a list of supported countries.

🚧

End-to-end flow

1. Create a First Party Audience via the API (as described on this page).

   An audience is uniquely identified by the audience_name provided.
   Allow up to 1 hour for a newly created audience to become available.

2. Add 1 or more batches of users, passing the relevant audience_id. See Adding users (below).

   For testing purposes, populate the audience with as many users as possible (1,000 users or more).
   To cater for network latency, limit each batch to 100k users (or less).

3. Wait 1 - 3 days for the audience to achieve scale.

   You can check the audience_size using the My Audience endpoint.
   For basic troubleshooting steps, see Audience size has not changed? (below).

4. Target the above Audience ID.

📘

Adding users

When adding users, you need to pass the audience_id. A possible flow is shown below:

1. Submit a CREATE request, passing the relevant audience_name.
2. If the name exists, the server returns the existing audience.

   You can add users immediately.

3. Else, the server creates a new audience, and returns that.

   Allow up to 1 hour for the newly created audience to become available.

🚧

Audience size has not changed?

The audience_size field reflects the estimated number of users with visible activity in the Taboola network, over the past 30 days.

If the audience_size does change, it means that Taboola was unable to match any of the uploaded users. In that case, check the following guidelines:

1. Populate the audience with as many users as possible (1,000 users or more).
2. Wait 1 - 3 days for the audience to achieve scale.
3. Make sure that you have not mistakenly hashed the emails twice.
4. If the problem persists, open a ticket with [email protected].