Your analytics organization reaches conclusions. Propperly maintains them.
A metric definition. A decision that updated it. An open conflict that wasn't resolved yet. This is the object Propperly maintains: a governed current state with four distinct properties.
Below: an illustrative example of the workflow, followed by the resulting artifact. Everything shown uses constructed data.
How a definition gets reviewed and updated
A new analysis arrives. It challenges the current metric definition. Propperly surfaces the conflict and proposes a revision. A person reviews and approves or rejects it. By design, nothing is applied until they do.
A new analysis updates a metric definition: reviewed, not silently applied.
product reporting · approved · Q1
product reporting · approved · analyst · today
What Propperly produces: a governed current state
After review, the organization's conclusions are maintained in four states. Each change is attributed and preserved. The old definition does not disappear, it becomes superseded with its rationale intact.
Active user = logged in within rolling 30 days
metric_doc · jan 12 · v1 · product team
Move active-user window to 28 days (better reflects weekly engagement pattern)
analytics decision · may 04 · head of analytics
Three dashboards still calculating on 30-day window
dashboard audit · jun 01 · data engineering
Active user = logged in within rolling 28 days
current · approved may 04 · supersedes v1
Dashboard migration incomplete, 3 of 6 still on old window
open · assigned · target: Q3
The superseded definition is preserved. The decision behind the change is attributed. The open migration is a standing state, not a note. An agent reading from this knows the current definition, knows when to flag historical comparisons, and knows this migration is not yet resolved.
Explore whether this fits your problem
Tell us the problem you are trying to solve and we will follow up to discuss whether Propperly is the right fit.
Please do not paste dashboards, data, credentials, or sensitive definitions. A short description of the problem is all we need to start.
We use these details to review and respond to your request. Do not submit project files, credentials or sensitive information. Forms are processed through Netlify.
Privacy details
We collect only the contact and qualification details you enter here, and use them solely to review and respond to your request. Please don't submit project files, source code, API keys, credentials, secrets, or other sensitive information. Submitting this form doesn't create an account. You can request deletion atassaf.m@propperly.ai. Submissions are processed through Netlify. We measure aggregated website traffic and interaction events through Plausible; the contents of this form are not sent to analytics.
Request received.
I'll review it and be in touch if there's a useful conversation to have.