Key takeaways
- The type list is set in config/pixels.php — below is a summary of purpose and caveats.
- Several pixels on one link are allowed; avoid duplicates via GTM + the same vendor separately.
- The TikTok blade is currently incomplete (cookie) — do not promise a full PageView SDK.
- Fire only with domain or Smart Traffic (+ consent when notification is on).
Types table
| Тип | ID format | What is sent (blade/config fact) | Typical case |
|---|---|---|---|
| Pixel ID | fbevents.js + fbq PageView (+ noscript tr) | Meta retarget / events | |
| google-ads | ID (the template will add AW-) | gtag AW- config + noscript | Conversions / Ads audiences |
| google-analytics | gtag ID (e.g. G-…) | gtag config | Analytics on the redirect |
| google-tag-manager | GTM-… | gtm.js + noscript iframe | Tag container |
| tiktok | ID in a cookie | Only document.cookie pixel=… for 5 days | Incomplete — see the caveat |
| yandex-audience | Segment/pixel ID | Per the Yandex Audiences blade | Yandex audiences |
| Partner ID | Insight Tag + noscript gif | B2B retarget | |
| vk-ads | numeric id | Top.Mail.Ru _tmr pageView | VK Ads |
| vk-target | id | 1×1 img tracker | myTarget |
| adroll | ID AdRoll | Per the AdRoll blade | NextRoll / AdRoll |
| bing | ID UET | Per the Bing blade | Microsoft Ads |
| Tag ID | Per the Pinterest blade | Pinterest Ads | |
| quora | Pixel ID | Per the Quora blade | Quora Ads |
| x | Pixel ID | Per the X blade | X Ads |
For facebook / yandex / adroll / tiktok there are also separate guides in the knowledge base — check UI details.
One pixel or several
- One pixel — if the whole budget is in one system (for example Meta only).
- Several — cross-channel collection (Meta + Google Ads + VK) from one smart link.
- GTM as an «umbrella» — convenient if the team already lives in the container; then separate google-ads/ga pixels on the link may be redundant.
- Each vendor = a separate cookie policy and separate consent in your notice.
TikTok caveat
In resources/views/redirect/pixels/tiktok.blade.php a cookie pixel={value} with expires ≈ 5 days is set. There is no full TikTok Pixel SDK / ttq.page / PageView connection in this blade.
In marketing claims and help do not assert «full TikTok PageView as in Events Manager» while the code is like this. A separate TikTok article describes the product scenario — if they diverge, the actual blade has priority.
Common fire conditions
- The pixel is created and attached.
- domain_id or smart_traffic.
- Consent, if pixel_notification is on.
- The click goes through a scenario where pixels are not turned off by bot detection.
End-to-end scenario: retargeting playbook.