> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fluid.app/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For new direct REST integrations, use the v2026-04 surfaces. The @fluid-app FairShare SDK continues to use its own published public-v2025-06 contract.
> Authenticate with the header Authorization: Bearer <token>; public storefront read endpoints require no auth.
> Lists use cursor pagination via the page[cursor] and page[limit] query params; follow meta.pagination.next_cursor until it is null.
> Never use /api/company/v1 or /api/v1 paths, page/per_page params, or offset pagination — they are legacy.
> The OpenAPI specs under api-reference/ are the authoritative contracts; prefer them over prose when in doubt. api-reference/storefront-v2026-04.yaml covers the v2026-04 storefront surface (/api/v202604/... paths); api-reference/auth-v0.yaml covers the unversioned auth surface (/api/... paths — authentication, MFA, social auth, and token exchange); api-reference/checkout-v2026-04.yaml covers the v2026-04 checkout surface (/api/checkout/v2026-04/... paths — carts, cart auth, discounts, items, subscriptions, orders, enrollments, and store config); api-reference/public-v2025-06.yaml covers the Public SDK surface used by the @fluid-app FairShare SDK, including its parallel cart lifecycle, browser integrations, versioned payment callbacks, unversioned public utilities, and the cart price-override operation; api-reference/payment-v2026-04.yaml covers the v2026-04 payment gateway admin surface (/api/payment/v2026-04/... paths, bearer-authenticated — gateway CRUD, gateway purchase/authorize/$0-verify, transaction list/show and capture/void/credit, and merchant payment configuration); api-reference/payments-v2026-04.yaml covers the v2026-04 cart payment surface (/api/payments/v2026-04/carts/{cart_token}/... paths, authenticated by the cart token in the path with no bearer — payment-method selection, VGS card tokenization, 3D Secure verification, and PayPal/Braintree/Klarna/Apple Pay flows); api-reference/commerce-v2026-04.yaml covers the v2026-04 commerce order-editing surface (/api/v202604/orders/{order_id}/edits paths, bearer-authenticated — post-checkout order edits that atomically insert items and add adjustments/discounts, with an optional dry-run preview); api-reference/webhooks-v0.yaml covers the unversioned webhooks surface (/api/... paths — webhook registration, delivery payloads, callback registrations, company events, and webhook/callback schemas).
> Successful responses wrap the resource payload alongside a top-level integer status and a meta object.

# Migrate to server-side attribution

> Remove retired FairShare attribution-pattern attributes and use automatic attribution or an explicit rep override.

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:

```html theme={null}
<script
  id="fluid-cdn-script"
  src="https://assets.fluid.app/scripts/fluid-sdk/latest/web-widgets/index.js"
  data-fluid-shop="scrute-farms"
  data-path-attribution-pattern="^/([^/]+)/"
  data-enable-path-attribution="true"
></script>
```

With the basic SDK configuration:

```html theme={null}
<script
  id="fluid-cdn-script"
  src="https://assets.fluid.app/scripts/fluid-sdk/latest/web-widgets/index.js"
  data-fluid-shop="scrute-farms"
></script>
```

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.

```html theme={null}
<script
  id="fluid-cdn-script"
  src="https://assets.fluid.app/scripts/fluid-sdk/latest/web-widgets/index.js"
  data-fluid-shop="scrute-farms"
  data-share-guid="a1b2c3d4-e5f6-7890-abcd-ef1234567890"
></script>
```

An override takes precedence over automatic attribution. Remove the override when you want to test URL-based attribution.

See [Attribution override](/sdk/installation#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. Test an unattributed URL and confirm that your anonymous experience still works.

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

<CardGroup cols={2}>
  <Card title="Install FairShare" icon="code" href="/sdk/installation">
    Review the current script configuration and supported overrides.
  </Card>

  <Card title="Test affiliate content" icon="user-check" href="/themes/affiliate-hydration">
    Verify attributed and anonymous theme experiences.
  </Card>
</CardGroup>