Skip to content
This repository has been archived by the owner. It is now read-only.

Begin migration from Classic to Universal analytics #532

Merged
merged 3 commits into from Mar 17, 2015
Merged

Begin migration from Classic to Universal analytics #532

merged 3 commits into from Mar 17, 2015

Conversation

@fofr
Copy link
Contributor

@fofr fofr commented Mar 17, 2015

All apps should use Universal alongside Classic so we can test the implementation and be ready to complete the upgrade to Universal once testing is complete.

Because js files aren't concatenated and minified in the service manual I've avoided pulling in the print and error tracking for now.

Story: https://www.pivotaltracker.com/story/show/89525510

fofr added 3 commits Mar 17, 2015
* Avoid inline script tags
* Initialise an analytics tracker for sending identical pageviews and
custom dimensions to both classic and universal analytics
* Includes sensible IP anonymising and cross site tracking defaults
benilovj added a commit that referenced this pull request Mar 17, 2015
Begin migration from Classic to Universal analytics
@benilovj benilovj merged commit bb6e45d into master Mar 17, 2015
1 check passed
1 check passed
continuous-integration/travis-ci/push The Travis CI build passed
Details
@benilovj benilovj deleted the analytics branch Mar 17, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.