Closed
Bug 1018228
Opened 10 years ago
Closed 10 years ago
Track an Optimizely conversion when a new account is created
Categories
(Webmaker Graveyard :: Metrics, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: adam, Assigned: adam)
References
Details
(Whiteboard: [landingpages] [metrics] [June27])
Attachments
(1 file)
To enable testing and optimization of Unbounce hosted landing pages, we need to call their conversion script when a new account is created. This is their conversion script: <script type="text/javascript"> var _ubaq = _ubaq || []; _ubaq.push(['trackGoal', 'convert']); (function() { var ub_script = document.createElement('script'); ub_script.type = 'text/javascript'; ub_script.src = ('https:' == document.location.protocol ? 'https://' : 'http://') + 'd3pkntwtp2ukl5.cloudfront.net/uba.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ub_script, s); }) (); </script> This page provides more information about how this works: http://support.unbounce.com/entries/334187-external-conversion-tracking
Assignee | ||
Updated•10 years ago
|
Whiteboard: [June13]
Assignee | ||
Comment 1•10 years ago
|
||
Not sure who would work on this, but trying to avoid leaving new bugs without an assignee :)
Assignee: nobody → jon
Updated•10 years ago
|
Whiteboard: [June13] → [June27]
Updated•10 years ago
|
Whiteboard: [June27] → [metrics] [June27]
Updated•10 years ago
|
Status: NEW → ASSIGNED
Updated•10 years ago
|
Whiteboard: [metrics] [June27] → [landingpages] [metrics] [June27]
Assignee | ||
Updated•10 years ago
|
Assignee: jon → adam
Assignee | ||
Comment 2•10 years ago
|
||
Re-scoping, as we're not using Unbounce.
Summary: Track an Unbounce conversion when a new account is created → Track an Optimizely conversion when a new account is created
Assignee | ||
Comment 3•10 years ago
|
||
Doesn't block, as the goal is now email sign-ups. But this will be a useful metric for comparing landing pages anyway.
No longer blocks: 1000226
Assignee | ||
Comment 4•10 years ago
|
||
This is the additional line of tracking for optimizely conversion goals. But this cannot be deployed until, Bug 1027041 is implemented and webmaker-analytics is upgraded in webmaker-auth-client.
Attachment #8442094 -
Flags: review?(jon)
Comment 5•10 years ago
|
||
Comment on attachment 8442094 [details] [review] https://github.com/mozilla/webmaker-auth-client/pull/27 r+, but lets add the latest version of the analytics to this patch, and run `grunt build` to build the minified version as well.
Attachment #8442094 -
Flags: review?(jon) → review+
Comment 6•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/webmaker-auth-client https://github.com/mozilla/webmaker-auth-client/commit/5f20b47a8a7d82b53b5bef47eeb8696c1476c4f7 fix bug 1018228 - add optimizely conversion tracking https://github.com/mozilla/webmaker-auth-client/commit/53bc51375ed7e00d8919cda819250de6f336a361 Merge pull request #27 from adamlofting/bug1018228conversion fix bug 1018228 - add optimizely conversion tracking
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•