For advertisers
DirectLinking, S2S, implementation and reliable measurement.
Tracking records relevant interactions and conversions. Attribution applies the rules for assigning value. Validation then checks whether the result meets campaign conditions, for example following a return or cancellation. Reviewing these stages separately helps explain differences in reports and commissions.
Related glossary: Affiliate tracking, Transaction validation
With DirectLinking, the affiliate referral first reaches a tracking route on the advertiser’s domain. The referral can be recorded in a first-party setup before the visitor continues to the destination. This reduces reliance on third-party cookies. The conversion must also be reported through the agreed method.
Related glossary: DirectLinking, Affiliate tracking
Hosted Tracking uses a configured advertiser subdomain for tracking requests handled by TradeTracker. DirectLinking uses an advertiser-domain route for the incoming referral. Hosted Tracking requires domain configuration and verification. It can form part of a first-party measurement setup alongside a suitable conversion integration and consent settings.
Related glossary: Hosted Tracking, DirectLinking, Affiliate tracking
With S2S tracking, the advertiser’s system reports a conversion directly to TradeTracker using the stored click reference. This is useful when a back-office system confirms the conversion or a browser event does not fit the purchase flow. Reliable reference storage and correct transaction data remain essential.
Related glossary: S2S tracking, Click ID
Yes. A suitable first-party referral setup can be combined with a server-side conversion report. These components serve different stages of the measurement flow. Align click references, order references and deduplication so the same order is not processed unintentionally more than once. Test the complete combination before launch.
Related glossary: S2S tracking, Deduplication
A first-party setup aligns the domain context with the advertiser. This can reduce dependence on external domains and third-party cookies. Actual coverage also depends on browser behaviour, visitor choices and implementation. Check the whole measurement flow rather than assessing the cookie type alone.
Related glossary: First-party cookie, Browser tracking restrictions
Use the supported integration or official TradeTracker template appropriate to your platform. Google Tag Manager can manage a conversion tag, but does not configure the entire measurement setup automatically. Configure and test campaign details, events, amounts, consent settings and any first-party tracking host.
Related glossary: Tracking tag, Tracking test
Run an agreed test from the affiliate link through to the recorded transaction. Check the destination, click reference, order reference, value, currency and number of reports. Then confirm registration and the agreed handling of the test in TradeTracker. Repeat relevant checks after changes to checkout, tags or integrations.
Related glossary: Tracking test, Transaction
Identify when the discrepancy began and whether it affects all orders or only some. Compare an affected order with a correctly reported one and check recent changes to links, checkout, consent management or the integration. Collect relevant references for investigation, then change the implementation once the cause is established.
Related glossary: Tracking failure, Tracking test
Systems can use different windows, attribution models, time zones, channel rules and conversion statuses. Consent, browser restrictions and reporting time can also create differences. Compare the same orders, period, currency and status first. A dashboard discrepancy warrants investigation but does not itself establish a tracking fault.
Related glossary: Analytics, Attribution window
De-duplication applies agreed rules when the same conversion is reported more than once or claimed by multiple marketing sources. Use a consistent order reference and agree which channels, events and reporting rules are in scope before implementation. TradeTracker's Code of Conduct requires advertisers to disclose implemented network de-duplication in the campaign information.
Check the outcome with test journeys involving the relevant channels, including repeat order notifications. Real Attribution allocates commission across eligible publisher interactions within its configured model. It does not automatically settle every claim made by other affiliate networks, paid search or email systems. Document those separate rules and keep publishers informed when they change.
Related glossary: Deduplication, Real Attribution, Tracking test
Cross-device measurement links eligible interactions from different devices when the implemented solution has the necessary information and the applicable data-processing conditions are met. TradeTracker describes cross-device touchpoints and app events within Mobile Metrics. Confirm the supported journey, integration and reporting scope for your campaign before relying on those capabilities.
S2S describes communication between servers. A first-party setup describes where tracking operates. Neither automatically identifies the same visitor on a phone and a laptop. Consent choices, available identifiers, browser restrictions and the implemented connection can limit what is measurable. Real Attribution allocates eligible recorded contributions; it cannot recover every interaction that the implementation has not identified.
Related glossary: Cross-device tracking, App tracking, S2S tracking, Real Attribution
Measure a representative page and checkout journey before and after the agreed tracking implementation under comparable conditions. Review network requests and script work, and compare loading speed, responsiveness and visual stability. Check mobile devices as well as desktop. Google's Core Web Vitals provide useful measures for those aspects of the experience.
Use the supported TradeTracker integration and check for duplicate tags or unnecessary additional scripts. Assess performance and tracking accuracy together: a fast page with a missing conversion event is not a successful implementation. Discuss the appropriate first-party, Hosted Tracking or S2S setup with your technical contact. Server-side reporting can change browser work, but it does not guarantee zero performance impact.
Related glossary: Client-side tracking, S2S tracking, Tracking test
Sources: Google: Core Web Vitals, TradeTracker FAQ: testing a tracking implementation
Ask Tarun for an explanation or a practical example. For account-specific help, contact your TradeTracker team.
Already a partner? Member login
