This task connects permission-based customer communication to a measurable business journey. This guide focuses on how to add authorised tracking, respect consent and test one clear event path.
Check plan and consent first
Merchant tracking integrations are a Pro feature. A Pro control does not remove the business’s duty to obtain any consent required before optional marketing tags run.
Open Integrations
Use the Tracking section to add a supported integration and identifier. Add one route for each measurement purpose and avoid installing the same tag through several tools.
Keep event data minimal
Never send passwords, payment credentials, identity numbers or free-text form answers to an advertising or analytics platform. Record the events you expect before enabling the integration.
Test one journey
Open a controlled public journey and confirm page, lead, checkout or purchase events according to the integration. Compare paid outcomes with Selstack Payments rather than treating a browser event as authoritative revenue.
Troubleshoot duplicates
Disable duplicate site-wide or external installations and test again. If Selstack shows the integration saved but no event arrives, confirm identifier, enabled status, consent and browser blocking before contacting support.
Example: Configure Tracking for a Campaign
A Pro business can add one Meta Pixel or Google Tag Manager integration, obtain consent and test a purchase journey without sending form answers.
If Configure Tracking for a Campaign is not working
If events double, remove duplicate external installation and retest one controlled browser journey.
Confirm the result
- The audience, permission and message purpose agree.
- Personalisation, links, consent and unsubscribe behaviour were tested.
- The follow-up has a clear owner and stop condition.
- Results are measured against leads, orders or replies rather than views alone.
When to ask Selstack for help
Contact official Selstack support when the saved result, status or resolved identity still conflicts with the intended record after one refresh. Include the business, page, time, safe reference and visible message. Do not include passwords, OTPs, recovery codes, full card details, BVN, NIN or unmasked bank documents.