| Guide | Use it when |
|---|---|
| Custom events | Your product has an action Datalyr cannot infer automatically. |
| Identity | Anonymous activity must connect to a known customer. |
| Attribution | You need to verify how campaign context reached revenue. |
| Conversion delivery | A business event should be sent to an ad platform. |
| First-party tracking | You want supported tracking on your own subdomain. |
| Cross-domain tracking | The journey moves between sites or checkouts. |
| Pixels and scripts | Datalyr should load a supported browser tag. |
| App campaigns | A campaign moves from web or ad click into a mobile app. |
| Privacy and redaction | Collection or delivery must follow stricter controls. |
Advanced
Advanced
Configure custom collection, identity, delivery, and privacy.
Use these guides after the standard installation and revenue source are working.