On this page
- RNX-1020.T001 · Conversion event validation
- RNX-1020.T002 · Lead qualification linkage
- RNX-1020.T003 · Attribution uncertainty
- RNX-1020.T004 · Revenue basis
- RNX-1020.T101 · Conversion identifier deduplication
- RNX-1020.T102 · Refund and cancellation outcome reconciliation
- RNX-1020.T103 · Cross-domain acquisition continuity
- RNX-1020.T104 · Consent-related observation denominator
- RNX-1020.T105 · Attribution timezone and currency join
RNX code library · 9 controls
RNX-1020Acquisition and Revenue Measurement
Read what these checks mean, why they matter and which evidence they concern. Each ID below keeps its canonical place in the RNX hierarchy.
These are free learning summaries, not full technical tests or an industry certification. Specialized checks apply only to the relevant feature. Experimental labels are preserved from the canonical source.
RNX-1020.T001
Conversion event validation
Experimental — not an established ranking requirement
Check that a completed customer action records the intended event once.
Why it matters. Counting a click or a duplicate as a sale inflates results.
Illustration — fictional. Opening a form records a completed inquiry even when nothing was submitted.
When it applies. Inspected target: conversion event. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-1020.T002
Lead qualification linkage
Experimental — not an established ranking requirement
Distinguish useful sales leads from all incoming contacts.
Why it matters. Spam and unsuitable requests should not look like qualified demand.
Illustration — fictional. Newsletter signup counts as qualified sales lead.
When it applies. Inspected target: CRM linkage. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-1020.T003
Attribution uncertainty
Experimental — not an established ranking requirement
Label missing customer journeys and estimated credit for results.
Why it matters. An unknown source is not proof that a particular channel succeeded or failed.
Illustration — fictional. Every visit with an unknown source is assigned to AI search.
When it applies. Inspected target: attribution claim. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-1020.T004
Revenue basis
Experimental — not an established ranking requirement
Explain what a revenue number includes, including refunds.
Why it matters. Gross orders and retained income are different measures.
Illustration — fictional. Refunded order remains full net revenue.
When it applies. Inspected target: revenue series. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-1020.T101
Conversion identifier deduplication
Experimental — not an established ranking requirement
Deduplicate repeated conversion records using the appropriate identifier.
Why it matters. A retried notification should not become a second sale.
Illustration — fictional. One form replay becomes two leads.
When it applies. Inspected target: conversion replay fixture. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-1020.T102
Refund and cancellation outcome reconciliation
Experimental — not an established ranking requirement
Reflect refunds and cancellations in reported outcomes.
Why it matters. An order that was reversed is not retained revenue.
Illustration — fictional. A refunded hundred-dollar order remains recorded as a hundred dollars of retained revenue.
When it applies. Inspected target: order adjustment. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-1020.T103
Cross-domain acquisition continuity
Experimental — not an established ranking requirement
Preserve the intended acquisition trail when a customer crosses owned domains.
Why it matters. Your checkout host should not accidentally replace the original source.
Illustration — fictional. The checkout subdomain is credited as the source of a sale instead of the customer's original referral.
When it applies. Inspected target: cross-domain journey. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-1020.T104
Consent-related observation denominator
Experimental — not an established ranking requirement
State how consent affects the share of activity you can observe.
Why it matters. Untracked purchases are unknown by source, not proof of zero AI-driven purchases.
Illustration — fictional. Untracked purchases are counted as zero AI purchases.
When it applies. Inspected target: measurement coverage interval. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-1020.T105
Attribution timezone and currency join
Experimental — not an established ranking requirement
Align time zones, currencies and money units when joining reports.
Why it matters. Otherwise a sale may land on the wrong day or appear a hundred times too large.
Illustration — fictional. An order is assigned to the wrong local day, or its cents are mistaken for dollars.
When it applies. Inspected target: joined monetary row. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.