Download Tag is Fired on Click of Button - What about direct links to scene=2?

RESOLVED FIXED

Status

www.mozilla.org
Analytics
RESOLVED FIXED
a year ago
a year ago

People

(Reporter: pgerman, Unassigned)

Tracking

Production

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

a year ago
Right now downloads are tracked via events fired on click of the download button

There are a number of downloads that will occur by users being linked directly to /firefox/new/?scene=2

Since these users never click a download button, they will never trigger a download event. How do we want to track these users' downloads?

Possible options:
1. Move download logic to fire on load of scene 2 rather than button click
2. Fire separate tags on both click and initiation to itemize separate data points
3. Create logic that can detect if a tag has been initiated on load of scene 2

Ideal outcome:
1. Know the volume of clicks to download by build, channel, etc.
2. Know the volume of download initiations or completions by build, channel, traffic source, etc (traffic source includes all 3rd party domains that send folks directly to scene 2).
(Reporter)

Comment 1

a year ago
After discussing with Craig Cook, it sounds like the best option is to trigger a download on scene two. Developers will build logic that initiates an event for visits landing directly on scene 2.

Please have this event occur only for downloads that have been initiated by a user landing directly on /firefox/new/scene=2

dataLayer.push({
  'data-download-os': '<os>', //acceptable values include: Desktop, Android, iOS
  'data-download-version': '<version>', //acceptable values include: win, win64, osx, linux, linux64, android, ios,
  'data-download-language': '<lang>', //Use same language field that is being used in click of existing download button
  'event': 'download-scene2'
});

@Eric, can you assign this to one of our developers?
Flags: needinfo?(erenaud)
I just want to call out the fact that we may not be able to code a solution that only addresses users "landing directly" on scene2, because we can only know so much about referrers. So we should be open to alternative implementations than the one specified in comment 2, such as...
* preventing scene2 loads unless someone clicks on an "official" download button and gets a nonce or something, or
* stop treating "download button clicks" as a proxy for download, and only treat "scene2 pageloads" as the proxy
* etc.
(Reporter)

Comment 3

a year ago
@Dev Team - Can you make a recommendation on what would be the most reliable solution?
Flags: needinfo?(jon)
Flags: needinfo?(craigcook.bugz)
Flags: needinfo?(agibson)
(In reply to pgerman from comment #3)
> @Dev Team - Can you make a recommendation on what would be the most reliable
> solution?

I think Craig's proposed solution is the cleanest - just move tracking to when the user lands on scene2 (this is where we used to have it originally).

We're all focused on hub work right now, so this will need to go in the backlog.
Flags: needinfo?(jon)
Flags: needinfo?(craigcook.bugz)
Flags: needinfo?(agibson)
(Reporter)

Comment 5

a year ago
@Alex, re: timing - understood.

I'll build something temporary to make sure that we're tracking the download. But it will be good to get something a little bit more robust when we can get to this in the backlog.

@Eric, let's make sure this is prioritized shortly after the hub goes live.
I've added this to our unassigned tasks users story - https://tree.taiga.io/project/malexis-mozillaorg-durable-team/task/1374?kanban-status=628903
Flags: needinfo?(erenaud)
@pg, didn't you resolve this using GA?
Flags: needinfo?(pgerman)
(Reporter)

Comment 8

a year ago
Correct. I built a rule in GTM. Closing.
Status: NEW → RESOLVED
Last Resolved: a year ago
Flags: needinfo?(pgerman)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.