If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[Fx17] Implement new Facebook Tab

RESOLVED INCOMPLETE

Status

www.mozilla.org
Pages & Content
P1
normal
RESOLVED INCOMPLETE
5 years ago
5 years ago

People

(Reporter: Laura Forrest, Assigned: jpetto)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: u=user c=SocialAPI p=3)

Attachments

(1 obsolete attachment)

(Reporter)

Description

5 years ago
Please implement a new Tab connected to our Facebook Messenger for Firefox launch. This will be part of our overall Facebook social media account. 

Please also be sure to make this page trackable. We'll want to know: 
1. how many visits it gets 
2. how many people watch the video 
3. Most importantly, how many people click the main "Get it now" (or whatever) button.

Comment 1

5 years ago
Please note that this page will also have some subtle animation.  As dicsussed, we're looking at creating a live newsfeed (with an update rolling in every several seconds or so) MikeA/ChrisM had said that they will be doing a prototype of this to test before the designs are done.

Comment 2

5 years ago
animation moved to separate bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=808958

Updated

5 years ago
Assignee: malexis → jon
Priority: -- → P1
Whiteboard: u=user c=SocialAPI p=3
(Reporter)

Comment 3

5 years ago
Requirement: Be sure to give this new page a shortened URL via the facebook admin setup (I believe that's where that happens). /fxmessenger would be good.

Comment 4

5 years ago
Jon: If you have questions about the L10N side of this Bedrock page and the Facebook requirements, please talk to Mike Kelly (:mkelly) in the #webprod channel on IRC. He did something very similar for the Affiliates Facebook tab.

Affiliates facebook page: https://www.facebook.com/Firefox/app_373528039377278
Affiliates facebook code: https://github.com/mozilla/affiliates/tree/master/apps/facebook

Affiliates is also a Django site and it is similar, but not exactly the same as Bedrock. If you join us in #webprod on Mozilla's IRC, you will get quicker help.
(Reporter)

Updated

5 years ago
Blocks: 808713

Comment 5

5 years ago
Reiterating specs:

* this tab will have two states 
* it will browser sniff and serve the appropriate state for: FF 17 users, and non Fx or pre-Fx17 users. 
* we are plugging in the video via youtube embed. 
* we'd like to make sure that if the custom tab page is shared, the facebook messenger icon is what is shared in the feed. we'll provide that. 
* lets track the crap out of this page :) 

* final delivery of assets are coming up very very soon!

Comment 6

5 years ago
this page is also localized - chelsea can speak to that.
Localized copy for this will be ready on Wednesday.

Comment 8

5 years ago
making small changes to the hero image - please hold on implementation till that's final - unless it won't affect your work.  just fyi.  will be uploaded in the next few hours - asap.
(Assignee)

Comment 9

5 years ago
I'll be starting implementation Monday morning. Just post the PSD when it's ready.

Thanks.

Comment 10

5 years ago
thanks.  I wanted to also add that this custom tab should be viewable in a logged-off state.  that's very very important as we are directing traffic here from various channels and we are accounting for people who may not be on facebook.
(Reporter)

Comment 11

