pageview reaches Events and your revenue source is
connected. Each one closes a specific gap between the install and the conversion.
| Guide | Use it when |
|---|---|
| Custom events | You need an action the SDK does not track on its own. |
| Identity | Anonymous visits must join a known customer. |
| Attribution | You need to see which campaign produced a conversion. |
| Conversion delivery | A conversion must reach Meta, Google, TikTok, Snapchat, or OpenAI. |
| First-party tracking | Ad blockers or Safari are cutting your event volume. |
| Cross-domain tracking | The journey crosses two hostnames before it converts. |
| Pixels and scripts | You want Datalyr to load a Meta, Google, or TikTok tag. |
| Filters | Office, bot, or staging traffic is inflating your numbers. |
| App campaigns | A campaign moves from an ad click into a mobile app. |
| Privacy and redaction | Consent, GPC, or a regulated vertical constrains collection. |
| Health and wellness redaction | Product names or URLs could trigger an ad-platform restriction. |
Change one setting at a time, then test it. Identity, filters, and conversion rules
change every future event in the workspace, and they don’t rewrite the past.
Which setting lives where
| What you change | Where |
|---|---|
| Auto Identify, Shopify cart attribution, GPC, DNT, strict privacy mode | Settings → Identity & Attribution |
| Extra hostnames, blocked IPs, blocked pages, masked pages | Settings → Filters |
Meta, Google, or TikTok tags loaded by dl.js | Settings → Pixels & scripts |
| Sensitive-category redaction on outgoing conversions | Settings → Privacy & redaction |
| The tracking subdomain and the install snippet | Settings → Domains and Settings → Install |
| Connections to ad platforms and revenue platforms | Sources, a top-level nav item under Manage |
| Rules that forward a conversion to a destination | Conversions |