Back to GrowthDex
Growth idea action plan

Firefox Add-ons UTM-tagged AMO links by channel

Append UTM tags to every AMO listing link so the add-on dashboard can separate installs by source, channel, placement, and campaign instead of lumping launch traffic together.

rare tactic
Best-fit channelMarketplaces · Analytics · Distribution
Stage + contextbrowser extensions · firefox add-ons · attribution · channel measurement
BudgetFreebudget tier
Suggested operator signalTarget users who complete the tactic’s intended next action

Why this can grow a startup

A lot of extension teams celebrate installs without learning where the useful traffic came from. Mozilla's AMO stats dashboard supports standard UTM parameters on listing links and breaks downloads out by those tags. That turns the listing into a cleaner measurement surface. The team can compare a homepage button, a blog post, a release thread, and a social post without guessing from timing alone. Better attribution makes future promotion calmer because the next push can follow the channel that produced real installs, not the loudest impressions.

Source-backed example

Firefox Extension Workshop says AMO tracks standard UTM parameters such as source, medium, content, and campaign as additional sources in the add-on download statistics dashboard.

Source-reported evidence

Source: Firefox Extension Workshop: Monitoring extension usage statistics

AMO supports utm_source, utm_medium, utm_content, and utm_campaign on listing links, with a 40-character limit per value.

Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.

Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.

MarketplacesAnalyticsDistributionbrowser extensionsfirefox add-onsattributionchannel measurement
GrowthDex operator note

When to use it

Use this when Marketplaces, Analytics, Distribution is relevant to browser extensions, firefox add-ons, attribution and you can run a bounded test with a free budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

How to do it

  1. Choose one target segment and define the exact next action this tactic should prompt.
  2. Adapt the tactic to Marketplaces and Analytics, using evidence from Firefox Extension Workshop: Monitoring extension usage statistics as context—not as a promised result.
  3. Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
  4. Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
  5. Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Next move

Compare a stack for your situation

Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.

Build my stack

Explore the context

Creator and Community GrowthMarketplacesAnalyticsDistribution

Related tactics

Chrome Web Store country metrics before localization

Use store visitor and install data by country and language before localizing the listing, so translation work follows demand instead of founder guesswork.

rareMarketplaces, Localization, Analytics

GitHub Marketplace checkout funnel before listing rewrite

Read the Marketplace landing-to-checkout funnel before rewriting the listing so the team knows whether the leak is discovery, consideration, or conversion.

rareMarketplaces, Analytics, Conversion

Google Workspace GA4 listing analytics before copy rewrites

Opt in to GA4 for the Marketplace listing before rewriting screenshots or descriptions so the team can see which traffic sources and install events are actually moving.

uncommonMarketplaces, Analytics, Conversion

Google Workspace marketer access to listing GA4

Grant marketer access to the Google-owned GA4 property so the people rewriting the listing can see traffic sources, geographies, and install behavior without waiting on engineering exports.

rareMarketplaces, Analytics, SEO

Firefox Add-ons name earns the slug

Pick a descriptive add-on name early, because AMO turns that choice into the public slug and a vague title makes both search and trust weaker.

rareMarketplaces, SEO, Brand

Firefox Add-ons paid function disclosed on listing

State on the listing when payment unlocks any feature, so the install does not feel like a bait-and-switch after the review queue clears.

rareMarketplaces, Revenue, Brand
Close the loop

Did you launch this experiment?

Report a launch to help us understand which growth ideas founders put into practice.

This report uses a pseudonymous browser ID. Prompts, names, email, or free-text are not included in outcome events.

Advisory bridge

Apply this with an operator

Build creator and community systems around real incentives, trust, and repeat participation.

Work with Ian