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
Campaign parameter ignored when not as first parameter #697
Comments
please read: Visits from search engines or campaigns are not recorded, Piwik shows "No data available". especially the part where it explains that only the first keyword/campaign will be recorded as referer; can you please double check that you were not testing this way? |
Hi, there. I checked again. The visitors are all coming with URLs of the type When I visit the URL I still think the different behaviour depends on the campaign parameter appearing as the first one or not. Could anyone check whether this is the case? |
did you check with at least 30 minutes between each test? if yes we shall reopen and fix this issue |
Hi. We did some extensive testing and we are using piwik on a production website receiving lots of daily visits of the form !http://my.test.domain/page?q=keyword&cm=campaignname Test visits where we use cm as first parameter are recorded, the ones with cm as second parameter are not. We installed the latest version yesterday and the issue seems to be still there. Thanks |
re-opening for investigation |
By visual inspection of the code: piwik.js already escapes the url=XXX; in Tracker/Visit.php, getReferrerInformation() calls getRequestVar('url') which results in the value being sanitized. The result is confusing parse_url(). |
(In [1234]) fix #697 - some campaigns not being tracked |
see also
|
When I'm passing the campaign parameter as second parameter, it is not correctly detected.
Thus, after setting
campaign_var_name = "cm"
in config.ini.php, the following doesn't generate a campaign record:
!http://my.test.domain/?x=0&cm=test&b=1
while this one works:
!http://my.test.domain/?cm=test&b=1
Keywords: campaign
The text was updated successfully, but these errors were encountered: