-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
using setCustomUrl() breaks campaign and newsletter tracking #1198
Comments
I'll have to think about this some more, but I want to record these thoughts before I leave and forget:
|
We can indeed have the known campaign parameters to the setCustomUrl() and then remove them at tracking time... These parameters are found in
Re newsletter/campaigns; it is common in WA tools and processes to consider that a newsletter is a campaign like a PPC, off site, on site campaigns can be. The use case you're citing is pretty rare, usually newsletters are clicked more than 30min after the last visit on the website. |
closing as wont fix for now, as if users really want campaign tracking, they can (should?) add the parameters to the custom URL (using javascript for example). I will also try to work on #1042 and with custom campaign variable names, this makes this task more risky. |
Workaround tried by a customer: According to it the parsing of the parameters does not work when using "setCustomUrl", because then only this custom url is sent to matomo and not the "normal" url with all the parameters. The solution is quite simple: just extract those parameters from the normal url and add it to the custom url. With something like the Google Tagmanager it's quite easy. |
When the JS method setCustomUrl() is called, the 'url' parameter to piwik.php is replaced by the custom URL. This 'url' parameter is the one parsed to detect campaign and newsletter referrals. Instead,
Keywords: wishlist
The text was updated successfully, but these errors were encountered: