UTM vars on Android Buttons for Play Campaign Tracking

RESOLVED FIXED

Status

Websites
Web Analytics
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: garethc, Assigned: kohei)

Tracking

Details

(Whiteboard: [kb=1232277])

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Can we please add utm campaign tracking parameters to the links where Android buttons exist on mozilla.org? We would like to properly attribute traffic for our Play Store Metrics

Example: 

https://www.mozilla.org/en-US/mobile/?utm_source=mozilla&utm_content=mobile

We could also use utm_content and utm_campaigns for optimization purposes.

Do we have a list of pages where Android buttons are present on Moz.org?

Comment 1

5 years ago
Gareth: All Bedrock download buttons are controlled in a single app and they just show up on any page we define. We just have to make the change once in the app.

Comment 2

5 years ago
The question is do we want to take whatever UTM vars are being passed to a page and then pass those to the Google Play store OR do we want to just manually set UTM variables to specific to the www.mozilla.org website.

For example, do we *always* set the play store link to:

https://play.google.com/store/apps/details?id=org.mozilla.firefox&utm_source=www-mozilla-org&utm_medium=download-button&utm_campaign=website

or should that just be the default and you can override it by passing utm vars to the source page? I'm leaning on the first option on just always setting the same values because Android download campaigns will be pointing to the Play Store and not our website.

Updated

5 years ago
Depends on: 868618

Comment 3

5 years ago
This would only be valuable if we have GA integration with Google Play store to be able to report on in-bound traffic to play.google.com. If we won't ever have GA integrated into Google Play store, we would have to go back to creating a bedrock version of bug 845603.

Comment 4

5 years ago
Now that we have GA on the play store, we should be able to pass UTM vars to play store links.
(Assignee)

Updated

5 years ago
Depends on: 934807
OS: Mac OS X → All
Hardware: x86 → All
(Assignee)

Comment 5

5 years ago
So now I can take this.

:garethc could you provide the utm parameters you need?
Assignee: nobody → kohei.yoshino
Status: NEW → ASSIGNED
Flags: needinfo?(garethcull.bugs)
Whiteboard: [kb=1232277]
(Reporter)

Comment 6

5 years ago
Hey Kohei,

Here's the link with the utm parameters attached to the play store url.

https://play.google.com/store/apps/details?id=org.mozilla.firefox&utm_source=mozilla&utm_medium=Referral&utm_campaign=mozilla-org

Because of how our reporting is set up internally for the Play Store, i'm specifying the actual source in the campaign parameter for now. 

Thanks Kohei!

Could you also fire an event onclick of the Android buttons as per bug #872740. 

Gareth
Flags: needinfo?(garethcull.bugs)
(Assignee)

Comment 7

5 years ago
(In reply to Gareth Cull [:garethc] from comment #6)
> https://play.google.com/store/apps/details?id=org.mozilla.
> firefox&utm_source=mozilla&utm_medium=Referral&utm_campaign=mozilla-org

Thanks! Will send a pull request soon.

> Could you also fire an event onclick of the Android buttons as per bug
> #872740. 

Yes, Bug 872740 will _trackEvent on the Android buttons too :)
(Reporter)

Comment 8

5 years ago
Awesome! Thanks Kohei!
(Assignee)

Comment 9

5 years ago
Created attachment 8357312 [details] [review]
Pull Request on GitHub

Comment 10

5 years ago
Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/2200c543aec2696b7d41b5ed6f98fb6517c3addb
Fix Bug 868601 - UTM vars on Android Buttons for Play Campaign Tracking

https://github.com/mozilla/bedrock/commit/5af317bc4858cf636b83cd33a0a21ffcb92e9c3b
Merge pull request #1569 from kyoshino/bug-868601-gplay-link-params

Fix Bug 868601 - UTM vars on Android Buttons for Play Campaign Tracking

Updated

5 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.