Affiliate Compliance for Browser Extensions

8 min

Overview Overview

Affiliate browser extensions must follow strict policies from major affiliate networks to ensure fair participation in affiliate marketing. These rules exist to prevent extensions from unfairly taking credit for sales, protect publishers’ efforts, and provide a clear, trustworthy user experience.

Compliance is not optional — networks actively monitor behavior and can suspend extensions that violate these requirements. This document provides a generalized view of compliance requirements for affiliate extensions, with a detailed section on the stand-down policy.

Core Compliance Principles Core Compliance Principles

1. User-Initiated Activation Only 1. User-Initiated Activation Only

• Extensions must never fire an affiliate link or set a cookie without explicit user action.
• A user must intentionally click a button or choose to activate cash back.
• Automatic redirects or hidden cookie drops (often called cookie stuffing) are prohibited.
• Simply visiting a merchant site must not trigger affiliate tracking on its own.
• The activation link or button must be clear and visible — it cannot be disguised or hidden in a way that prevents the user from understanding they are initiating affiliate tracking.

2. Stand-Down on Existing Affiliate Links 2. Stand-Down on Existing Affiliate Links

If a user arrives at a merchant already affiliated through another publisher (e.g., a blog, email, or another extension), your extension must stand down:

• No pop-ups or activation prompts should appear. See section 5 below for other disallowed activities.
• The extension must not overwrite or warn about the existing affiliation.
• The user should remain with the originally credited affiliate.

This prevents confusion (e.g., a shopper thinking they can “stack” cash back across extensions) and ensures publishers get proper credit.

Note: Users are allowed to change affiliation but must take action on their own (e.g. invoking the extension icon) to do so. If a user activates through your extension but then that affiliation is lost/overwritten (e.g. a user clicks to reveal a coupon on a website and that website gains the attribution for the user), your software is allowed to prompt the user to let them know that they lost their previous affiliation and offer to reaffiliate with your software.

3. How to Detect Affiliate Traffic 3. How to Detect Affiliate Traffic

Extensions determine when to stand down by detecting affiliate tracking. This typically involves:

• URL parameters that indicate affiliate referrals, such as:
  • afsrc=1
  • affsource=1
  • foid
• Affiliate tracking domains (commonly used in redirects). Examples include:
  • anrdoezrs.net
  • commission-junction.com
  • dpbolvw.net
  • linksynergy.com
  • jdoqocy.com
  • kqzyfj.com
  • tkqlhce.com
  • emjcd.com
  • ftjcfx.com

Safari Limitation: Safari extensions cannot observe redirect sequences. They must rely solely on detecting affiliate parameters in the final landing page URL.

4. Duration of Stand-Down 4. Duration of Stand-Down

Once an affiliate referral is detected, the extension must remain passive for the duration of the user’s session.

• During this period, do not prompt, redirect, or otherwise market to the user.

Wildfire makes no claims about how a session should be defined.

5. What Counts as “Marketing to the User” 5. What Counts as “Marketing to the User”

Affiliate networks define “marketing” broadly as anything designed to capture the user’s attention and encourage cash back activation. Examples of prohibited actions during stand-down:

• Displaying a modal or popup to activate cash back automatically.
• Animating or flashing the extension icon.

Allowed behavior:

• Showing the extension icon in a static, filled color state to indicate merchant eligibility.
• Continuing to allow user-initiated activation once the session timeout has passed.
• Allowing activation if the user engages with the extension icon directly.
• Prompting upon "losing" affiliation (see note in #2 above)

6. No Automatic Redirects of Organic Traffic 6. No Automatic Redirects of Organic Traffic

• Direct or search-originating traffic must not be secretly funneled through affiliate URLs.
• User intent and click are required for activation.
• This prevents “hijacking” of organic sessions.

7. User Transparency and Control 7. User Transparency and Control

• Notifications must be clear, reasonably sized, and relevant.
• Extensions must act like assistants, not intrusions.

Summary Summary

A compliant affiliate extension will:

• Only activate with user intent.
• Stand down gracefully when another affiliate is in play.
• Never overwrite or warn about existing affiliates.
• Provide clear, user-friendly controls.

Non-compliance risks user trust and can lead to suspension by affiliate networks. By following these guidelines and testing rigorously, extensions can maintain compliance while delivering value to both users and partners.

Updated 16 Jun 2026