> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/integrations/destination-platforms/taboola/export-first-party-audiences.md).

# Export First Party Audiences

### Overview

This destination service lets DinMo create Taboola First Party Audiences and keep their users up to date from your DinMo segments.

To use this service, follow these three steps:

1. **Create a Taboola destination**. Follow the platform setup guide to establish the connection.
2. **Create a DinMo user segment** containing the profiles you want to send to Taboola.
3. **Activate the segment** with the Taboola destination to start synchronization.

Each time the activation runs:

* New users entering your DinMo segment are added to the Taboola audience.
* Users leaving your DinMo segment are removed from the Taboola audience.
* DinMo creates the Taboola audience if it does not already exist.
* If an audience with the same name already exists in Taboola, DinMo reuses the existing audience.

Only users with an identifier that can be matched by Taboola will be available in the Taboola audience.

### Destination setup

Before exporting audiences, create a Taboola destination of type **Export First Party Audiences**:

* Go to **Destinations** > **Add a new destination**
* Choose your **Taboola** platform
* Click the **Export First Party Audiences** option
* Give it a name and save the destination

### Activation configuration

Once your Taboola destination and DinMo segment are configured, create an activation to begin syncing audience membership.

You can activate the segment:

* From the segment overview, using one-click activation
* From the **Activations** tab, if you want more control over the source model, audience name, description, or schedule

#### Audience name and description

The audience name configured for the activation is the name DinMo uses for the First Party Audience in Taboola.

If a Taboola audience with the same name already exists, DinMo uses that existing audience. Otherwise, DinMo creates a new audience with the configured name and optional description.

#### Fields mapping

In the fields mapping section, map the identifiers DinMo should send to Taboola.

You can map the following fields. At least one is required:

* **Email**: The user's email address. The value can be clear text or already hashed with SHA-256. DinMo sends the value as a SHA-256 hash to Taboola.
* **Mobile advertising ID**: The user's mobile advertising ID, also known as `madid`. DinMo sends this value without hashing it.

If both fields are present for a profile, DinMo sends them together as one identity cluster for that user. Fields that are not mapped are not sent to Taboola.

#### Sync mode

Taboola audience export supports full and delta synchronization.

<table data-full-width="true"><thead><tr><th>Sync Mode</th><th>Description</th><th>Behavior</th></tr></thead><tbody><tr><td><strong>Full</strong></td><td>Recomputes the full audience membership for the activation.</td><td>DinMo compares the current segment with the previous run, adds users that should be present, and removes stale users individually from the Taboola audience.</td></tr><tr><td><strong>Delta</strong></td><td>Applies only membership changes since the previous run.</td><td>DinMo adds users who entered the segment and removes users who exited the segment.</td></tr></tbody></table>

#### Scheduling

Define how frequently DinMo updates the Taboola audience. With each scheduled update:

* New profiles entering the segment are added to the audience.
* Profiles leaving the segment are removed from the audience.
* Profiles that remain in the segment keep their audience membership in Taboola.

Choose a schedule that matches how quickly your media activation needs fresh audience membership.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dinmo.io/integrations/destination-platforms/taboola/export-first-party-audiences.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.