By Marcus Doyle, affiliate-tracking support lead with nine years of experience testing publisher links, conversion reporting, and transaction queries
Last reviewed: July 24, 2026
A missing Awin commission should be checked in the Transactions report before it is reported as a tracking failure. Search the relevant date range and advertiser, then distinguish a transaction that is absent from one that is already Pending, Approved, or Declined. This independent guide is not affiliated with Awin.
Do that first. Skip rebuilding every tracking link until the report confirms that no transaction exists.
What Awin tracking does
Awin affiliate links contain tracking information that identifies the publisher responsible for a referral. When a visitor follows the link and completes the advertiser’s agreed action, Awin can attribute the transaction and record the related commission.
That process depends on several stages working together:
- The publisher uses a valid Awin link.
- Awin records the referral.
- The advertiser’s tracking remains active through checkout.
- The completed action meets the program’s commission rules.
- The transaction is reported to Awin.
- The advertiser later validates or declines it.
A failure at any stage can produce the same visible symptom: no expected commission.
Start with the Transactions report
Awin’s current help documentation describes the Transactions report as the main view for transactions of every status. It can be filtered by timeframe, partner, transaction type, and statuses including Pending, Declined, and Approved.
For a publisher, the equivalent transaction-report guidance also supports reviewing payment status, advertiser, order references, and transaction types such as sales or leads.
Use a wider date range than the expected purchase day. Reporting can depend on the advertiser’s implementation and transaction timestamp.
Check for:
- A transaction under another status
- A different commission amount
- A corrected or declined record
- An unfamiliar order reference
- A transaction attributed to another date
- A lead instead of a sale
A missing commission is not always a missing transaction. Sometimes the transaction is present but filtered out.
Clicks and transactions are separate records
A recorded click does not prove that a later purchase will be attributed to the publisher.
Awin describes affiliate tracking as monitoring the customer journey from the publisher click through the completed action. The conversion must still be connected with the correct referral under the advertiser’s tracking and attribution setup.
This creates three common scenarios:
| What appears | What it suggests |
|---|---|
| Click and transaction both appear | Tracking reached conversion reporting |
| Click appears, transaction does not | Checkout tracking, attribution, consent, or reporting may have failed |
| Neither appears | The link, redirect, reporting filter, or test method may be wrong |
| Transaction appears as Declined | Tracking worked, but validation failed |
Priority one is classification. Skip arguing that tracking failed when the sale is already listed as Declined.
Use ClickRefs before a campaign goes live
Awin calls its custom tracking references ClickRefs, also known as SubIDs. They can be added to affiliate links to identify the page, placement, campaign, or traffic source that generated activity.
For example, separate references can distinguish:
- Homepage banner
- Product review
- Email placement
- Social campaign
- Comparison page
- Different websites under one publisher account
Awin’s Click References Report then aggregates performance using those values.
This matters when a sale is missing. Without a ClickRef, the publisher may know that someone purchased but cannot connect the expected transaction with one precise placement or click path.
Use readable internal labels. Do not place private customer information inside a ClickRef.
Check whether the transaction was declined
A declined transaction means the conversion was recorded but the advertiser rejected the commission.
Awin lists several documented reasons a transaction can be rejected, including:
- Failed payment or credit check
- Customer cancellation
- Returned goods
- Another condition under the advertiser’s program rules
The detailed transaction record or export may provide the applicable decline reason. The advertiser’s validation decision is different from a technical tracking failure.
That difference changes the next action.
A missing record may justify a transaction query. A declined record should be reviewed against the displayed reason and the advertiser’s terms.
When to submit a transaction query
Awin supports publisher transaction queries for sales or other qualifying actions that were expected but did not appear correctly in reporting. The Publisher Transaction Report links directly to guidance for reporting a missing sale.
A useful query needs enough transaction context for the advertiser to investigate, but it should be submitted through the platform’s supported process rather than an informal public message.
Before opening one, verify:
- The advertiser program was approved when the referral occurred.
- The link belonged to the correct advertiser.
- The transaction is genuinely absent.
- The advertiser’s permitted reporting period has passed.
- The customer completed the qualifying action.
- The transaction was not cancelled, returned, or already declined.
Do not submit duplicate queries for the same order. One clear case is easier to review than several overlapping reports.
Advertiser validation can take time
Transactions remain Pending until the advertiser validates them. Awin’s official guidance says that reporting delays or prolonged validation can be raised with the advertiser or account manager.
Pending does not mean lost.
The advertiser may need to wait for a cancellation period, return window, payment confirmation, service activation, or another program-specific event before approving the commission.
Validation time varies by advertiser and region. An old forum estimate should not override the program’s current terms or the transaction status shown inside Awin.
Wait on Pending. Investigate absent.
Ad blockers can interfere with testing
Awin’s advertiser tracking-test guidance identifies browser ad blockers as one potential cause of a test transaction not appearing. It recommends testing in an incognito window or with blocking extensions disabled.
That is a controlled test step, not proof that every missing publisher sale was caused by an ad blocker.
Browser privacy tools can block scripts, redirects, or cookies. The advertiser may also use server-side or parameter-based methods that reduce dependence on one browser mechanism.
For a clean test:
- Use the designated test link.
- Open a private browser session.
- Disable extensions for that session.
- Complete one test order.
- retain the order reference.
- Check the tracking result once.
Avoid producing several test purchases in quick succession. Duplicate records can make diagnosis harder.
Consent settings affect cookie-based tracking
Awin’s current consent documentation says that when an advertiser indicates visitor consent has not been obtained, Awin does not set its landing-page cookie and does not read first-party or process third-party cookies at checkout, except for certain strictly necessary cashback and loyalty activity.
Consent handling is primarily an advertiser implementation responsibility, but it can affect publishers because a referral may not be tracked in the expected cookie-based way.
This is a documented friction competitors often reduce to “the cookie disappeared.”
The actual issue may involve:
- The consent signal sent by the advertiser
- The customer’s consent choice
- The advertiser’s tracking configuration
- The attribution method used at checkout
- A permitted exception for a particular partner type
Do not promise that every click creates a commission cookie. Tracking depends on the implemented consent and attribution framework.
Last-click attribution can change credit
Awin’s developer documentation describes its Last Click Identifier as a mechanism for determining which paid referral was the last one before checkout. When the identified referral came from an Awin publisher, the system can attribute the transaction accordingly.
That means an earlier publisher click may not receive credit when another qualifying paid channel or publisher becomes the later attributable referral under the advertiser’s setup.
The precise attribution rules can vary by advertiser, partner type, and technical configuration.
A customer saying “I used your link” is useful context, but it does not reveal every click that occurred before purchase. Another referral may have intervened.
Attribution is evidence-based, not memory-based.
App purchases require in-app tracking
Awin’s publisher guidance says that accurate attribution for conversions completed inside an advertiser’s app depends on whether the advertiser has implemented in-app tracking.
A user can click a publisher link on the web, open or switch to an app, and complete the purchase there. If that transition is not supported by the advertiser’s tracking setup, the conversion may not appear as expected.
Before promoting an app-heavy advertiser, check the available program information for mobile or in-app tracking support.
Skip assuming that desktop, mobile-web, and app journeys behave identically.
They do not.
Platform changes can break advertiser tracking
Awin’s current testing documentation identifies e-commerce platform changes as another cause of missing transactions. When an advertiser changes or updates its platform, it should confirm that the Awin integration remains active.
Awin’s 2026 plugin-upgrade guidance provides specific examples for Shopify, WooCommerce, Wix, and Shoplazza. It directs advertisers to:
Support → Integration → Tracking Installation Guide
and, when troubleshooting is needed:
Support → Integration → Tracking Diagnosis.
This is mainly an advertiser-side route. Publishers normally cannot repair another company’s checkout tracking.
If several unrelated customers report missing transactions for the same advertiser during the same period, the pattern may justify contacting the advertiser or Awin rather than altering every publisher link.
Duplicate transactions after migration
Awin’s plugin documentation warns that temporary duplicate transactions can appear when legacy ShareASale tracking and Awin tracking run at the same time during an integration migration. It says the duplicates should resolve after the old ShareASale integration is removed.
This applies to advertiser integrations, not every publisher account.
A duplicate transaction is not an extra guaranteed commission. Validation can remove the duplicate before payment.
Publishers should avoid treating a temporary double entry as final revenue until the records have completed advertiser validation.
The device columns can reveal a broken path
Awin’s updated Transactions report includes a Device column showing the devices associated with the click and the transaction.
That detail can expose cross-device behavior.
A click may occur on a phone while the purchase is completed on another device. Whether the conversion is attributed depends on the tracking methods available in the advertiser’s implementation.
The column does not guarantee that every cross-device journey is captured. It gives additional evidence for transactions that were successfully reported.
Hands-on check: compare click and conversion device values before deciding that a mobile link itself failed.
A practical missing-sale order
Use this sequence:
- Open the Transactions report.
- Expand the date range.
- Filter by advertiser and transaction status.
- Check whether the transaction is Pending, Declined, or already Approved.
- Review the order reference and transaction type.
- Compare ClickRef reporting when one was used.
- Check for known advertiser tracking or platform changes.
- Allow for documented validation time.
- Submit one transaction query when the conversion remains absent and eligible.
Skip replacing links across the entire site until one clean test shows the link or redirect is actually broken.
Frequently asked questions
Does an Awin click guarantee commission?
No.
Where do I find Awin transactions?
Use the Transactions report, which supports filters for timeframe, advertiser, status, and transaction type.
What is an Awin ClickRef?
It is a custom reference added to an affiliate link to identify a placement, site, or campaign in reporting.
Why is my sale Pending?
The advertiser has not completed validation. Pending transactions may remain under review until the program’s applicable confirmation conditions have been met.
Can an ad blocker stop Awin tracking?
It can interfere with some tracking tests or scripts. Awin recommends a private browser test with blocking extensions disabled when diagnosing advertiser tracking.
Why did Awin decline a transaction?
Documented reasons include a failed customer payment, cancellation, returned goods, or another advertiser-program condition. Review the transaction’s displayed reason.
Can purchases inside an app be tracked?
They can be when the advertiser has implemented suitable in-app tracking. Awin advises publishers to verify that support before relying on app conversions.
Should I report every missing sale immediately?
No. First confirm that the transaction is absent rather than Pending or Declined, check the advertiser’s validation timing, and make sure the order met the program conditions. When those checks pass, use Awin’s supported transaction-query process.
Awin tracking problems become easier to isolate when clicks, attribution, transaction reporting, advertiser validation, and payment are treated as separate stages. The missing record should be traced to one stage before another link or account is created.