Available lifecycle scripts
The editor checks whether the supplied text is valid JavaScript, but syntax validation does not
prove that a provider loaded, an event was delivered, or the script is safe.
Recommended setup
- Create a test source or project in your analytics provider.
- Add the provider’s browser loader to Base Script.
- Initialize anonymous application tracking in App Initialization Script when required.
- Map
idand the suppliedtraitsin User Identification Script. - Send Vida
pageandpropsvalues from Page View Tracking Script. - Send Vida
eventandpropsvalues from Event Tracking Script. - Use the provider’s live debugger to verify identification, page views, and representative events.
- Repeat the validation from a downstream customer account before copying the configuration to production.
Use traits carefully
Thetraits object describes the signed-in user and the routed Vida account. Use stable external
identifiers when you need to reconcile Vida activity with your product. Inspect the actual payload
in the test environment instead of assuming every account type exposes the same fields.
Collect only the data your analytics implementation requires and apply your privacy, consent,
retention, and access policies.