# Taboola (Actions) Destination

## Destination Info

* Accepts [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Taboola (actions)**, **Taboola (Actions)** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.
* This destination is **Beta.**

[Taboola](https://developers.taboola.com/backstage-api/reference/create-a-first-party-audience/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) integration allows you to connect and target your Segment audiences with Taboola.

This destination is maintained by Taboola. For any issues with the destination, contact their [Support team](mailto:support@taboola.com) or your account manager.

## Getting started

### Get Taboola Account Details

Before connecting the **Taboola (Actions)** destination you'll need the following:

1. Your Taboola **Client ID** and **Client Secret** - provided by your Taboola account manager.
2. **Account ID**: retrieve using one of these options:
   * [Taboola Ads](https://ads.taboola.com) - Use the account's alphanumeric name without spaces and in lowercase. For example, 'My Account - Name' would become 'myaccountname'
   * [API](https://developers.taboola.com/backstage-api/reference/get-account-details) - Retrieve Account Details using the Get Account Details API.

### Create and Connect the Taboola Destination

1. From your Segment workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog) search for **Taboola (Actions)**.
2. Select **Taboola (Actions)** and click **Add Destination**.
3. Next, connect the Engage Space to your **Taboola (Actions)** Destination. To do this, use the `Search for a source` search field to find your Engage Space, then select it. Next, click the **Confirm Source** button.
4. On the **Basic Settings** screen input the Taboola **Client ID** and **Client Secret** values.
5. Enable the Destination using the toggle, then click the **Save Changes** button.

The **Taboola (Actions)** Destination is now connected to your Engage Space. The next steps cover connecting an Audience to a **Mapping** on your **Taboola (Actions)** Destination.

6. Navigate to the Audience you'd like to sync to **Taboola (Actions)**.
7. On the **Audience Overview** tab, click the **Add Destination** button, then select the **Taboola (Actions)** Destination.
8. Under the **Destinations** heading in the **Audience Overview** page you should now see your **Taboola (Actions)** listed. Click the **Add Mapping** button.

   ![Taboola actions settings tab with options for event names, account ID, and TTL in hours.](https://docs-resources.prod.twilio.com/5bd9dd0ab30d023e76e414007cbc7e74f68b78f45beb2c5e492e984f17e136be.png)
9. When the side panel on the right displays, navigate to the **Settings** tab.
10. On the **Settings** tab, ensure that **Send Track** is enabled, then populate the Taboola **Account ID** field.

    ![Audience settings.](https://docs-resources.prod.twilio.com/ca2a39f8f57e5e85bbe13bc64eb7e9765baa05555da05b4527e60449c42d4faa.png)
11. Click the **Save** button.
12. Remain in the side panel, and navigate to the **Matching mappings** tab. Click the **Add mapping** button, then select **Sync Audience**.
13. On the **Sync Audience** page, click the **Save** button. You'll be taken back to the **Matching mappings** tab. Enable the Mapping using the toggle.

    ![Taboola actions Matching mappings tab showing enabled sync audience mapping.](https://docs-resources.prod.twilio.com/58a7266d5b4aee473a32a3eea919c1dc2a05919eddf22ce61038ac7a5f96e94f.png)

The Audience will start to sync to Taboola shortly.
It takes another 2-5 days for the segment to scale up and become available for targeting/suppression in Taboola Ads.

> \[!NOTE]
>
> To view the audience on the Taboola platform, navigate to the [Taboola Ads audience page](https://ads.taboola.com/audiences), select "Custom Audience" and search for the audience you have just connected.

## Supported identifiers

The **Taboola (Actions)** destination supports syncing Audiences to Taboola using either the `email` and/or the `Mobile Device ID`.
`email` will be automatically included if present. Additional configuration steps are required in order to sync `Mobile Device ID` values. To sync `Mobile Device ID` values ensure the following is configured:

1. Configure your Engage Space's identity resolution rules for `android.id` and `ios.id` identifiers by navigating to `Unify` >> `Unify Settings`.

   ![Identity resolution settings with user\_id, android.id, and ios.id configured.](https://docs-resources.prod.twilio.com/48de1bc68b097f830423277a418e780e808b4f3e70d5bdf1ec376c7978a14be1.png)
2. Ensure that both the `android.id` and `ios.id` identifiers are configured exactly as per the image below. This configuration step takes place when the Destination is being connected to an Audience.

   ![Customized Setup for LiveRamp Audiences with options to add identifiers and map traits.](https://docs-resources.prod.twilio.com/1877deef292570c9076d85ce8f6c8a3cc40cee31751b459852a2a8b02f74957a.png)

## Destination Settings

| Field               | Description                                        | Required | Type     |
| ------------------- | -------------------------------------------------- | -------- | -------- |
| Audience Identifier | The audience identifier from your Taboola account. | No       | select   |
| Client ID           | The client ID from your Taboola account.           | Yes      | string   |
| Client Secret       | The client's secret from your Taboola account.     | Yes      | password |

## Available Actions

Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Taboola-supported actions:

> \[!NOTE]
>
> Individual destination instances have support a maximum of 50 mappings.

* [Sync Audience](#sync-audience-5)

### Sync Audience

Sync users to Taboola.

Sync Audience is a **Cloud** action. The default Trigger is `type = "track"`

| Field            | Description                                                                                                                                     | Required | Type    |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- |
| Email address    | The user's email address                                                                                                                        | No       | STRING  |
| Batch events     | When enabled, events will be batched before being sent to Taboola. In most cases, batching should be enabled.                                   | Yes      | BOOLEAN |
| Mobile Device ID | To send iOS and Android Device IDs include them as 'ios\_id' and 'android\_id' via the 'Customized Setup' option when connecting your Audience. | No       | STRING  |

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

> \[!NOTE]
>
> Real-time audience syncs to Taboola (Actions)  may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field               | Description                                        | Required | Type     |
| ------------------- | -------------------------------------------------- | -------- | -------- |
| Audience Identifier | The audience identifier from your Taboola account. | No       | select   |
| Client ID           | The client ID from your Taboola account.           | Yes      | string   |
| Client Secret       | The client's secret from your Taboola account.     | Yes      | password |