Skip to main content
FairShare now resolves attribution automatically from the current page URL. You no longer configure path or subdomain matching rules on the SDK script tag.

​
Remove retired attributes

Remove these attributes wherever you load the FairShare CDN script:
  • data-path-attribution-pattern
  • data-subdomain-attribution-pattern
  • data-enable-path-attribution
  • data-enable-subdomain-attribution
For example, replace this configuration:
With the basic SDK configuration:
You do not need a replacement pattern. FairShare refreshes attribution when the page URL changes, including navigation in a single-page application.

​
Keep an override only when you need one

Use an override when the page must credit a specific rep instead of using the attribution resolved for the current URL.
An override takes precedence over automatic attribution. The browser remembers it, so to test URL-based attribution, remove the override and clear the site’s data in your browser. See Attribution override for every supported override.

​
Verify the migration

  1. Search your templates and deployed script tags for all four retired attributes.
  2. Remove the attributes and deploy the updated script tag.
  3. Open an attributed URL and confirm that FairShare resolves the expected rep.
  4. Navigate to a second rep URL without reloading the page if your site is a single-page application.
  5. In a browser with cleared site data, open a URL that names no rep and confirm that your anonymous experience still works. A visitor a rep already credited keeps that credit on such a URL. See How credit is established and kept.
If the browser console still shows the removal warning, an old script tag is still present in the rendered page. Check cached theme output and tag-manager snippets as well as your source templates.

​
Next steps

Install FairShare

Review the current script configuration and supported overrides.

Test affiliate content

Verify attributed and anonymous theme experiences.