Enable additional signals
Outbound links, bots, performance, and website errors.
Open Setup → Pixels → Pixel → Settings → Automatic tracking to enable four features without per-event rules.
- Enable a switch; changes save immediately.
- Reload the published website to load updated settings.
- Perform the test below.
| Feature | New Pixel default | Collected data | Verification |
|---|---|---|---|
| Outbound links | Off | outbound_link for HTTP/HTTPS links to a different hostname. | Click an external link and check the event. |
| Bot detection | On | Automation score and signals attached to journey events. | Inspect bot signals in event data. Visits are not blocked or discarded. |
| Web Vitals | Off | LCP, CLS, INP, FCP, and TTFB when available. | Visit, interact, then switch tabs; check Site health → Vitals. |
| Error tracking | Off | Uncaught JavaScript errors and unhandled promise rejections. | Reproduce a known error on a test website and check Site health → Errors. |
Outbound links
The event includes the full URL, up to 100 text characters, and optional window target. A different subdomain is a different hostname. mailto:, tel:, and same-hostname links do not count. For clicks on nested content, anchor lookup goes up three levels; deeper structures can be missed.
This follows ordinary event consent. A separate Click rule on the link can send both your named event and outbound_link.
Performance and errors
Web Vitals and Error tracking use a separate channel without cid or sid, without waiting for banner consent. They still stop when the Pixel is disabled. Do not expect this data in ordinary journey event lists.
In Site health, choose the Pixel; a single Pixel may open directly. Vitals shows available measurements and Errors grouped errors.
Metric delivery depends on the browser, interactions, exit, and visibility changes. Not every page produces every metric. This channel does not connect visits to individual profiles.
Error tracking deduplicates matching message/location combinations and limits sending to 20 errors per page load. Messages are capped at 500 characters and stacks at 2000. Queries are removed from source URLs and stack URLs, but error text is not fully anonymized: avoid putting form data in website error messages.
If data is missing
Check the switch and reload. Errors preceding activation are not recovered. Check the Pixel and time range in Site Health. For ordinary event issues, use the verification guide.