5 years ago
(In reply to Jon Petto from comment #9)
> I'll be starting implementation Monday morning. Just post the PSD when it's
> ready.
> 
> Thanks.

This page is now done! You can have at it here: https://bugzilla.mozilla.org/show_bug.cgi?id=805237#c13
(Reporter)

Comment 12

5 years ago
Let's use this technical iFrame URL from mozilla.org for this tab: 

www.mozilla.org/facebookmessengertab 

If Facebook offers a custom URL with their root domain we'd like: 

www.facebook.com/fxmessenger (this follows the standard of our other tabs)
(Reporter)

Comment 13

5 years ago
Adding Bill from Webtrends to this bug so he can advise on implementing any Webtrends reporting if needed. 

Bill -- on this page we'll need to: 

1. Track WT marketing tags through a custom conversion event, the click on the main button. Meaning be able to see the conversion rate of each marketing source through the button click

2. Basic page views, referral sources, etc. 

Here's a mockup of the page: https://bugzilla.mozilla.org/show_bug.cgi?id=805237#c13

If custom code is needed please post to this bug with directions for WebDev. 

If any custom webtrends reports need to be created, please create those before next Tuesday 11/20 so that the data will be captured from day 1.

Comment 14

5 years ago
I'm assuming that WT.mc_id, our campaign parameter, will be appended to any incoming URLs that you want to track for marketing purposes. 

For the onClick or onMouseDown event:
dcsMultiTrack('DCS.dcssip','mozilla.org','DCS.dcsuri','/facebook_messenger.button','WT.ti','Facebook Messenger','WT.dl','26','WT.conv','1')
(Reporter)

Comment 15

5 years ago
(In reply to Bill from comment #14)
> I'm assuming that WT.mc_id, our campaign parameter, will be appended to any
> incoming URLs that you want to track for marketing purposes. 
> 
> For the onClick or onMouseDown event:
> dcsMultiTrack('DCS.dcssip','mozilla.org','DCS.dcsuri','/facebook_messenger.
> button','WT.ti','Facebook Messenger','WT.dl','26','WT.conv','1')

Thanks Bill! Yes, we'll use marketing tags. 

Jon -- Please put that code above on the main button, both states, to allow us to track. Thanks!

Comment 16

5 years ago
One addition needed. Please change '/facebook_messenger.button' to 'facebook_tab/facebook_messenger.button'

Comment 17

5 years ago
Hi there, wanted to add the custom tab app's thumbnail image.  Not sure if it's part of this bug or not, but sharing anyway. 

* mockup: https://bugzilla.mozilla.org/attachment.cgi?id=681695&action=edit
* design: https://bug811589.bugzilla.mozilla.org/attachment.cgi?id=681684
(Reporter)

Comment 18

5 years ago
The localizations for this page are ready. They are attached in 21 different languages. 

Video: Please do not include the video portion of this page. The Video has not yet been localized. 

Button Tracking: Please add the same tracking mentioned in Comment 14 to each button

The strings can be found in the files called: 

Hero Graphic 
SocialAPI_FB_Custom
Tab_NoFFx  
SocialAPI_FB_CustomTab
(Reporter)

Comment 19

5 years ago
Created attachment 681774 [details]
Localizations Ziped

Localizations
(Reporter)

Comment 20

5 years ago
Comment on attachment 681774 [details]
Localizations Ziped

This format did not come through well on Bugzilla. I will post using a different mechanism.
Attachment #681774 - Attachment is obsolete: true
(Reporter)

Comment 21

5 years ago
===Localization File====

I'm unable to attach the file to Bugzilla so am posting links to the files two different ways here. 

1. Dropbox https://dl.dropbox.com/u/76193488/Social_API_translated_21_languages.zip

2. Basecamp: https://basecamp.com/1897137/projects/1351525-social-api/messages/6159899-l10n-update#comment_31803309

I will also email them.
(Reporter)

Comment 22

5 years ago
Here are three more locales, I've also emailed them. 

1. Dropbox: 

https://dl.dropbox.com/u/76193488/Social%20API%20Translations%203%20More%20Locales.zip

2. Basecamp: https://basecamp.com/1897137/projects/1351525-social-api/messages/6159899-l10n-update#comment_31837026
(Assignee)

Comment 23

5 years ago
Regarding the buttons (Firefox & Messenger), what are their respective destinations? Do we want the Firefox button linking to the download page (https://www.mozilla.org/en-US/products/download.html)?

Do we have a download page link for Messenger yet?

Comment 24

5 years ago
Jon: Here are the button URLs:

Download Firefox: http://www.mozilla.org/firefox/new/ (don't include the locale)

Get Started with Facebook Messenger: https://www.facebook.com/about/messenger-for-firefox

Laura: can you confirm this is where you wanted the buttons to go? The download button on the Facebook tab will have to go to the /new page because the there is no logic (platform+locale+channel) behind the button on the tab.
(Reporter)

Comment 25

5 years ago
(In reply to Chris More [:cmore] from comment #24)
> Jon: Here are the button URLs:
> 
> Download Firefox: http://www.mozilla.org/firefox/new/ (don't include the
> locale)
> 
> Get Started with Facebook Messenger:
> https://www.facebook.com/about/messenger-for-firefox
> 
> Laura: can you confirm this is where you wanted the buttons to go? The
> download button on the Facebook tab will have to go to the /new page because
> the there is no logic (platform+locale+channel) behind the button on the tab.

Yes, confirmed for now. 

We're creating a custom landing page for these people, but since this can't be localized we may be limited for this initial launch, and have to send users to http://www.mozilla.org/firefox/new/  instead of the page we're creating in Bug 808570: mozilla.org/firefox/facebookmessenger. I will move doing this to the post-launch phase.
(Assignee)

Comment 26

5 years ago
I've got a version of the tab ready for review. Should I submit a pull request to the dev branch of bedrock? Is that the best way for everyone to take a look?

Comment 27

5 years ago
Laura - When you get the URL for the iFrame let me know so I can create the filters I need. Also is the download button tagged so we can track it also?
(Reporter)

Comment 28

5 years ago
Jon -- Here's the video information you'll need in order to embedd: https://bugzilla.mozilla.org/show_bug.cgi?id=811533#c7

Thanks!
(Reporter)

Comment 29

5 years ago
(In reply to Bill from comment #27)
> Laura - When you get the URL for the iFrame let me know so I can create the
> filters I need. 

Jon -- Can you confirm the iFrame URL for Bill?

>Also is the download button tagged so we can track it also?

Jon -- can you confirm that the button (both states) is tagged? The info to tag the button is in Comment 14.
(Assignee)

Comment 30

5 years ago
The iFrame URL will be http://www.mozilla.org/facebookmessengertab. The URL will be localized.

Both states of the button have the following attached to the click handler:

dcsMultiTrack('DCS.dcssip','mozilla.org','DCS.dcsuri','facebook_tab/facebook_messenger.button','WT.ti','Facebook Messenger','WT.dl','26','WT.conv','1');

I'll get working on embedding the video shortly.

Comment 31

5 years ago
Are we tracking the download button?
http://www.mozilla.org/firefox/new/
(Reporter)

Comment 32

5 years ago
Bill: if we use this domain www.mozilla.org/facebookmessengertab  with MMC tags, and link users to a iFrame hosted Facebook tab, will the marketing tags be truncated? Please advise.
(Reporter)

Comment 33

5 years ago
(In reply to Bill from comment #31)
> Are we tracking the download button?
> http://www.mozilla.org/firefox/new/

That page and that button is currently tracked, yes. But I encourage you to take a look at the source code to make sure it's current tags will work for this campaign. I'm no engineer!
(In reply to Jon Petto from comment #26)
> I've got a version of the tab ready for review. Should I submit a pull
> request to the dev branch of bedrock? Is that the best way for everyone to
> take a look?
Please submit your Pull Request against the facebook-tab-firefox-17 branch. We'll then put it on a demo server.
(Assignee)

Comment 35

5 years ago
A pull request has been submitted:

https://github.com/mozilla/bedrock/pull/477

Comment 36

5 years ago
(In reply to Laura Forrest from comment #32)
> Bill: if we use this domain www.mozilla.org/facebookmessengertab  with MMC
> tags, and link users to a iFrame hosted Facebook tab, will the marketing
> tags be truncated? Please advise.

As long as the domain and dcsid remains the same we will preserve the tag. The report will look at the campaign on a visit level so as long as we see the tag at least once we are good.

Comment 37

5 years ago
(In reply to Jon Petto from comment #35)
> A pull request has been submitted:
> 
> https://github.com/mozilla/bedrock/pull/477

Thanks, Jon! We'll get a review done on this.
It is my understanding that the URL for this page is not exposed to visitors. Can we change it to http://www.mozilla.org/firefox/facebookmessengertab/ ? (aka adding the /firefox/ part). I think it makes sense for our information architecture to keep all things related to Firefox under this folder.

Comment 39

5 years ago
(In reply to Anthony Ricaud (:rik) from comment #38)
> It is my understanding that the URL for this page is not exposed to
> visitors. Can we change it to
> http://www.mozilla.org/firefox/facebookmessengertab/ ? (aka adding the
> /firefox/ part). I think it makes sense for our information architecture to
> keep all things related to Firefox under this folder.

+1. We won't be pointing people directly to the tab outside of the Facebook experience and the URL will be hidden due to the iframe. People would have to right click and open frame in new window to get the URL.
Closing as resolved - incomplete until project picks back up again.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.