Solutions
Attract new customers to your brand
Leverage our affiliate network to reach new customers for your products and services. Search for relevant affiliates and partners with engaged audiences who are in-market and ready to buy. Our global network enables you to promote your brands to millions of customers.
Plans & Service
Plans & Service
Discover our range of Platform Plans & Service Plans to unlock the technology & service behind our premium partnership marketing campaigns. Explore to grow your sales and improve your performance.
Partners
Partner Types
Partners
Discover why Optimise is the affiliate network & partnerships platform of choice for so many Partners. Explore the Advertiser Directory to create new relationships, grow your network and leverage our extensive range of partner tools.
Advertisers
Advertisers
Reach across our extensive network of Marketplaces and learn why global advertisers work with our network of quality publishers. Explore our Partner Platform technology & Service Plans backed by our team of local experts.
How to Reduce Attribution Disputes Between Advertisers and Publishers
How to Reduce Attribution Disputes Between Advertisers and Publishers
Attribution disputes are usually process failures, not partner failures
Attribution disputes can drain time, delay payments and weaken otherwise valuable advertiser–publisher relationships. They normally surface as a simple question: why does an advertiser’s reporting not match the publisher’s figures? In practice, the cause is often a combination of different tracking rules, incomplete data, attribution windows or a change that was not clearly communicated.
The objective is not to make every system show an identical number. It is to agree which data source and rules govern commercial decisions, then make exceptions fast to investigate and evidence.
Agree the source of truth before launch
Every partnership should identify one reporting environment as the source of truth for validation and payment. This is commonly the affiliate platform, because it records the click, transaction status and approval decision in one auditable workflow. Where an advertiser’s backend or CRM is the contractual source, state that explicitly and define how the publisher can validate outcomes.
The agreement should cover:
- the report used for validation and payment;
- the timezone and reporting cut-off;
- the currency, exchange-rate method and treatment of VAT;
- transaction statuses included in provisional and approved revenue; and
- the process and timescale for corrections.
Avoid wording such as “standard reporting applies”. It invites different interpretations. Name the report, the columns that matter and the scheduled approval date. A platform-led workflow, such as one managed through Optimise Media, gives all parties a consistent audit trail and reduces reliance on screenshots or manually exported spreadsheets.
Document the attribution rules in plain language
Technical configurations must be translated into operational rules that account managers, finance teams and publishers can apply consistently. A concise attribution specification should be available to every active partner.
At minimum, record the attribution model, cookie duration, click-through and view-through rules, deduplication logic, eligible products or services, excluded customer types and any channel priority. For example, “last eligible affiliate click within 30 days” is clearer than “last-click attribution”, especially when paid search, voucher codes, app traffic or direct response campaigns may also claim credit.
The specification should also say what happens when multiple identifiers exist. If an affiliate click ID, a voucher code and an email promotion all appear on the same order, the rule for resolving that situation must be defined before it becomes a disputed transaction.
Use robust, testable tracking
Reliable attribution depends on a complete data path: the publisher click, the redirect, the advertiser’s landing page, the conversion event and the transaction feed or server-side confirmation. A gap at any point can create an apparent discrepancy.
Before a campaign goes live, test representative journeys across supported devices, browsers and checkout paths. Include scenarios such as a new customer purchase, returning customer purchase, use of a promotional code, app-to-web journeys, deferred payment methods and cancellations. Record the expected tracking result and retain the test order references.
Server-side conversion tracking or a properly implemented transaction feed can improve resilience where browser restrictions affect cookies. It is not automatically more accurate: identifiers still need to be passed correctly and the feed must contain the correct order value, status and timestamp. Monitor missing IDs, duplicate order references and late-arriving transactions as operational exceptions.
Standardise data definitions
Many disputes are caused by two correct reports measuring different things. An advertiser may report gross order value while a publisher expects net commissionable revenue. One system may include shipping or tax, while another excludes them. Refunds, partial cancellations, discount codes, subscriptions and recurring revenue can all alter the apparent result.
Create a shared data dictionary for the programme. It should define:
- commissionable sale value;
- eligibility rules for new and existing customers;
- treatment of delivery, tax, discounts and gift cards;
- cancellation, return and chargeback rules;
- transaction approval and rejection reasons; and
- how subscriptions, instalments and repeat purchases are attributed.
Where a rule differs by publisher type or campaign, make that difference visible in the programme terms and partner-level setup. Hidden exceptions are difficult to defend and even harder to reconcile retrospectively.
Make deduplication visible and auditable
Deduplication is a legitimate control, but it is one of the most common sources of mistrust when it is opaque. If an order is credited to another channel, the publisher should be able to see a clear rejection or adjustment reason rather than a generic “declined” status.
Use a controlled list of rejection reasons, such as “returned order”, “internal voucher code”, “paid search policy breach” or “another channel received priority under the agreed rule”. Provide the order reference, event date and relevant attribution evidence where appropriate. This lets the publisher distinguish genuine tracking loss from a valid commercial decision.
Review deduplication rates by publisher, campaign and device type. A sudden change can indicate a configuration issue, a new marketing channel or an unintended impact from a checkout update. Early detection is far cheaper than resolving a backlog at month end.
Set a regular reconciliation routine
Reconciliation should be a routine control, not a response to a complaint. Set a predictable cadence based on programme volume: weekly for high-volume campaigns, monthly for most programmes and ad hoc only for clearly defined investigations.
The routine should compare tracked clicks, conversions, revenue, approval rate, rejection reasons and any material variance against the advertiser’s reference data. Focus investigation on unusual movement, such as a sharp conversion-rate drop, increased missing click IDs or rejection patterns limited to one publisher.
Keep a short reconciliation log containing the date, data period, variance identified, owner, evidence reviewed, decision and corrective action. This creates continuity when teams change and prevents the same issue from being reopened repeatedly.
Define an escalation path with evidence requirements
Partners need a fair route to challenge a result, but an unstructured mailbox process creates delay. Publish an escalation procedure that states who may raise a query, the evidence required, the response target and the final decision-maker.
For individual-order disputes, request the order reference, click ID where available, transaction date, claimed value and a concise explanation of the variance. For broader tracking concerns, request a date range, affected URLs or campaigns, expected versus actual volumes and examples. This makes investigations repeatable and protects customer data by keeping requests limited to what is necessary.
Set a reasonable limitation period. Investigating historic claims after data-retention periods have passed rarely produces a reliable outcome. When the evidence is inconclusive, apply the pre-agreed default rule consistently rather than negotiating case by case.
Treat programme changes as controlled changes
Changes to checkout, domains, consent tooling, product feeds, voucher handling or channel rules can all affect attribution. They should be treated as controlled changes with an owner, test plan, implementation date and post-release monitoring.
Notify affected publishers in advance when a material change may alter tracking or eligibility. Include the effective date, expected impact, testing status and contact route. After release, monitor key tracking indicators against a baseline and resolve anomalies before approving the next payment cycle.
Build trust through consistent governance
The strongest programmes do not eliminate every discrepancy; they make discrepancies explainable. Clear rules, reliable tracking, shared definitions and an evidence-led reconciliation process protect both advertisers and publishers. They also allow account teams to focus on growth rather than repeated debate over the same transactions.
For advertisers and publishers working through Optimise Media, embedding these controls into programme setup and ongoing management creates a clearer basis for attribution, validation and payment. The result is a partnership that is easier to audit, faster to resolve and more resilient as channels and technology evolve.