SupportExternal Tracking
Install approved analytics or advertising tracking and verify exactly what data leaves Lead360.
How this fits into Lead360Explore the agency and client platformConnect administration, providers, users, billing, and developer access.- 01
How Lead360 helps
- 02
Plan the measurement
- 03
Install and test
- 04
After publishing
How Lead360 helps
Lead360 External Tracking lets authorized teams add approved measurement configuration to supported customer destinations. A controlled setup connects campaign and conversion events with the correct site or funnel while consent, data minimization, duplicate prevention, and source verification remain explicit.
When to use this area
Use External Tracking when a documented analytics or advertising measurement requirement cannot be met by existing built-in reporting.
Before you begin
- Document the provider, business purpose, event names, data fields, and destinations.
- Review consent and privacy requirements for every region and audience.
- Inspect the approved code for credentials, personal data, duplicate loaders, and unsupported remote behavior.
Plan the measurement
- Choose the provider, account, pixel, tag, or container owned by this business.
- Define the page views and conversion events needed.
- Use stable event names and avoid duplicate client and server events.
- Confirm consent and privacy requirements before enabling tracking.
Install and test
- Enter the provider identifier or approved script in the intended field.
- Use provider test tools and a browser test session.
- Confirm each action fires once with the intended properties.
- Verify no private contact, credential, or payment data is exposed.
After publishing
Compare Lead360 and provider totals, monitor rejected events, and document attribution windows and consent behavior before using the data for decisions.
Use Ask360 here
Ask360 can explain current tracking fields, review an approved snippet for obvious duplication or sensitive data, and prepare a controlled test plan. It never fetches arbitrary remote code, publishes a script, changes consent settings, or claims an event fired without observed evidence.
Confirm the result
A completed External Tracking workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.
- Test in a non-customer or controlled environment first.
- Observe the exact browser and provider events.
- Confirm consent state, deduplication, page performance, and removal behavior.
Troubleshooting
An event fires more than once
Check duplicate snippets, tag managers, client and server event overlap, page navigation, and retry behavior.
Tracking runs before consent
Review consent manager ordering, default state, regional rules, and every installation location before republishing.
Frequently asked questions
What should I confirm before using External Tracking?
Document the provider, business purpose, event names, data fields, and destinations. Review consent and privacy requirements for every region and audience. Inspect the approved code for credentials, personal data, duplicate loaders, and unsupported remote behavior. Start with a small, reviewable change whenever the workflow can affect customers, money, published content, or shared records.
How does Lead360 help with External Tracking?
Lead360 External Tracking lets authorized teams add approved measurement configuration to supported customer destinations. A controlled setup connects campaign and conversion events with the correct site or funnel while consent, data minimization, duplicate prevention, and source verification remain explicit.
Continue with Lead360
Use this workflow in Lead360
Put this guide into practice with a 14-day free trial of Lead360 Pro early access, or continue learning through the related collection.