-
Notifications
You must be signed in to change notification settings - Fork 58
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
Ability to reset custom dimension when tracking SPA with Matomo Tag Manager #368
Comments
@peterbo would this be fixed by #201 maybe? I think there was some discussion in #201 (comment) Or how do you reckon would this work best? |
Hey @tsteur - #201 would definitely help to get rid of tons of workarounds. But in this case, it would not solve the problem. As an example, the following use-case:
Possible solutions:
Also, I'm not quite sure how to solve this the most elegant way. Perhaps a setting like "reset variable value if not present in the next event of the same type" or something like this. But this seems to be a bit too "specific". ;) |
I wonder if in that case maybe somehow needs to be hooked into this using Custom HTML tag and calling I would have suggested to maybe have an option to delete custom dimensions after the page view or after the event was tracked. But if I understand things correctly that wouldn't help in that case? |
I tried to execute
Or simply have one setting for an event to imitade a context changing pageView -> all variables get reset, before some get reassigned. When this specific event gets triggered, all the selected variables get resetted, before the new variables sent with the event get assigned. I'm not sure how practical this would be, but for SPA, this certainly would help. |
Got it 👍 |
For tracking with the legacy tracking code, there is
_paq.push(['deleteCustomDimension', 1]);
- that doesn't work with the Tag Manager. That results in custom dimensions being tracked for pageviews and actions that should not contain this data.The text was updated successfully, but these errors were encountered: