Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide control over setting client_id and user_id in common event #22

Closed
adatzer opened this issue Jun 27, 2022 · 0 comments
Closed

Provide control over setting client_id and user_id in common event #22

adatzer opened this issue Jun 27, 2022 · 0 comments

Comments

@adatzer
Copy link
Contributor

adatzer commented Jun 27, 2022

At the moment the client maps the uid/user_id Snowplow property to the user_id property of the common event (here and here). Sometimes this may not be desirable (for example when using the Snowplow Client in combination with GA4 Tag).

Even though gtm-server-side tags usually provide options to configure any mapping downstream, we could also explore providing an option to disable this mapping from the Client, while also leaving the original behaviour as default.

Edit: We could provide a common pattern to also take into account #26

@adatzer adatzer changed the title Consider providing control over setting the user_id in common event Provide control over setting the user_id in common event Oct 11, 2022
@adatzer adatzer changed the title Provide control over setting the user_id in common event Provide control over setting client_id and user_id in common event Oct 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant