1. Operational Analytics
  2. Data model
Reference

The tables behind Operational Analytics

Operational Analytics ships with 17 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.

Tables
17
Features
6, plus shared settings
Change it
Add fields and tables in Proto

How the model is organised

Configuration

Organizations, People and process definitions identify scope and ownership.

Operations

Process snapshots link process execution facts and metric observations to the measured period; metric observations link to source snapshots.

Execution and provenance

Operation runs and operation steps keep the work trace; metric definitions, metric results and source mappings keep metric meaning.

Review and evidence

Review decisions, evidence documents, state history and follow up actions preserve decisions and response.

Every table, by feature

Process measurement

5 tablesAbout this feature
  • Process snapshots

    Measured web properties with lifecycle status and observed outcome fields.

    Linked to Organizations, People, Process definitions
  • Process definitions

    Configured measurement and experiment definitions with effective dating.

    Linked to Organizations
  • Organizations

    Customer organizations whose web properties are measured.

  • People

    Analysts, owners and reviewers belonging to an organization.

    Linked to Organizations
  • State history

    Immutable lifecycle transition history for each source.

    Linked to Process snapshots, People

Execution facts

5 tablesAbout this feature
  • Process execution facts

    Consented observation-level session and conversion event facts.

    Linked to Process snapshots
  • Process snapshots

    Measured web properties with lifecycle status and observed outcome fields.

    Linked to Organizations, People, Process definitions
  • Operation runs

    Workflow execution runs with frozen revision, input hash and result identity.

    Linked to Process snapshots
  • Operation steps

    Numbered steps of an operation run with input/output and receipt state.

    Linked to Operation runs
  • Source snapshots

    Sourced snapshot captures with coverage window and freshness status.

Bottleneck analysis

5 tablesAbout this feature
  • Process snapshots

    Measured web properties with lifecycle status and observed outcome fields.

    Linked to Organizations, People, Process definitions
  • Process execution facts

    Consented observation-level session and conversion event facts.

    Linked to Process snapshots
  • Operation runs

    Workflow execution runs with frozen revision, input hash and result identity.

    Linked to Process snapshots
  • Operation steps

    Numbered steps of an operation run with input/output and receipt state.

    Linked to Operation runs
  • Review decisions

    Independent reviewer decisions recorded against an exact source revision.

    Linked to Process snapshots, People

Metrics and results

6 tablesAbout this feature
  • Metric definitions

    Approved metric definitions with grain, expressions and aggregation method.

    Linked to Process definitions, People
  • Metric observations

    Observation-level metric readings tied to a snapshot and source.

    Linked to Process snapshots, Source snapshots
  • Metric results

    Calculated metric results persisted once per approved definition and window.

    Linked to Process snapshots, Metric definitions, Operation runs
  • Source mappings

    Reviewed field mappings between source and target definitions.

    Linked to Process definitions
  • Source snapshots

    Sourced snapshot captures with coverage window and freshness status.

  • Operation runs

    Workflow execution runs with frozen revision, input hash and result identity.

    Linked to Process snapshots

Review and evidence

5 tablesAbout this feature
  • Review decisions

    Independent reviewer decisions recorded against an exact source revision.

    Linked to Process snapshots, People
  • Evidence documents

    Supporting source evidence documents and verification state.

    Linked to Process snapshots, People
  • State history

    Immutable lifecycle transition history for each source.

    Linked to Process snapshots, People
  • Process snapshots

    Measured web properties with lifecycle status and observed outcome fields.

    Linked to Organizations, People, Process definitions
  • People

    Analysts, owners and reviewers belonging to an organization.

    Linked to Organizations

Follow-up work

4 tablesAbout this feature
  • Follow up actions

    Assigned corrective and follow-up actions with due dates.

    Linked to Process snapshots, People
  • Process snapshots

    Measured web properties with lifecycle status and observed outcome fields.

    Linked to Organizations, People, Process definitions
  • Evidence documents

    Supporting source evidence documents and verification state.

    Linked to Process snapshots, People
  • People

    Analysts, owners and reviewers belonging to an organization.

    Linked to Organizations

Shared and settings

1 table
  • Users

    Users

    Linked to Users

Keys and references

Process snapshots is the source for execution facts, review decisions, operation runs, evidence and actions. Its Revision is carried into a review decision and operation run. Source snapshots captures the external source coverage and freshness. A metric results row ties a metric definition to a source and run. These references let the team inspect a result without losing its origin.

Migration order

  1. Create Organizations and People, then load process definitions.
  2. Add metric definitions and source mappings for the chosen measurement period.
  3. Load process snapshots with owners and definitions.
  4. Import source snapshots and process execution facts, checking source references and consent basis.
  5. Add observations, results, decisions, evidence and follow-up actions after their parent records exist.

Set up Operational Analytics your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started