A weekly portfolio report should show each offer's observed path from acquisition to commercial state, expose missing and excluded data, and end with the operator's recorded decision rather than a traffic ranking.
Keep reach and commercial state separate
The report begins with qualified pageviews by site, source, and answer page, then shows deeper states in separate columns. A site with many visits and no form starts has a different problem from a site with few visits and several qualified inquiries. Combining those conditions into one score hides whether the offer, acquisition source, or measurement system needs attention.
Plausible supports consolidated multi-site views, goals, funnels, UTM attribution, and custom properties. Those features supply the raw dimensions, but the operator still has to define what counts as an engaged visit, a form start, a complete inquiry, a qualified problem, and an order. The report prints each definition beside the number so changes cannot silently rewrite history.
Show coverage and faults before interpretation
Every weekly row carries data-quality fields: verified routes, last successful synthetic journey, unmatched submission states, unknown acquisition share, excluded test count, duplicate count, and event-contract changes. A missing qualified-inquiry event should not be interpreted as weak demand when the intake join has failed. The operator needs the fault before the commercial interpretation.
Privacy and retention choices also belong in the record. The ICO states that first-party analytics cookies require consent and that analytics use should be explained to visitors. The report identifies which collection method and consent rule apply to the cohort, the retention window, and whether any material change affected comparability with the prior week.
End with a recorded offer decision
The final column records keep, revise, hold, or retire, along with the evidence and next observation window. A revision names the exact page, source, form, price, or qualification rule being changed so the next report can compare the relevant state. The system supplies measured inputs and a consistent template; the operator remains responsible for the commercial decision.
Where the service stops
Reality Contact, LLC implements and verifies the approved measurement system, but does not supply legal advice, choose consent on the buyer's behalf, identify visitors across unrelated contexts, contact leads, or decide which offer survives. The buyer approves event definitions, privacy and retention rules, exclusions, qualification states, and uses the first cohort report to keep, revise, hold, or retire each offer. This is analytics implementation and operational reporting, and it does not replace privacy counsel, consent review, security review, or the buyer's own commercial judgment. Reports describe recorded events and their known coverage; they do not establish why a visitor acted or whether an unobserved person had commercial intent.
Sources: Plausible multi-site and conversion feature overview; ICO analytics-cookie guidance.