SKLIK Audiences integration

Sklik is a Czech ad network under the Seznam Group. This guide covers everything needed to set up the integration from scratch.

This integration is based on the Sklik API. The APIs used are:

• client.loginByToken
• retargeting.emails.addEmail
• retargeting.emails.removeEmail

Bloomreach isn't responsible for changes made in the aforementioned third-party documentation.

Prerequisites

Before you start, make sure you have the following:

• A SKLIK account with access to retargeting lists.
• A SKLIK API token—find this in your SKLIK account settings.
• A retargeting list ID—find this in your SKLIK retargeting lists.
• Your Bloomreach project token—go to Settings > Project.
• Bloomreach API credentials (API group ID and API secret)—go to Settings > Access Management > API keys and create credentials in a private group.

⚠️

Important

Create your Bloomreach API credentials before starting the scenario setup. If you create them mid-setup, you'll lose your progress.

Create the catalog

The authentication flow stores the SKLIK session token in a catalog. Create this catalog before setting up the scenario.

1. Go to Imports > New import > Catalog.
2. Name the catalog sklik_session_token.
3. Select the copy+paste option and paste the following:

item_id,token
token,123abc

4. Set the token column as a string.
5. Run the import. Skip the searchable columns step.

Once the import finishes, open the catalog and note the catalog ID from the URL—you'll need it later.

Set up the authentication scenario

The authentication scenario retrieves and stores a fresh SKLIK session token throughout the day. You only need one authentication scenario per project. There's no need to create a separate one for each audience scenario.

Configure the trigger

The session token needs to be refreshed hourly, but the UI doesn't have an "every hour" option. To work around this:

1. Set the trigger to Repeat daily.
2. Add all 24 hour entries manually.

Add the API user condition

Add a condition to filter on registered = sklik_api_user. This ensures the scenario only runs for the dedicated API user.

🛑

Warning

Without this condition, the scenario triggers for your entire customer database.

To set this up:

1. Create a customer profile with the attribute registered set to sklik_api_user.
2. Add a condition node to the scenario that filters on this attribute.

https://api.sklik.cz/drak/json/client.loginByToken

[
  "your_sklik_token_here"
]

Set up the audience scenario

Once the authentication scenario is running, set up the audience scenario to add and remove customers from your SKLIK retargeting list. Define your customer segment and connect it to the audience webhook.

Add customers to an audience

This webhook calls retargeting.emails.addEmail to add customers to a SKLIK retargeting list.

Batch mode

Turn on Batch mode in the webhook editor. Without this, emails are sent one by one.

Endpoint

https://api.sklik.cz/drak/json/retargeting.emails.addEmail

{%- set token = catalogs.sklik_session_token.item_by_id('token')['token'] -%}

{%- set retargeting_list_id = 123456789 -%}

[
	{
    "session": {{- token | json -}}
},
{
    "retargetingListId": {{- retargeting_list_id | json -}},
    "provider": "bloomreach",
    "emails": 
    [
    {% output customers separated by ",\n  " %}
    ]
}

]

{{- customer["email"] | json -}}

Verification and testing

The most efficient way to verify the integration is to compare the size of an audience created with this API against a manually imported audience from the same customer list.

You can also push valid @seznam.cz, @post.cz, and @email.cz customers who are active email subscribers to the SKLIK audience—you should see a ~100% match rate. For example, 1,000 customers pushed should produce an audience of ~1,000.

Match rates for other domains such as @gmail.com or @centrum.cz will be lower. The total number of matched contacts also depends on consent on the Seznam site—if a consented user doesn't have consent on the Seznam site, Seznam won't match them.