See how Selstack handles consent, platform configuration, event meaning, testing and data minimisation, where the boundaries sit and what records support campaign measurement that respects customer choices and produces interpretable events.
This article documents the named Selstack capability, its boundaries and the records a reader can use to verify what happened. It does not assume every control is available to every account.
Start with a measurement purpose
Tracking integrations are a Pro feature. Add one only when a defined campaign decision requires it, and document the owner, events and retention expectation before copying an identifier into settings.
Respect consent before collection
Do not fire optional marketing tags before the visitor has made the required choice. A platform setting does not remove the merchant’s privacy and consent responsibilities.
Keep sensitive values out of events
Never send passwords, card data, identity numbers, free-text form answers or unnecessary customer details to an advertising or analytics platform.
Avoid duplicate installation
Adding the same tag through several tools can count one action more than once. Test one browser journey and confirm which system created each event.
Interpret events carefully
A view, start, lead and paid order are not interchangeable. Compare tracking data with the authoritative Selstack order or contact record before making revenue claims.
Put Use Tracking Integrations Responsibly on Selstack into practice
A Pro business can configure a supported tracking identifier, obtain required consent and test one browser journey without sending form answers.
If Use Tracking Integrations Responsibly on Selstack breaks down
If events duplicate, remove repeated external installation and remember that a browser event is not authoritative payment evidence.
Final checks for Use Tracking Integrations Responsibly on Selstack
- The feature scope and intended audience are stated accurately.
- Any access, plan or administrative requirement is explicit.
- The current Selstack status or audit record is used to verify the outcome.
- The article does not claim that pending work, a preview or an attempt is complete.
- No password, OTP, recovery code, full payment credential or identity number is requested.