Analytics governance

Analytics implementations, documented and tested.

Generate tracking specifications from screenshots, version them like code, and verify what is actually live on your site.

What is OmniSpec?

OmniSpec is Cresia’s analytics governance product: it generates tracking specifications — events, parameters, schemas — from journey screenshots, versions them with approvals like code, and tests the live implementation against the spec. It supports Adobe (XDM/AEP schemas) and GA4, so "which version is live?" has one answer.

Features

What OmniSpec does

From screenshots to a full specification

Upload the journey — screen by screen — and OmniSpec drafts the tracking specification: events, parameters, and schemas in your stack’s format (Adobe XDM/AEP or GA4). Analysts review a complete draft instead of assembling one for weeks.

  • ✓Events, parameters and schemas drafted from the actual journey
  • ✓Adobe XDM/AEP and GA4 formats out of the box
  • ✓Analysts start from a review, not a blank template

Versioned like code, approved like a release

Every change to the spec is a reviewed, versioned revision with a named approver. The current version is unambiguous; the history explains every change — the shared-drive-full-of-spreadsheets era ends.

  • ✓One current version, always identifiable
  • ✓Named approvals on every revision
  • ✓Full change history: what changed, who approved it, when

The live site, tested against the spec

OmniSpec exercises the live implementation and compares what actually fires against what the spec says should fire. Gaps arrive as a report you can assign — not as a quarter of quietly wrong numbers.

  • ✓Live implementation checked against the approved spec
  • ✓Gaps reported with page, event and parameter detail
  • ✓Re-run after every release, before the data goes wrong
How it works

From start to shipped

  1. 1

    Upload the journey

    Screens of the flow you need tracked — that’s the input.

  2. 2

    Review the draft spec

    Events, parameters, schemas — drafted in your stack’s format for your analysts to refine.

  3. 3

    Approve and version

    The spec becomes a versioned, approved artifact. Implementation teams build against it.

  4. 4

    Validate what’s live

    OmniSpec tests the site against the spec and reports every gap — repeatably, after every release.

Who it’s for

Built for the people who own the outcome

Analytics leads

Implementation quality they can prove, with a validation report instead of a hunch.

MarTech owners

One governed spec per journey instead of competing spreadsheets in a shared drive.

Data consumers

Dashboards they can trust, because what fires is tested against what was specified.

New to analytics governance? Start with our plain-language guide: What is a tracking specification?

OmniSpec, in practice

Which analytics stacks are supported?

Adobe (XDM/AEP schemas) and GA4 today, with the spec format designed to extend.

Who is OmniSpec for?

Analytics and marTech teams who own implementation quality — and everyone downstream who depends on the data.

What input does spec generation need?

Screenshots of the journey you need tracked. OmniSpec drafts events, parameters and schemas from them; your analysts review and refine.

How does validation work?

OmniSpec exercises the live site and compares what actually fires against the approved spec, then reports gaps with page, event and parameter detail.

Can we validate after every release?

Yes — validation is repeatable on demand, so tracking regressions surface days after a release instead of a quarter later.

Does OmniSpec fix implementations too?

It reports precisely what’s missing or wrong; your implementation team (or partner) fixes it with an exact work list instead of a vague "the numbers look off".

See OmniSpec on your own use case.

Pricing on demand — shaped to your team and volume.

Request a demo