Revenue operations · V23

Conversion Intelligence Lab

Join real affiliate clicks and transactions to the exact page, merchant and CTA that generated them. No revenue or conversion metrics are estimated.

Measurement architecture updated 2026-09-01Automatic click capture + browser-only analysis
Privacy: CSV files selected here are processed in your browser. V23 can also capture outbound affiliate-click events server-side in Cloudflare Analytics Engine. The custom event dataset is designed without cookies, account identifiers, IP fields or device fingerprints.
Checking automatic click capture…

Measurement readiness

583 affiliate links

Tracked across 180 monetized pages.

141 Awin CTAs

Now using 141 unique clickrefs for CTA-level attribution.

97 clickrefs migrated

Legacy references are preserved in the migration map for historical continuity.

11 monetized merchants

Performance can be segmented by merchant, page, zone and intent.

Load real performance data

Automatic captured clicks

If private export is configured in Cloudflare, load aggregated click events directly. The admin token is held only in this browser session and is not stored by this page.

Or continue with CSV upload below.

Trend Watch

Compare the most recent period with the immediately previous period of equal length. This watches click direction only; it does not infer revenue or statistical significance.

Uses the same private export token entered above.

No trend snapshot loaded. Trend Watch starts only after real click events exist.
CTA / pagePreviousCurrentΔ clicksΔ %Signal

History guardrail: V23 suppresses directional alerts until two complete comparison periods exist. After that, the default alert guardrail is previous period ≥10 clicks, absolute change ≥5 clicks and relative change ≥40%. “New volume” requires at least 10 current clicks with zero in the previous period.

Use the two templates below. Click data should come from your analytics event export; transactions can come from Awin's Publisher Transaction Report. The join key for Awin is click_ref / clickref.

No performance data loaded. The table below is currently ranked only by opportunity score, not by revenue.

Scale / Hold / Fix / Stop engine

This V23 layer joins the current click period from Trend Watch with real Awin transactions by unique clickref. It uses approved commission only for realized EPC. Pending commission is never counted as earned revenue.

Decision guardrail: classifications remain Hold until Trend Watch has two complete periods and you confirm that the Awin export covers the same current period. Awin transaction dates are filtered to the current window when present.
Decision engine waiting. Load Trend Watch and an Awin transaction export first.
0

Scale

0

Hold

0

Fix

0

Stop

CTA / pageClicksApprovedPendingApproved commissionCVREPCTrendDecision

V23 thresholds: Scale requires at least 15 current clicks + 2 approved transactions + positive approved EPC and no decline signal. Fix begins at 20 current clicks with no approved/pending transactions. Stop is deliberately strict: at least 60 current clicks, mature history, confirmed full Awin window, and zero approved/pending transactions. “Stop” means pause scaling and verify attribution/advertiser validation before removing a CTA.

Profitability ranking: pages & merchants

V23 aggregates CTA-level evidence into two decision layers. Page ranking answers where to add internal authority, traffic or CTA exposure. Merchant ranking currently answers which Awin advertiser deserves broader coverage, because realized transaction imports in V23 come from Awin. Approved commission and EPC are ranked inside each currency only; currencies are never silently combined.

Economic ranking waiting. Load Trend Watch and an Awin transaction export, then confirm the full transaction window.

Page profitability

PageRank / currencyClicksApprovedCommissionEPCInlinksTrendRecommended action

Awin merchant economics

MerchantRank / currencyClicksApprovedPendingCommissionEPCTrendRecommended action

Internal-link recommendation guardrail: a page must have at least two approved transactions, positive approved EPC, mature history and a confirmed transaction window. “Increase internal links” is reserved for proven pages below the current monetized-site median of 17 internal inlinks. V23 generates recommendations only; it does not rewrite site links automatically.

V23 Optimization Queue

Turn economic recommendations into controlled, reversible tests. V23 defines the hypothesis, one change dimension, primary metric, minimum evidence threshold, review window and guardrail. It never edits production pages automatically.

Optimization Queue waiting. Load mature Trend Watch history and real Awin transactions, then confirm the full transaction window.
Experiment / pageStatusTypeHypothesisOne controlled changeMetricsMin new clicksReviewGuardrail

Experiment discipline: do not change traffic source, CTA wording, placement and merchant offer simultaneously. Winners require downstream transaction evidence; extra clicks alone are not a conversion win. “Control / protect” rows are intentionally left unchanged.

V23 Experiment Lifecycle

Freeze the pre-change economics before touching production, then compare the aligned post-change window. Baselines are immutable in the ledger; evaluations are appended as evidence. Outcomes are Keep / Extend / Revert, with Running until the planned review date.

No experiment baseline frozen yet. Start a READY experiment above after loading aligned real data.

Local ledger works immediately. Optional Cloudflare KV persistence uses the same private admin token and the EXPERIMENT_LEDGER binding.

Experiment / pageStarted / baselinePlanned reviewFrozen baselineOutcomeAction

Start guardrail: Trend Watch must use the same number of days as the experiment review window. Review on or within 3 days after the planned date with the same window length. If evidence is low, currency is mixed, or the period is misaligned, V23 returns Extend rather than forcing a winner.

V23 Production Change Registry & Surgical Rollback

Attach the exact production modification to each frozen experiment before deployment. V23 stores an immutable change manifest and can generate a rollback manifest that reverses only the controlled fragment. It does not restore a whole old page, so unrelated improvements made later are not automatically discarded.

No production changes registered yet. Freeze a READY experiment, download its manifest template, complete the exact before/after fragment, validate it against the extracted site, then import the manifest here.

Use assets/aivs_change_manager_v23.py to validate/apply/rollback manifests on an extracted site copy. Cloud persistence reuses the existing private EXPERIMENT_LEDGER KV binding; no new KV namespace is required.

Experiment / pageControlled changeRollback scopeProduction stateOutcomeActions

Rollback guardrail: V23 supports only exact-fragment replacement. A rollback is refused if the experiment fragment is missing, duplicated unexpectedly or has been modified by later work. In that case, resolve the conflict manually instead of overwriting newer changes.

V23 Deployment Identity & Post-Deploy Verification

Verify the exact package that is online before linking a production change to an experiment. V23 checks the stamped release fingerprint, hashes critical deployed assets, and can match the fingerprint to a recent Cloudflare Pages production deployment ID when the optional Pages Read API token is configured.

No deployment verification loaded. Deploy a stamped V23 package, enter the private token above, then verify.

Package verification works from the deployed fingerprint + probe hashes. Exact Cloudflare deployment-ID matching additionally uses CF_PAGES_READ_TOKEN, CF_PAGES_PROJECT_NAME and the existing CF_ACCOUNT_ID.

Cloudflare Pages API: not checked yet.
ProbeStatusExpected SHA-256Online SHA-256

Experiment guardrail: “Mark deployed” now refuses unless the online release fingerprint contains that experiment's exact change-manifest hash. This prevents associating a result with the wrong package.

Page-level decision table

PageOpportunityClicksApprovedCommissionCVREPCDecision

How to read the output

DecisionMeaning
ScaleObserved approvals + positive approved EPC with enough current click volume and no decline signal. Increase exposure carefully.
HoldEvidence is incomplete, pending, low-volume or not period-aligned. Keep measuring; do not force an optimization.
FixEnough clicks exist to investigate a conversion or traffic problem, but the evidence is not strong enough to stop the CTA.
StopHigh-volume zero-result candidate after strict guardrails. Pause scaling first; verify attribution and advertiser validation lag before removal.

Files for analysis

Important: do not compare commission totals across currencies as if they were one currency. The dashboard labels mixed-currency aggregates instead of silently combining them.