1300804 - Analytics for Alternate Download Experience

Status: RESOLVED FIXED

(www.mozilla.org :: Analytics, defect)

Description

[u570438]

Hi Jon,

Can you make the following additions into this page:
https://bedrock-demo-jpetto-fxnew.us-west.moz.works/en-US/firefox/new/?v=2

On each of the download links within the modal window (and if possible, more broadly), can you add a data attribute called, 'data-download-platform' that holds the platform that is being downloaded?

The values that should be passed into that attribute include:
windows
windows-64
osx
linux
linux-64

Additionally, in v=2, can you add the following on-click of the 'Firefox for Other Platforms & Languages' button?

dataLayer.push({
    'event': 'alternate-version',
    'link-name': 'Systems & Languages'
});

Comment 1

[u570438]

Hi Jon,

Can you let me know when this is done?

Thanks,

PG

Comment 2

[Jonathan Petto [:jpetto]]

Hey Peter - 

I've added the "data-download-platform" attribute to all download buttons site wide. Because the buttons are generated from an external data source, I didn't exactly match the platform values you specified. The values instead are:

win
win64
osx
linux
linux64

I could technically write some code to translate the above list to match yours from comment 0, but hopefully the list here will work.

I've also added a click handler to the 'Firefox for Other Platforms & Languages' link at the bottom of the page on ?v=2. I'm not doing any deferring of the original click intent (sending the user to /firefox/all/). I'm unsure if that dance is necessary after our switch to GTM. Let me know if the dataLayer call gets aborted due to the location change.

These updates should finish building on the demo server in about 15 minutes.

Comment 3

[Luka Cempre (formerly owned by James Lorence)]

Hey Jon,

I actually just added a data attribute for exactly what Peter is requesting here on the download links on the /firefox/all page as part of a different body of work. I used a slightly different naming conversion of "data-download-version" though.

Could you change the data attribute that you've added to use that name? Peter already gave the sign off that he doesn't mind changing it.

-James

Comment 4

[u570438]

I'm good for whichever solution is simplest. Thanks and sorry for the re-work.

Comment 5

[u570438]

James, Can you also include the list of values that should be passed into the attribute?

Comment 6

[Jonathan Petto [:jpetto]]

No problem on changing the data attribute name.

If at all possible, can we use the following values for "data-download-version":

win
win64
osx
linux
linux64
ios
android

These values come from an external data source, meaning it would be a bit of a pain and a hack to alter them.

Comment 7

[Luka Cempre (formerly owned by James Lorence)]

Jon,

I was passing the same values that you were planning to, so there shouldn't be any change there.

Comment 8

[u570438]

It looks like those values are correct, and we can use them. Let me know when you've changed the name of the attribute.

Thanks!

Comment 9

[Jonathan Petto [:jpetto]]

The updated data-attribute names are now up on the demo server:

https://bedrock-demo-jpetto-fxnew.us-west.moz.works/en-US/firefox/new/?v=2

Comment 10

[Luka Cempre (formerly owned by James Lorence)]

The data-download-version looks good to me.

Comment 11

[u570438]

The data attributes look good, but I'm not seeing the datalayer.push that should happen on when the user clicks a link to load the modal window (you could put that either on click or on load of the modal).

Comment 12

[u570438]

Can you let me know when the datalayer.push is in place?

Comment 13

[Jonathan Petto [:jpetto]]

Peter - What should the keys & values be in the dataLayer push when opening up the modal?

Comment 14

[u570438]

Its at the bottom of comment 0. Maybe let's hop on a call if you have any questions.

Comment 15

[Jonathan Petto [:jpetto]]

Ah, I see the confusion. Comment 0 asks for a datalayer push on the "Firefox for Other Platforms & Languages" link in ?v=2, which is in the footer (and to which I added a datalayer push in comment 2). The link to open the modal on ?v=2 reads "Download Firefox for another platform".

(The link under the download button in ?v=1 reads "Firefox for Other Platforms & Languages", which is probably what mixed things up.)

I've moved the datalayer push from the footer link to the modal opening link in ?v=2. The build should be finished on the demo in about 30 minutes.

While we're here, do we need a datalayer push on the "Firefox for Other Platforms & Languages" link underneath the download button in ?v=1?

Comment 16

[u570438]

Thanks Jon.

No, in v1, the link goes to a separate page, and some of our tagging rules pick up the required data collection.

In v2, it opens a modal and the rule is not met.

Comment 17

[Jonathan Petto [:jpetto]]

Peter - 

Do we need a custom ct param for the App Store badge displayed in the modal for ?v=2?

The App Store link by default is:

https://itunes.apple.com/{country}/app/apple-store/id989804926?pt=373246&mt=8

On most pages, we pass a custom ct value that gets appended to that URL, e.g.

https://itunes.apple.com/{country}/app/apple-store/id989804926?pt=373246&mt=8&ct=some_custom_value

Comment 18

[Jonathan Petto [:jpetto]]

:adavis - 

Apologies for pulling you on this already moving train...

To summarize, we are testing a couple options of providing additional download links to users on /firefox/new/. One option includes a link that, when clicked, opens a modal containing direct download links to all platforms, as well as badges for the App and Play stores.

Can you comment on whether or not we need a custom "&ct=" param for the App Store link/badge included in the modal?

Thanks!

Comment 19

[Alex Davis [:adavis]]

The CT param would allow to track clicks in the itunes connect dashboard. Last I checked, if the install happens over desktop (i.e. in iTunes), it won't track the install but rather just the click. (still better than nothing)

If a user goes to /new via his phone and installs, it would track the install and click in iTunes Connect.

Do I think it's necessary to add the CT param? Since it's just a param, I think it's minimal effort and can't harm. So, we might as well include it. It's nice to have all the iOS tracking in one place.

I hope that clarifies.

Comment 20

[pgerman]

This looks like it is closed.