Adding different utm parameters for the desktop in-app conversion flow

[data-sync-user]

From this thread discussion:

I found that the in-app conversion process through the desktop app  uses the web check out flow and this traffic would show up in data identically as FxA signed-in with Direct channel in the desktop conversion flow. (Monthly in-app traffic size going into the checkout page which is included in Monthly sign-in FxA subscription traffic from “Direct” channel i.e. utm_source=www.mozilla.org-vpn-product-page&utm_medium=referral&utm_campaign=vpn-product-page)

Potential issues that I can think of from this:

• We don’t know how much traffic drops off when users are led from the app to the checkout page.
• In accurate tracking in direct existing fxa signed-in group starting from the product page
• Possible double counting in the mobile and the desktop conversion funnel

Suggestion: differentiating the group coming from the in-app conversion funnel using utm parameters from the direct traffic coming from the traffic starting from the product site.

After discussing with [~accountid:62e6feee32850ea2a32368bb] , [~accountid:6047d245addbcd006ba913b3] , [~accountid:6047c89779f9a90070e914d3] , the appropriate utm parameter values would be:

• utm_medium = vpn-client
• utm_source =  desktop-signup-flow
• utm_campaign = null

And this attributed traffic will be included as product owned channel group.

┆Issue is synchronized with this Jira Task ┆Reporter: Yeonjoo Yoo

[data-sync-user]

➤ Santiago Andrigo commented:

Sarah Bird FYI

[data-sync-user]

➤ Sean Rose commented:

{quote}utm_campaign = null{quote}

This means the utm_campaign value should be blank/empty, right? In which case the utm_campaign parameter could simply be omitted.