Closed Bug 708791 Opened 13 years ago Closed 13 years ago

[Firefox for Android] Set up interstitial page

Categories

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

Product:
www.mozilla.org
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: christine.brodigan, Assigned: jlong)

References

Details

Steven/James,

Goal: track Android Market clickthroughs

Deadline: must go into production for the 4.11, Dec 22 release

Tactic:

*Create an interstitial webpage that contains the Download Android Webtrends tag (see Bug 706720)
*Link to this page from the Download Firefox for Android buttons 
*Redirect to https://market.android.com/details?id=org.mozilla.firefox after rendering the page

Similar to: This is how Laura F. tracks snippet clicks
I think we would have to implement this sooner in order to get the tags implemented in the other pages on time before Dec 20 right? Would this be possible? 

Many thanks!
(In reply to Jaclyn Fu from comment #1)
> I think we would have to implement this sooner in order to get the tags
> implemented in the other pages on time before Dec 20 right? Would this be
> possible? 
> 
> Many thanks!

Jaclyn, it's pretty late for 4.10, assigning to Laura F. to see if she can bump something or find an available webdev resource. Fingers crossed.
Assignee: jlong → lforrest
Hi Fred- Can you help find a resource here? SilverOrange is busy, and James is working on Bedrock and the newsletter.
Assignee: lforrest → fwenzel
So it's just a blank page? After downloading, wouldn't the user be sitting on a blank page? That doesn't seem the most ideal. Just a thought.

Is the tracking done on the referring page that simply links to this page?

If it doesn't require building out a page, I can probably do it this week.
So when users click on our mobile download button, it will go to this blank page, which will then immediately redirect to https://market.android.com/details?id=org.mozilla.firefox - the tracking will be done on the blank page (because we can't add a tracker to an external non-Mozilla page like the Android Market)

Will users see a completely blank page or will it redirect fast enough so they don't notice?
This probably shouldn't be a blank page. If it's necessary, it should probably work like this page: http://www.mozilla.org/en-US/m/download-android.html (the destination of the main download button on mozilla.org/m/
(In reply to Steven Garrity from comment #6)
> This probably shouldn't be a blank page. If it's necessary, it should
> probably work like this page:
> http://www.mozilla.org/en-US/m/download-android.html (the destination of the
> main download button on mozilla.org/m/

How is that page different from what this bug is about? Strikes me as exactly the same thing (interstitial before downloading Fx for Android)?

If it *is* different, then I agree with Steven that we could just copy-and-paste that page and replace the tracking code and redirect target.

(In reply to mcbmoz from comment #0)
> Similar to: This is how Laura F. tracks snippet clicks

Hmm, I asked and it seems it's not quite the same. Snippets usually just pass a GET parameter to the target site which then does the tracking (obviously not an option here). One exception was the Personas tracking, which would post to Webtrends via AJAX on click. That would be an option here too, but I am not sure if that AJAX cross-domain model is universally usable (outside about:home, that is).

So the easiest and most promising option is probably indeed a copy of the interstitial in comment 6.
The interstitial page on http://www.mozilla.org/en-US/m/download-android.html is for mobile only right now, and this bug is for a desktop interstitial page. 

Another difference with the mobile-optimized interstitial page is that it opens up the Android Market in-app, whereas this desktop page would redirect to the Web version of the Android Market.

Should we still copy and paste? Is there another solution? Or would Creative have to whip something up?
The only problem is that page is designed for mobile. We can copy it, but we might want to have creative take a quick look at it to make it look less bare-bones on the  desktop.
Just talked to Tara about what this page might look like. So instead of a "thank you" message, there will be an "in progress" type message (since this page will mainly flash by quickly, and users wouldn't have downloaded it yet). 

The page will be mainly simple, except with the copy + possibly Firefox logo. Too much content will be distracting when it's being redirected. 

Filing Creative bug!
Depends on: 709961
Just checking in...is creating a new page the best/only way to solve the original problem, which seems to be that we need to track clickthroughs to the Android Market? 

I ask b/c creating a page at the last minute when there's lots of other stuff going on isn't really ideal if it can be avoided. Would be great if we could take a quick step back and reassess.
You know what, I may have misunderstood the original idea. This is for *desktop* users to download *mobile* firefox, is that right? So desktop users will be redirected to the Android market website, they won't receive a download prompt?

I was under the impression that they would see a download prompt, which is why a blank page would be bad. But I think I'm ok with a blank page if it redirects them to the Android market. The only issue is that it's a lot slower.
So it sounds like from chatting with james that a blank page will be fine, but we should test for any blank page lag time. Let's move forward with blank page!
No longer depends on: 709961
Blank is okay for now, but the experience is pretty bad if, say, the android market is down: Then people see a blank page and will never move on from it. So there's a price to the simplicity.
(In reply to Fred Wenzel [:wenzel] from comment #14)
> Blank is okay for now, but the experience is pretty bad if, say, the android
> market is down: Then people see a blank page and will never move on from it.
> So there's a price to the simplicity.

That's fine Fred, thanks for the info though. 

When can we start to test this out? We should make sure there's no noticeable lag time.
Assignee: fwenzel → jlong
OS: Mac OS X → All
Hardware: x86 → All
I'll get it done today or tomorrow.
Blocks: 706720
No longer depends on: 706720
ping jlongster - how is this doing? thanks!
Will try to have done by the end of day today!
I need the tracking code to be put in bug 706720 before I can finish this.
what URL should I use to tag with the WT tracker? does this interstitial page have a new URL or are we using the final destination URL https://market.android.com/details?id=org.mozilla.firefox?
The page I'm making is at:

/<lang>/mobile/android-download

Where <lang> is the current locale.
I'm confused if it's just the normal tracking code or not. I've setup a blank page which will redirect with the normal tracking code. Please view the source and see if it's right:

https://www-dev.allizom.org/en-US/mobile/android-download.html
Brad - Can you help out here?
This is fully setup on trunk. Please test the page in comment 22.
Whiteboard: r=98969,98973 b=trunk
I took a look and it appears to be functioning correctly.
I created a report entitled 'TEST Android Marketing Campaign (Interstitial Redirect)' it has been added to the mozilla/firefox profile and will start collecting data when the page and associated campaigns go live.
Cool. Someone, please ping me when this should go out, otherwise it will go out on Tuesday.
Thanks James and Brad! 

James - is the earliest it can go out Tuesday? the sooner the better if possible
Nope, I can roll it out Monday if needed.
Monday would be great! Thanks!
I created an additional test report entitled 'Test Android Marketing Campaign w/ Referring Page (Interstitial Redirect)'.
pushed to production r99087
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: r=98969,98973 b=trunk
Component: www.mozilla.org/firefox → www.mozilla.org
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.