Install and verify the Leado pixel
Connect website behavior to forms, onsite experiences, audiences, workflows, and experiments.
See it in Leado
What you’ll achieve
- A consent-aware pixel source that records the expected website and commerce events exactly once with usable identity and acquisition context.
What you’ll need
- Access to the website template, store integration, or tag manager
Follow the workflow
-
1
Open Settings → Marketing Automation
For a standalone site choose Website and select Copy website script. For Shopify choose Shopify and use Activate app pixel; use Fallback custom pixel snippet only when the app-pixel extension is not available. WordPress or WooCommerce sites can use the dedicated plugin and workspace token.
-
2
Install once across the intended site
Place the website script in the global template so it loads once per page, preferably through the supported commerce integration or a version-controlled tag-manager container. Do not install the same source through both a platform integration and tag manager.
-
3
Connect consent behavior
Make pixel loading and identity/event collection follow your consent-management platform, privacy notice, retention policy, and applicable law. Test both accepted and rejected consent states.
-
4
Generate a traceable test journey
In a private browser, visit a representative page and perform supported actions such as page view, product view, add to cart, form submission, or purchase in a safe test environment. Add recognizable UTM parameters when checking acquisition fields.
-
5
Return to Pixel Tracking and select Apply
Use the date, Source, Event, and Search filters. Confirm Total events, Unique visitors, Last event, Events by type, Daily volume, and a matching Recent events row.
-
6
Validate identity and value fields
Where the test identifies a contact or purchase, confirm the contact link, product/order identifiers, value, currency, source, medium, campaign, and page URL are correct before using the event downstream.
-
7
Check for duplicates and gaps
One user action should not create duplicate events. Missing events usually point to consent, service-worker or script blocking, single-page navigation, selector, cross-domain, or checkout-installation gaps.
Verify your work
- Last event reflects the new test visit
- Recent events contains the expected event name, source, page, and acquisition fields
- Known-contact or purchase events connect to the correct record where identification is available
If something doesn’t look right
No events
Verify the snippet is present in the rendered page, the correct workspace key is used, consent allows loading, and browser blocking is disabled for the test.
Duplicate events
Remove the second installation and check single-page navigation handlers.
Events lack a contact
Identification requires a supported login, form, email-link, or commerce signal; anonymous browsing remains anonymous until linked.
Limitations and safeguards
Browser privacy controls, blockers, consent choices, cross-domain journeys, and offline actions can limit observable events.