TEASEDocs
ProductsLinkTroubleshooting

"I created a source rule but the fan still shows up as organic"

A source_link rule tells the resolver which domain a link belongs to — it does not, by itself, re-run attribution for fans who already converted.

Symptom

A source_link rule was created binding a link to a domain/channel (see Create a rule that attributes a link to a source), but a fan who came through that link still shows up as organic, or with no source at all, in Club's fan/attribution views.

Cause

Two separate things have to both be true, and a new rule only guarantees the first:

  • Going forward, new clicks and conversions through that link resolve against the rule immediately — this part works as soon as the rule is saved.
  • Already-existing fans and transactions that arrived before the rule existed are not automatically retro-attributed by creating the rule. Backfilling past fans against a new rule is a separate, deliberate re-attribution step on Club's side, not something Link's rule table triggers on its own.

Rules also only bind a link the owner explicitly created one for. A link with real traffic but no matching rule shows up in Unassigned links instead of silently inheriting any other rule.

How to check

  • Confirm the rule actually matches the link's real provider id/name — a rule keyed on the wrong identity (name prefix vs. exact name, for example) silently matches nothing rather than erroring; see Traffic-sources troubleshooting for the specific rejection/scope cases.
  • Check whether the fan in question converted before or after the rule was created — a timestamp before the rule's creation date is expected to still read organic.
  • If the rule is correct, matches the right link, and the fan converted after it existed, and attribution is still missing — that's Club's resolution step, not this rule table; see The click is in our numbers but Club shows nothing.

What's next

Domain health is green but the live page is wrong — another "the setting is right, the visible result isn't" case, on the content side instead of attribution.

On this page