Measure the message, not the page it sat on.
A page is a container. What a visitor actually read was a headline, a claim or a call to action — which may appear on a dozen pages and be rewritten next week. Your content platform gives each of those a stable identifier that survives both, and Reveliqo measures it.
In short: Your content platform gives every page, section, headline, CTA, product claim, campaign message and content variant a stable identifier, so exposure, conversion and revenue are reported per asset instead of per URL.
What it is
The content platform structures what a company publishes into a graph: pages, sections, headlines, CTAs, claims and variants, each an addressable asset with a version history, wherever it happens to be rendered.
What this lets you ask
- “Which headline is associated with the most revenue per thousand exposures?”
- “Did the rewritten pricing CTA move conversion, or did the traffic mix move?”
- “Which product claim holds up on our best pages and does nothing on the rest?”
What Reveliqo receives
- Content-asset identifiers for page, section, headline, CTA, product claim, campaign message and content variant.
- Exposure events from Smart Beacon: which assets a visit was actually shown, not which assets the template contains.
- Asset version and variant, so a rewrite starts a new measurement instead of quietly contaminating the old one.
- The asset's place in the content graph, so one claim can be reported across every page it appears on.
How it is connected
- Publish with content-asset IDs in the rendered markup. A data attribute on the element is enough.
- Smart Beacon reads those attributes and records exposure when the asset enters the viewport, not when the page loads.
- Authorise the content platform's workspace so Reveliqo can resolve an ID to its text, type and version for display.
- Choose which asset types are measured. Headlines, CTAs and claims usually justify it; every paragraph on the site does not.
How you verify it
- Inspect a headline in the browser, note its asset ID, then find that ID in the content report with its exposure count.
- Change a headline in your content platform and confirm the new version is measured separately from the same day onward.
- Cross-check exposures against pageviews for a page carrying the asset. Exposures should be lower, because not everyone scrolls.
Limits worth knowing
- Exposure needs Smart Beacon. Edge collection sees the page request but cannot know which section a visitor reached.
- Assets without IDs are invisible to this report. Coverage is a publishing decision, and partial coverage produces partial rankings.
- An asset on a high-intent page usually looks stronger than the same asset elsewhere. Compare within a context before concluding the words did the work.
Other integrations
Connect the rest of the stack
Finance system
Customers, invoices, payments and subscriptions — revenue that arrived, not orders that were placed.
Accounting system
Cost, margin and recognised revenue — so a channel is judged on profit, not turnover.
Consent platform
Consent state decides the collection mode. One policy engine, never two.
Connect a site today. Read tomorrow's brief instead of building it.
Connect a site and the first brief arrives with the day's changes already explained — traffic separated from bots, conversions attached to revenue, and the evidence behind every sentence one click away.
Real people separated from bots Every answer shows its evidence Reveliqo runs on Reveliqo