AffiliateWP External Referral Links

Updates for one year, unlimited sites, auto updates, and regular updates.

$3.99

Version 1.2.2 report outdated
Updated on November 11, 2026
Auto Updates Yes
License GPLv2+

Access all items listed on our website. All new releases are also included as long as the plan is active.

External Referral Links lets affiliates promote your products from a separate website. Many affiliates run their own blogs, review sites, or campaign pages on a different domain. Without this add-on, a referral that starts on a separate WordPress site is not picked up, so the affiliate earns nothing for the sale. The add-on closes that gap by remembering which affiliate sent the visitor, carrying that information across to your main store, and keeping the referral attributed correctly even though the visit began somewhere else.

The problem it solves

Picture two WordPress sites. Site A is your main store, with AffiliateWP and a commerce or membership plugin installed. Site B is a separate website with its own WordPress installation and database, set up to promote what Site A sells. An affiliate sends visitors from Site B to Site A, but without this add-on, Site B has no code that reads the affiliate’s ID from the address, so the affiliate receives no commission. Installing AffiliateWP and a commerce plugin on Site B does not fix this, because each site keeps its own database and the two do not share data.

How a referral travels between the sites

Affiliates share links on Site B that include their ID or username, such as a link ending in ?ref=123 or ?ref=john. The add-on reads that value through the referral variable and stores it in a cookie in the visitor’s browser. Links from Site B to Site A then carry the saved value forward, so the referral continues when the visitor reaches the store. Visitors can move around Site B as they like. If they leave and return later, the referral is still remembered for as long as the cookie remains valid.

Visit tracking works differently on Site B. The documentation states that no visit entry is created for the external site itself. A visit is recorded only when the visitor clicks back through to Site A. Because of that, the visit numbers an affiliate sees may look lower than the traffic they actually sent, so set expectations with your affiliates before they start reporting on their results.

Setting it up

Install the add-on on Site B, the external site, and leave AffiliateWP on Site A, where your commerce or membership system already runs. Site B must run its own complete WordPress installation. Place the plugin folder inside wp-content/plugins on Site B and activate it from the Plugins screen. You can also search for the plugin name under Plugins, then Add New. Once it is active, affiliates can begin using links that carry their ID or username.

The official material links to AffiliateWP’s integration guides for eCommerce and membership systems, while the installation steps sit in a separate guide. Before you invite affiliates to promote through Site B, run a complete test. Click an affiliate link on Site B, move through to Site A, and complete a test order. Then check the Referrals screen in AffiliateWP to confirm the referral is attributed to the right affiliate.

Keeping both sites in step

Because a referral passes between two independent installations, a change on either site can affect the hand-off. Keep both sites on current WordPress and PHP versions where you can, and repeat your test order after any update to Site A or Site B. Note the date of each change in a simple log, so that if a referral goes missing, you can tell quickly whether a recent update is the likely cause.

Settings

The add-on includes a settings screen, but the only option its documentation describes is cookie expiry. That setting controls how long a referral stays attached to a visitor’s browser. Choose a duration that matches how your affiliates promote the store. A short window suits quick, one-off campaigns, while a longer window gives visitors more time to come back and buy. Test the chosen duration before a campaign launches, because it determines how long a referral can remain in effect.

Limitations to plan around

External Referral Links works only with non-pretty affiliate links. A non-pretty link carries the referral in a query string, such as ?ref=123, rather than in a rewritten path. Decide on your link format before affiliates start sharing URLs, because the examples in the documentation all use the query-string style.

The documentation describes only links that travel from Site B to Site A as carrying the affiliate’s ID or username. Campaign links built for other destinations should be tested separately before they go into use. Taken together, these limits make the add-on a bridge for one specific setup rather than a general tracking solution.

Measuring results

Because visits on Site B are not logged, judge the external site by the referrals and commissions that reach Site A, rather than by visit numbers alone. Compare the referrals generated through Site B with those from your other channels in AffiliateWP’s reporting screens. Look for patterns across several weeks instead of single days, since a referral can be remembered and credited when a visitor returns later through the cookie.

Good fits for this add-on

External Referral Links suits a few common setups. A content site that reviews products can promote your store from its own domain. A campaign microsite can run a short-term promotion without touching the design of your main store. A community or partner site with its own WordPress installation can send members to your store while keeping its own branding. In each case the separate site stays independent, and the add-on carries the affiliate’s identity across to Site A.

Preparing your affiliates

Affiliates need clear instructions before they start linking from their own sites. Give each one the exact link format, with their ID or username placed after the referral parameter. Explain that links must point from Site B to Site A so the stored value can travel with the visitor. Ask them to click their own link once and confirm that the visit reaches the store, so any mistake shows up early.

Troubleshooting checklist

  • Confirm the add-on is active on Site B and that AffiliateWP is active on Site A.
  • Check that affiliate links use the query-string format rather than a pretty permalink.
  • Review the cookie expiry setting and make sure it suits the campaign.
  • Click through from Site B to Site A and confirm the visit is recorded once the visitor returns to Site A.
  • Place a test order and check the Referrals screen for the expected affiliate.

Privacy and cookies

Because the add-on stores a cookie in the visitor’s browser, review your cookie notice and privacy wording so they reflect this behavior. The documentation does not describe the cookie name, the domain it is set on, or its default lifetime, so check those details yourself on a test installation before you publish any policy text.

How a visit travels, step by step

Consider a single visitor. An affiliate publishes a review on Site B and links to your store with a referral value in the address. The visitor clicks the link, and the add-on saves the affiliate’s value in a cookie. The visitor reads more of Site B, leaves for a while, and returns to the review later. The saved value is still there, so the link from Site B to Site A carries it across. The visitor reaches Site A, places an order, and the referral is recorded for the affiliate named in the cookie. Every step depends on the cookie still being valid, which is why its expiry setting matters.

Choosing a cookie window

The cookie window is a planning decision rather than a fixed rule. Campaigns with a deadline, such as a seasonal sale, may suit a shorter window so that a referral does not carry on long after the offer has ended. Evergreen review content may suit a longer window, because readers may return weeks after their first visit. Whichever duration you choose, record it in your campaign notes, so that when an affiliate asks why a referral did or did not count, you can answer quickly.

When this add-on is not the right tool

  • Choose a different approach if the separate site is not a WordPress installation, because the add-on is installed on that site.
  • Choose a different approach if your affiliates rely on pretty permalinks, because the add-on works only with query-string links.
  • Choose a different approach if you need visits on the separate site to appear in AffiliateWP, because those visits are not logged there.
  • Choose a different approach if the separate site must share a database with your store, because the two sites keep their data apart.

Frequently asked questions

Do I need AffiliateWP on Site B? The official setup keeps AffiliateWP on Site A, where referrals and commissions are recorded. Site B needs the add-on and its own WordPress installation.

Can I use pretty links? No. The add-on works only with non-pretty affiliate links, so keep the query-string format.

Does Site B need a store plugin? The official example describes Site B as a site set up to promote the products on Site A. It does not describe a store plugin on Site B.

Similar Products