Firefox Accounts Referrals

Marketing pages often promote the creation of a Firefox Account (FxA) as a common call to action (CTA). This is typically accomplished using either a signup form, or a prominent link/button. Other products such as Mozilla VPN use similar Firefox Account auth flows to manage subscriptions. To accomplish these tasks, bedrock templates can take advantage of a series of Python helpers which can be used to standardize product referrals, and make supporting these auth flows easier.

Note

The helpers below can typically be shown to all browsers, but some also feature logic specific to desktop Firefox, such as signing users into Sync.

Firefox Account Signup Form

Use the fxa_email_form macro to display a Firefox Account signup form on a page.

Usage

To use the form in a Jinja template, first import the fxa_email_form macro:

{% from "macros.html" import fxa_email_form with context %}

The form can then be invoked using:

{{ fxa_email_form(entrypoint='mozilla.org-firefox-accounts') }}

The template’s respective JavaScript and CSS bundles should also include the following dependencies:

Javascript:

js/base/mozilla-fxa-form.js
js/base/mozilla-fxa-form-init.js

CSS:

@import '../path/to/fxa-form';

The JavaScript files will automatically handle things adding metrics parameters, as well as configuring Sync and distribution ID (e.g. the China re-pack) for Firefox desktop browsers (more info on these further down the page). The CSS file contains some default styling for the signup form.

Configuration

The signup form macro accepts the following parameters (* indicates a required parameter)

Parameter name

Definition

Format

Example

entrypoint*

Unambiguous identifier for which page of the site is the referrer.

mozilla.org-directory-page

‘mozilla.org-firefox-accounts’

entrypoint_experiment

Used to identify experiments.

Experiment ID

‘whatsnew-headlines’

entrypoint_variation

Used to track page variations in multivariate tests. Usually just a number or letter but could be a short keyword.

Variant identifier

‘b’

style

An optional parameter used to invoke an alternatively styled page at accounts.firefox.com.

String

‘trailhead’

class_name

Applies a CSS class name to the form. Defaults to: ‘fxa-email-form’

String

‘fxa-email-form’

form_title

The main heading to be used in the form (optional with no default).

Localizable string

_(‘Join Firefox’)

intro_text

Introductory copy to be used in the form. Defaults to a well localized string.

Localizable string

_(‘Enter your email address to get started.’)

button_text

Button copy to be used in the form. Defaults to a well localized string.

Localizable string

_(‘Sign Up’)

button_class

CSS class names to be applied to the submit button.

String of one or more CSS class names

‘mzp-c-button mzp-t-primary mzp-t-product’

utm_campaign

Used to identify specific marketing campaigns. Defaults to fxa-embedded-form

Campaign name prepended to default value

‘trailhead-fxa-embedded-form’

utm_term

Used for paid search keywords.

Brief keyword

‘existing-users’

utm_content

Declared when more than one piece of content (on a page or at a URL) links to the same place, to distinguish between them.

Description of content, or name of experiment treatment

‘get-the-rest-of-firefox’

Invoking the macro will automatically include a set of default UTM parameters as hidden form input fields:

  • utm_source is automatically assigned the value of the entrypoint parameter.

  • utm_campaign is automatically set as the value of fxa-embedded-form. This can be prefixed with a custom value by passing a utm_campaign value to the macro. For example, utm_campaign='trailhead' would result in a value of trailhead-fxa-embedded-form.

  • utm_medium is automatically set as the value of referral.

Common FxA Parameters

The fxa_button, pocket_fxa_button, and monitor_fxa_button helpers all support the same standard parameters:

Parameter name

Definition

Format

Example

entrypoint*

Unambiguous identifier for which page of the site is the referrer. This also serves as a value for ‘utm_source’.

‘mozilla.org-firefox-pocket’

‘mozilla.org-firefox-pocket’

button_text*

The button copy to be used in the call to action.

Localizable string

‘Try Pocket Now’

class_name

A class name to be applied to the link (typically for styling with CSS).

String of one or more class names

‘pocket-main-cta-button’

is_button_class

A boolean value that dictates if the CTA should be styled as a button or a link. Defaults to ‘True’.

Boolean

True or False

include_metrics

