Directory / plugin

AffClix for WooCommerce

v1.0.1 · by affclix

Server-side affiliate attribution for WooCommerce. Stamps the click ID onto every order and delivers orders to AffClix over a signed webhook.

About this plugin

AffClix for WooCommerce connects your store to your AffClix account so affiliate commissions are calculated from real orders instead of browser pixels.

The plugin does three things:

  1. Captures the click. When a visitor arrives from an affiliate link, the click ID, affiliate ID and UTM parameters are stored in a first-party cookie. No theme edits, no functions.php.
  2. Stamps the order. At checkout — both the classic checkout and the checkout block — the stored touch is written onto the order as order meta.
  3. Delivers the order. A native WooCommerce webhook posts the order to AffClix, signed with HMAC-SHA256. Refunds and status changes follow the same path, so clawbacks are automatic.

Because attribution is resolved from the order rather than from a pixel firing on the thank-you page, it survives ad blockers, Safari ITP, and customers who close the tab before the confirmation page renders.

Features

  • Works with the classic checkout and the checkout block
  • Compatible with High-Performance Order Storage (HPOS)
  • First-click or last-click attribution, with the window set in your AffClix account
  • Refunds and cancellations reverse unpaid commission automatically
  • Orders are delivered by WooCommerce’s own webhook queue, so checkout makes no outbound request
  • Optional read-only API key so AffClix can reconcile missed orders and sync your product catalogue
  • Translation ready

What you need

An AffClix account with API access. Your account ID, API key and API secret are in the AffClix dashboard under Settings API.

External services

This plugin connects your store to AffClix, a hosted affiliate tracking service. It cannot work without it. An AffClix account is required, and nothing is sent until you enter your credentials and tick “Enable tracking”.

AffClix API (api.affclix.com)

  • When: when you save the settings screen with tracking enabled, once a day afterwards, and when you deactivate the plugin.
  • What is sent: your AffClix account ID, API key and API secret, your site name and URL, and the plugin and WooCommerce versions. If you tick “Create a read-only WooCommerce REST API key”, that key is sent once, when it is created.
  • Why: to register the store and fetch its tracking settings (attribution window, cookie name, webhook address and signing secret).

AffClix order webhook (your AffClix tracking address, returned by the API above)

  • When: each time an order is created or updated, through WooCommerce’s webhook queue.
  • What is sent: the standard WooCommerce order webhook payload — order number, status, totals, currency, line items, coupon codes, and the billing and shipping details of the order, including the customer’s name, email, phone and address — plus the affiliate identifiers captured for that order.
  • Why: to attribute the order to the affiliate who referred it, calculate commission, and detect duplicate or fraudulent conversions.

AffClix web SDK (assets.affclix.com) — optional, off by default

  • When: on storefront page loads, only if you tick “Load the AffClix web SDK”.
  • What is sent: the visitor’s browser requests a JavaScript file from AffClix, which exposes their IP address and user agent, and the script reports page views to your AffClix account.
  • Why: page-view analytics in AffClix reports. Attribution and order delivery work without it.

AffClix is provided by Pivotstring. Terms of service · Privacy policy

Cookies

The plugin sets one first-party cookie (named ps_attr unless changed in your AffClix account) on visitors who arrive from an affiliate link. It holds the affiliate identifiers from that link — click ID, affiliate ID, campaign ID, sub IDs and UTM parameters — and the time of the click. It holds no personal data and expires at the end of your attribution window. Add it to your cookie notice if your jurisdiction requires one.

If your cookie banner supports the WP Consent API, the cookie is only set once the visitor allows statistics cookies.

Plugin tags