Close the learning loop
See what happened after the price changed.
Connect price history and campaign periods to GA4 funnel context and sales measures while keeping every source, freshness state and limitation explicit.
Descriptive evidence with its source attached.A price decision needs feedback
Revenue without price history—and price history without demand—leave half the story missing.
Reevals brings the timelines together while preserving what each source can and cannot prove.
Funnel and pricing live apart
Teams manually align dates before they can even begin a comparison.
Sources get mixed
GA4 events and sales-feed units can be double-counted or interpreted as the same measure.
Correlation becomes a promise
A descriptive before-and-after view must not be presented as guaranteed causality.
Price and outcome on one timeline
Explore the pattern without losing the source or its limits.
Switch the period and visible series. Funnel activity, campaign windows and price history remain aligned, while the view stays explicitly descriptive.
Pricing analytics
Measure what followed the price change.
Funnel activity, demand, revenue and campaign periods share the same timeline while data origin and limitations remain explicit.
A source ledger beside every chart
Do not let different measures become one convenient number.
GA4 events, sales-feed units, revenue and price observations have different meanings. Reevals keeps origin, mapping coverage, freshness and comparison period visible.
- GA4 stays read-only
- Sales units do not silently merge with purchase events
- Unresolved products reduce visible coverage
analytics / source-ledgerComparable periods, visible reliability
Before, during and after only works when the windows mean the same thing.
Use consistent duration, product scope and source coverage. If mapping or freshness changes between periods, the limitation appears beside the comparison.
- Equal periods with an explicit campaign marker
- Affected and control product groups kept distinct
- Reliability label shown with modeled estimates
Learning for the next decision
Outcome context becomes useful when it returns to the workflow.
The aim is not another reporting dashboard. It is a better next pricing or campaign decision with the observed evidence attached.
Product funnel
Review views, add-to-cart, checkout, purchase and revenue context by product and period.
GA4Sales-feed measures
Use units and revenue from an internal source without silently merging them with analytics events.
SeparateMapping coverage
See which product and event records are aligned, unresolved or stale.
94%Campaign evaluation
Compare marked periods and affected groups with explicit data origin and limitations.
DescriptiveObserved is not proven
Correlation is never presented as causation.
Every chart identifies its source and comparison period, and reliability limitations remain visible.
- 01No double counting across sources
- 02No hidden mapping gap
- 03No guaranteed lift claim
Questions before implementation
The practical questions teams ask first.
The useful answer depends on your catalogue, sources, constraints and ownership. These are the boundaries we establish before automation.
GA4 provides read-only outcome context. How that context influences a pricing strategy depends on the explicit rules and approvals your team configures.
No. Their origin and meaning remain separate so events, units and revenue are not silently double-counted.
Yes. Reevals can mark before, during and after periods, while labeling the comparison as descriptive rather than causal proof.
Mapping coverage and unresolved records remain visible so teams can judge whether the analysis is sufficiently reliable.
Continue the decision loop
Connect the next capability when the workflow needs it.
Pricing analytics
Bring one real decision—not a perfect data set.
We will map the evidence, constraints, ownership and technical boundary required for a useful first workflow.