A boolean value that dictates if metrics parameters should be added to the button href. Defaults to ‘True’.

Boolean

True or False

optional_parameters

An dictionary of key value pairs containing additional parameters to append the the href.

Dictionary

{‘s’: ‘ffpocket’}

optiona_attributes

An dictionary of key value pairs containing additional data attributes to include in the button.

Dictionary

{‘data-cta-text’: ‘Try Pocket Now’, ‘data-cta-type’: ‘activate pocket’,’data-cta-position’: ‘primary’}

Note

The fxa_button helper also supports an additional action parameter, which accepts the values signup, signin, and email for configuring the type of authentication flow.

Tracking External Referrers

If the URL of a bedrock page contains existing UTM parameters on page load, bedrock will attempt to automatically use those values to replace the inline UTM parameters in Firefox Account and Mozilla VPN links. This is handled using a client side script in the site common bundle which can be found in /media/js/base/fxa-utm-referral.js.

The behavior is as follows:

  • UTM paramters will only be replaced if the page URL contains both a valid utm_source and utm_campaign parameter. All other UTM parameters are considered optional, but will still be passed as long as the required parameters exist.

  • If the above criteria is satisfied, then UTM parameters on FxA links will be replaced in their entirety with the UTM parameters from the page URL. This is to avoid mixing referral data from different campaigns.

Important

Links generated by the FxA button helpers will automatically be covered by this script. For links generated using the fxa_link_fragment helper, you will need to manually add a CSS class of js-fxa-cta-link to trigger the behavior.

URL Parameter Conventions

When choosing URL parameter values, the following conventions help to support uniformity in code and predictability in retroactive analysis.

  • Use lower case characters in parameter values.

  • Separate words in parameter values with hyphens.

  • Follow parameter naming patterns established in previous iterations of a page.

Firefox Sync and UITour

Since Firefox 80 the FxA link and email form macros use UITour to show the Firefox Accounts page and log the browser into Sync or an Account. For non-Firefox browsers or if UITour is not available, the flow uses normal links that allow users to log into FxA as a website only without connecting the Firefox Desktop client. This UITour flow allows the Firefox browser to determine the correct FxA server and authentication flow. This transition was introduced to later migrate Firefox Desktop to an OAuth based client authentication flow.

The script that handles this logic is /media/js/base/mozilla-fxa-link.js, and will automatically apply to any link with a js-fxa-cta-link class name. The current code automatically detects if you are in the supported browser for this flow and updates links to drive them through the UITour API. The UITour showFirefoxAccounts action supports flow id parameters, UTM parameters and the email data field.

We hope to remove the legacy non-UITour login logic after 1 or 2 ESRs.

Handling Distribution (aka China Repack)

The China repack of Firefox points to https://accounts.firefox.com.cn/ by default for FxA accounts signups. To compensate for this on https://www.mozilla.org (so we don’t send those visitors to the wrong place), we rely on UITour to check the distribution ID of the browser. If the distribution ID is mozillaonline (i.e. China repack), then we replace our accounts endpoints with the alternate domain specified in the data-mozillaonline-link attribute. The logic to handle this is self contained in the associated helper scripts and handled automatically.

Note

This logic does not apply to Mozilla VPN, since the product is not available in China.

Testing Signup Flows

Testing the Firefox Account signup flows on a non-production environment requires some additional configuration.

Configuring bedrock:

Set the following in your local .env file:

FXA_ENDPOINT=https://stable.dev.lcip.org/

For Mozilla VPN links you can also set:

VPN_ENDPOINT=https://stage-vpn.guardian.nonprod.cloudops.mozgcp.net/
VPN_SUBSCRIPTION_URL=https://accounts.stage.mozaws.net/

Note

The above values for staging are already set by default when Dev=True, which will also apply to demo servers. You may only need to configure your .env file if you wish to change a setting to something else.

Local and demo server testing:

Follow the instructions provided by the FxA team. These instructions will launch a new Firefox instance with the necessary config already set. In the new instance of Firefox:

  1. Navigate to the page containing the Firefox Accounts CTA.

  2. If testing locally, be sure to use 127.0.0.1 instead of localhost

Google Analytics Guidelines

For GTM datalayer attribute values in FxA links, please use the analytics documentation.