Authentication of personalized tracking events

[Alex_Benini]

Hi @mgloel

If you are referring to this post:

@PaulBoocock

Already you could send auth tokens to the collector as a context and validate them with the JS Enrichment or the API Enrichment - this would be powerful for authenticated users, you could simply pass the auth token and enrich the event with user data based on the auth token as well as further authenticating the event for logged in users.

This isn’t ready out-of-the-box but what Paul explained can be applied to the mobile trackers too. On Android tracker you can attach a custom context (with auth token or a public key) to all the events (you can use Global Contexts feature for that), and adding an enrichment in your pipeline you can check the event source reliability.

This old post (for JS tracker but applicable to mobile trackers too) explains how to create a custom context.

From your initial post:

@mgloel

we would like to make sure to stop receiving events from these users once they have withdrawn their consent.

The Android tracker can be paused and resumed at runtime, so you could manage the consent of the user in your app and stop the event tracking when they withdrawn their consent.