Affiliatant records affiliate referrals, decides which affiliate earned each sale, calculates the commission and produces the paperwork for paying it. It holds no money at any point and takes no percentage of your sales, your affiliate commission or your payouts. The payment leaves your own bank, PayPal or Wise account.
It is priced on one meter, attributed conversions a month, so the number of affiliates you sign up and the number of clicks they send cost nothing. There is a free band for up to twenty attributed conversions a month that does not ask for a card.
Each affiliate gets a tracking link. It lands on a redirect endpoint that records the visit and sends the visitor on in a single hop, with no interstitial page in between.
The click identifier is held server side. A cookie exists as a labelled fallback and is never the record, because Safari’s Intelligent Tracking Prevention caps a cookie written by a script at seven days, and at 24 hours when the link carries certain parameters. Tracking that leans on that cookie loses sales it then has no way to report.
Visitor IP addresses are stored as a keyed hash and never in the clear, and consent is checked before an affiliate cookie is set. Tracking links may only point at hosts you have added to an allowed list, because a redirect that will forward a visitor to any address at all is an open redirect, and those get used to make a link to somebody else’s site look like a link to yours.
Each attribution is a record in its own right. It stores the model used, the window as it stood on the day, every click that lost and a reason code. Changing your window next month leaves last month’s decisions exactly as they were.
Coupon codes have explicit rules rather than an accident. You choose what happens when a shopper arrives through one affiliate’s link and then types a different affiliate’s code: the code wins, the click wins, or the code wins only where there is no click on file. One affiliate is credited in every case, and the affiliate who was not credited can be shown the reason.
When an affiliate is paid, an invoice has to exist. Affiliatant raises it as a self-billed invoice, the arrangement set out in HMRC’s VAT Notice 700/62, under which the merchant issues the invoice on the affiliate’s behalf by agreement with them.
It then hands over a file listing who to pay and how much, and you make the payment. Because Affiliatant never holds the money there is no float, no payout balance to top up, and nothing of yours sitting with a third party waiting to be released.
Every integration is free, unencoded and carries no licence check, and every one of them is available on every band including the free one. An API key is the only thing connecting a shop to an account.
The shop plugins report an order twice, once from the order hook and once from the receipt page, reconciled at the other end on a shared event identifier. A hook alone misses the shopper who closes the tab, and a receipt pixel alone misses the order a gateway completes by callback later. Reporting is idempotent on the programme, the order reference and the event kind, so a gateway that calls back twice still produces one conversion. If the service is unreachable the plugin queues the event on your own server and retries, and checkout completes either way.
An attributed conversion is an order credited to one of your affiliates, counted once, in the month it happened. Clicks, visits, affiliates and team members are not counted. The free band covers twenty a month with every feature included. Paid bands start at £15.00 a month and rise by volume, and there is no setup fee, no minimum term and no notice period. Stop at any time and the account returns to the free band.
Affiliatant has the full detail, including a walk through a single sale from click to payment and the pricing bands.
We are a hosting company before we are a software publisher. Affiliatant itself is a service we run, so there is nothing for you to install, but the shop reporting into it has to live somewhere. Ask us what that costs.