Retargeting playbook through ClikBy

Key takeaways

Working flow: link → domain → pixel(s) → Smart Traffic and/or AI Selena → cookie notice → click → filter → fire → ads account.
Without a domain and without Smart Traffic, pixels on the redirect are effectively unused.
UTM are written into visits; pixels fill vendor audiences.

Simplified chain from the redirect code:

The user clicks a short link (preferably on your domain).
If needed — the link password, then the expiry check.
Bot detection may cut off or mark the visit.
If there are pixels + pixel_notification and no cookie — the consent screen.
The visit is written (IP, geo, UTM, …).
Smart Traffic / AI: delay and client-side filtering logic before fire.
Without Smart Traffic, but with pixels and consent — server-side include of pixel blades.
Redirect to the destination; in the Ads account you can collect an audience/conversions.

A plain 301 without an intermediate page with pixels — when there are no conditions for the pixel scenario.

Destination with UTM if needed (UTM builder). Add a tag (Space) for the campaign.

Or plan Smart Traffic — otherwise pixels will not fire.

Facebook, Google Ads, VK, LinkedIn, and others from the supported types.

Set delay/events; for Selena — analysis rules. Allow for Selena settings cooldown (~4 h).

pixel_notification — transparency for the clicker and a fire condition upon consent.

Accept consent, wait for the Smart Traffic delay, check Network and the Ads account / Test Events.

In the ads account you build a retarget on visitors marked by the pixel.

domain_id or smart_traffic = on
The pixel is bound to this link, the ID is correct
consent{link_id}=1 after Accept
The click is not bot-only
For Google/Meta — vendor debuggers see PageView/hit
TikTok: do not expect a full SDK PageView with the current blade (cookie only) — see the comparison