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 PHP Tracking API with Javascript Tracking API #2699
Comments
Attachment: |
Attachment: |
Attachment: |
Thanks for the ticket. Can you please put all patches into one patch file, and explain the changes you made and what problem they solve? thx |
No problem - This was to resolve 'missing' visits that were recorded by our ad platforms but were never recorded in Piwik. The culprit seems to be people 'abandoning' before the page loads and the JS code can fire. The problem was diagnosed by parsing access logs for our sites and for our piwik install respectively. This patch does the follow:
This now allows for more accurate tracking as compared to the ad platforms, and allows us to measure Abandonment rate - we can see how many users leave before the page fully loads / the JS tracking code fires. Possibly beneficial in #1700 - Time of the request versus DOMReady? Currently, this requires the use of the 'trust_visitors_cookie' config option. |
Attachment: condensed Patches to single file |
Thanks for the patch. This is an interesting idea, we will not commit it in trunk, but maybe others will find this patch useful. |
Milestone 1.8.x Piwik 1.8.x deleted |
This has been implemented! see: #4239 |
Ran into the need to be able to use both APIs together for better accuracy in what various ad / search platforms report as clicks to our sites.
Example PHP API Tracking code:
I checked out the trunk and applied my changes to the latest revisions. Patches attached.
Keywords: interesting
The text was updated successfully, but these errors were encountered: