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
For a visit via a campaign, if the campaign keyword is not set, detect keyword from Referrer URL #517
Comments
No worries I'll give this a shot with a small adwords account I am playing with. Though I also have some more advanced idea's for tracking adwords without auto-tagging and thus giving more functionality in other area's. Will test this out firstly and go from there. |
marc, sounds good; let us know if you find any bug or issues, this has never been tested, but we want this to work perfectly and with an easy to use documentation; I think we can assume that we need adwords to be auto tagged using landing keyword, etc. |
Hey Matt, Not really. There are other less obvious to others, ways to track adwords that still keeps your data private. See bots and others can crawl and track adwords adds and backwards engineer what you are bidding on. Do that every day over a period of time and you have a clear picture of what keywords are profitable for someone in what industry. I'll test it out on auto-tagging and then discuss privately the other concepts and decide if you want to introduce those. Of course there could be both options, auto-tagging and then the privacy option :D Talk Soon |
example adwords url
|
From forum post
|
I made some test for a few days with an adwords account. Adwords reports 5 clicks and I see 5 clicks in the Piwik DB, good start. But 1 didnt have the referer set, 2 others were from google & Ask.com, 2 from Google display (adsense). The only way to track Adwords properly is to have users enable auto tagging in their account: Then landing page URLs have the parameter 'gclid' which is how we detect that the user is coming from adwords. Alternatively (AND / OR), Users can 'manually' tag their landing pages, then they simply can use the standard Piwik campaign feature #604 Then we can look at the ref URL
The parameter 'url' gives the URL where the click comes from. This is important to report it in Piwik since adwords advertisers would want to ban domains that have poor conversion rates from their Display pool. Maybe a good way to report Adwords in Piwik would be:
See google search network: http://adwords.google.com/support/aw/bin/answer.py?hl=en&answer=90956 and google display network: http://adwords.google.com/support/aw/bin/answer.py?hl=en&answer=117120 interesting page: http://www.google.com/support/forum/p/Google%20Analytics/thread?tid=3b79c0131cf3148d&hl=en Tasks
Any other suggestion / idea, please comment |
on a related note...
|
There is a proposed solution in: http://forum.piwik.org/read.php?2,79853,page=1#msg-81585 |
Claryfying & Restricting the scope of this ticket This was the previous ticket description:
; variable name to track the campaign name
|
(In [7811]) Refs #517, search for campaign keywords in referrer URL when not supplied by query param and use referrer hostname when no keywords in referrer URL and nothing supplied in query param. Note: also includes quick tweak to integration test base for more descriptive error when expected file cannot be found. |
(In [7812]) Fixes #517 if a campaign name is set, we will try to fill in the keyword with the publisher Url (when visitor came from adsense ad) or with user keyword (when coming from adwords) |
I have also problems with tracking AdWords campaigns. This issue is closed, but the problem seems to be not solved yet. I see lots of "googleads.g.doubleclick.net" referrers in my statistics. They are not detected as campaigns. The referrer URLs are of the form in #476. There are many parameters in the link, but parsing at least the "url=..." would be nice. I would also like to help with coding, just tell me what would be the best way to implement this in Piwik. Thanks a lot, |
I have found a workaround:
The original code did not work because the pk_campaign parameter was not set for our AdWords campaigns. This way, every visit from doubleclick host is considered as the AdWords campaign and the referring sites are encoded as campaign keywords. |
thanks for the suggestion. Could you send me an example of a Adwords URL and an example of a Adsense URL ? I think it would be best to set the campaign name to either Adwords or Adsense depending on the referrer URL. |
Thanks Matt, I sent you the URL examples to your email. Don't know if there is any secure info in the url parameters. There is an url parameter "adsense_enabled", which is always true in our links, so I don't have any examples of Adwords (no Adsense) urls. |
see also #4468 when &gclid= parameter found, mark visitor as Adwords |
…ds those visitors that come from a click on adwords
Bug report:
When a visitor comes and a campaign “name” is detected, there are sometimes no “keyword” set. Instead of leaving the value empty, we could try to fill up the gap and:
- try detect the keyword from the Referrer URL if it is found there (ie. if a search engine was used)
- if no keyword could be detected from the ref URL, set the “campaign keyword” as the domain hostname. This way it will give an easy breakdown of referrer website URL for campaigns.
This would improve the campaign tracking data quality.
Google Adwords tracking would also work better and give more accurate data.
- See new [Tracking Campaigns](http://piwik.org/docs/tracking-campaigns/)
- [URL Builder tool](http://piwik.org/docs/tracking-campaigns/url-builder/)
- Official piwik campaign parameters names are now: pk_campaign and pk_kwd (consistent with cookie prefix, better than piwik_ prefix)
- New FAQ: [“Does Piwik support Google Analytics campaign parameters (utm_campaign, utm_medium, utm_source, utm_term)?”](http://piwik.org/faq/general/#faq_119)
- New FAQ: [“How do I customize the Piwik Campaign parameters pk_campaign and pk_kwd?” ](http://piwik.org/faq/how-to/#faq_120)
The text was updated successfully, but these errors were encountered: