SKLIK Audiences Integration

This integration enables authentication and sending of customer lists into ad account in Sklik via webhook from Bloomreach Engagement’s scenario.

Sklik is an ad network operating in the Czech Republic under the Seznam Group.


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

Bloomreach is not responsible for changes made in the aforementioned 3rd party documentation.

Authentication Set-Up

Firstly, the authentication webhook has to be set up correctly. This allows generating a session token that is used in the audience to push webhooks. The session token needs to be retrieved multiple times a day because it changes regularly.

You need the SKLIK token, which you can find in your SKLIK account. Input this token inside the payload of the authentication webhook. The authentication webhook calls client.loginByToken API.

The response of the authentication webhook call will contain the session token saved in a catalog by a subsequent webhook present in the authentication flow. Since the session token changes multiple times a day, the authentication flow has a repeat trigger set to repeat multiple times a day (every hour). This ensures the session token in the catalog is up to date.

The catalog needs to be created manually at first. The easiest way is to create the catalog via import. Go to imports > New import > Catalog > name the catalog “sklik_session_token” use copy+paste option and copy-paste the following:


Set the column token as a string and import the catalog once (skip the searchable columns setting). Once the import finishes, find the catalog and open it.

The catalog ID is in the catalog URL. This ID needs to be placed in the “Add session token to a catalog” webhook, and you will also need to set authorisation for this webhook.


You only need one ongoing Sklik Authentication scenario in your project. There is no need for authentication flow for every Sklik audience scenario.

Audience webhook

Secondly, after we successfully obtain the session token, we can proceed with audience creation. The audience webhook is a batch webhook that uses Sklik’s retargeting.emails.addEmail API, which has certain rate limits. Splitting larger audiences into multiple chunks using custom wait time is advised.

Define your segment and connect it to the audience webhook. Then, you will be ready to push your chosen customers to the Sklik audience.

Preventing repetitive adding of the same people to the same audience for ongoing campaigns

Similarly, for best practices of native ad audience integrations, we recommend that you push customers to the SKLIK audience only once if nothing else has changed. Repeatedly adding the same customers to the same audience generates unnecessary events.

You can achieve this optimization by using simple conditions in your scenario flow. This condition ensures that only customers who have not yet been added to the audience or customers who have already been removed from the audience previously (and we want to add them again) will go through.

Verification and Testing

The most efficient way to verify the correct working of the SKLIK audience API is to compare the size of an audience created with this API with a manually imported audience created from the same list of customers.

Alternatively, If you push valid,, and customers who are active email subscribers (they are opening and clicking on your emails) to the SKLIK audience, you should get ~100% match rate. In other words, if you push 1000 such customers into the SKLIK audience, you should see an audience of size ~1000. In case of pushing other valid email domains such as or the match rate of these emails will be much lower. The total number of matched contacts depends also on the number of consents on Seznam's site. If your consented user doesn't have consent on the Seznam site, Seznam will not match this user.