Use cases

Example workflows, not customer stories.

No client names, logos, campaign results or testimonials are published. Each workflow below describes a role, the question it answers, and what it requires from you.

Talk to the team

Example workflow

Marketing leadership reporting

Who it is for: A marketing lead reporting to a board, owner or finance function.
Business question: What did marketing activity produce this period, measured against which definitions?
Required inputs: Channel exports or read access, plus a signed-off metric list.
Metricora's role: Metricora assembles the agreed metrics into one reviewed reporting view for the period.
Expected output: A monthly reporting pack with each figure labelled by source and period.
Limitation: Coverage is limited to the sources you supply. Figures outside those sources are excluded and marked as such.

Example workflow

Campaign review preparation

Who it is for: An in-house team preparing for a campaign review meeting.
Business question: Which activity is worth discussing, and what is the supporting evidence?
Required inputs: Campaign-level exports covering the period under review.
Metricora's role: Metricora structures the period into a comparable review view with a short written summary.
Expected output: A review view plus notes on what changed and what is unclear.
Limitation: Metricora does not create, edit, publish or control campaigns.

Example workflow

Agency and client reporting coordination

Who it is for: An agency reporting to a client, or a client reviewing agency reporting.
Business question: Are both sides reading the same numbers with the same definitions?
Required inputs: Agreed metric definitions from both parties and the underlying exports.
Metricora's role: Metricora maintains one shared definition set and one shared reporting view.
Expected output: A reporting view both parties reference in the same meeting.
Limitation: Requires both parties to agree definitions in writing before configuration.

Example workflow

Multi-channel activity visibility

Who it is for: Teams running activity across more than one platform.
Business question: What is running where, over which period, at what recorded cost?
Required inputs: Exports from each platform in scope, supplied per period.
Metricora's role: Metricora places the activity side by side with the source of each figure stated.
Expected output: A period view covering the channels you supplied data for.
Limitation: Platforms measure differently. Differences are documented, not silently reconciled.

Example workflow

Data-quality review

Who it is for: Teams that cannot reconcile figures between platforms or reports.
Business question: Where do the numbers diverge, and why?
Required inputs: The conflicting exports and the disputed period.
Metricora's role: Metricora documents the difference, its likely cause and the safer definition.
Expected output: A written data-quality note and a corrected definition where one exists.
Limitation: Some platform discrepancies cannot be resolved and are reported as unresolved.

Example workflow

Monthly performance reporting

Who it is for: Organisations that need a repeatable, defensible monthly pack.
Business question: Can we produce the same report, the same way, every month?
Required inputs: A fixed source list and a fixed metric definition set.
Metricora's role: Metricora holds the definitions stable so periods stay comparable.
Expected output: A repeatable monthly pack with a change log when definitions change.
Limitation: Comparability breaks if source availability or platform definitions change; this is flagged in the pack.