Integrations / Advertising
Sklik
Server-side conversion and retargeting measurement via the Seznam Sklik SEM Server-to-Server API (POST https://sem.seznam.cz/rtgconv). Maps Signal's GA4-style events to the 17 standard SEM events (PageView, ViewContent, AddToCart, Purchase, Lead, etc), ships SHA-256 hashed first-party match keys (em/ph/fn/ln/ct/zp/country), carries sul.js cookies (sid/udid) and the Sklik click id (sznaiid) for attribution, and maps consent to Consent Mode v2 (granted/denied).
Datafly Signal delivers first-party events to Sklik server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Sklik expects.
Why route Sklik through Datafly Signal
Conversions survive ad blockers and tracking prevention
A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari's ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Sklik optimises against are not filtered by the browser.
Email, phone number, first name, last name, city, postcode and country hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Sklik receives match keys rather than raw personal data.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what Sklik needs to attribute the event to the right session.
One consent decision governs every destination
Sklik is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_payment_infoadd_to_cartadd_to_wishlistbegin_checkoutgenerate_leadpagepurchasesearchsign_upview_itemVertical presets
Retail. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Sklik documentation.
Frequently asked questions
Does Datafly Signal integrate with Sklik?
Yes. Datafly Signal delivers first-party events to Sklik server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Sklik expects. The integration is included in every deployment at no additional cost.
How is server-side Sklik tracking different from the Sklik tag?
The Sklik tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Sklik from your server, so delivery does not depend on browser conditions.
What personal data is sent to Sklik?
Email, phone number, first name, last name, city, postcode and country are normalised and SHA-256 hashed inside your own deployment before delivery, so Sklik receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Sklik?
The blueprint ships with mappings for add_payment_info, add_to_cart, add_to_wishlist, begin_checkout, generate_lead, page, purchase, search, and more. Any event in your schema can be mapped to Sklik through pipeline configuration without a code change.
Do I need to keep the Sklik tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so Sklik deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Sklik server-side?
See how Datafly Signal delivers first-party events to Sklik from infrastructure you control, with hashed identity and consent enforcement built in.