Skip to content

Commit 070fddd

Browse files
committed
pr comments
1 parent 54c092b commit 070fddd

File tree

1 file changed

+2
-2
lines changed
  • src/connections/destinations/catalog/actions-taboola-actions

1 file changed

+2
-2
lines changed

src/connections/destinations/catalog/actions-taboola-actions/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,14 +44,14 @@ The Audience will start to sync to Taboola shortly.
4444
It takes another 2-5 days for the segment to scale up and become available for targeting/suppression in Taboola Ads.
4545

4646
> info ""
47-
> To view the audience on the Taboola platform, navigate to the [Tbaoola Ads audience page](https://ads.taboola.com/audiences), select "Custom Audience" and search for the audience you have just connected.
47+
> 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.
4848
4949
## Supported identifiers
5050

5151
The **Taboola (Actions)** destination supports syncing Audiences to Taboola using either the `email` and/or the `Mobile Device ID`.
5252
`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 configuration:
5353

54-
1. Your Engage Space's Identify Resolution rules will need to be configured for `android.id` and `ios.id` identifiers. This can be configured by navigating to `Unify` >> `Unify Settings`.
54+
1. Your Engage Space's identity resolution rules will need to be configured for `android.id` and `ios.id` identifiers. This can be configured by navigating to `Unify` >> `Unify Settings`.
5555
![Enage ID Resolution Settings with android.id and ios.id configured](images/engage_id_resolution_settings.png)
5656

5757
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.

0 commit comments

Comments
 (0)