Plainly.
Buyer reporting

Show whether the pilot changed anything useful.

Import a validated customer aggregate, combine it with one agreed outcome and export a report whose provenance is impossible to confuse with demonstration data.

Demonstration only · not customer evidenceThese fictional figures make the report testable. Every export is explicitly marked demonstration.
Strict schema · 100 KB maximum · unknown fields are rejected
Privacy-safe funnel
Optional understanding check

Aggregate categories only. No financial values or free-text responses.

Primary outcomePilot target met

Improved understanding moved from 58% to 76%, a positive change of 18.0%.

Loaded312 · 100.0%
Interacted241 · 77.2%
Completed186 · 59.6%
Next step74 · 23.7%
Eligible audience
500
Interaction rate
77.2%
Completion rate
59.6%
Next-step rate
23.7%
Optional understanding check

69.1% answered yes

162 responses from 87.1% of completed decisions.

Yes
112
Partly
38
Not yet
12

JSON reports retain the evidence status shown above. This workflow accepts aggregate journey counts only; calculator values, personal identifiers, free text and raw event records are outside the measurement contract.
Existing analytics

Customer-owned analytics in, aggregate evidence out.

Add one optional attribute to the normal embed. Plainly pushes only the approved event name, client identifier, campaign identifier, configuration version and contract version. Google Tag Manager or the buyer's analytics team controls collection, consent and retention. The reporting workbench accepts only a strict aggregate JSON bundle: raw events, user records and unknown fields are rejected.

<script
  src="https://plainlyfinance.co.uk/embed/plainly-embed.js"
  data-plainly-calculator
  data-calculator="pension-change"
  data-client="customer-id"
  data-campaign="approved-pension-change"
  data-analytics="dataLayer">
</script>