linvaraDATA
MOBILE MEASUREMENT / EVENT CONTEXT

A campaign ID
is only the
beginning.

Give acquisition data a place in the product journey. Map the relationship between a source, an app event and the outcome your team needs to understand.

Inspect an example ↓
01  Source context02  Event meaning03  Reporting logic
DESIGN THE MEASUREMENT BEFORE THE DASHBOARD.

The event is small.
The questions around it aren’t.

Choose a sample event to see the fields behind it and the question it could help answer.

EVENT INSPECTORINTERACTIVE EXAMPLE · NOT LIVE DATA
{
  "event": "first_open",
  "platform": "ios",
  "campaign": "sample_launch",
  "source": "example_network",
  "schema_version": 1
}

Where does the journey start?

A first-open event can be examined alongside available campaign context. Attribution depends on the agreed rules and the signals available to the implementation.

FIELD TO KEEP CONSISTENTcampaign
FICTIONAL SCHEMA / FOR EXPLANATION ONLYNO SDK CALLS · NO DATA COLLECTION

A field name is not
a complete definition.

An event contract describes what a payload means, when it should be produced and what a reader can safely assume.

Illustrative purchase event contract
FieldExampleWhat to agree
eventpurchaseThe action is completed, not merely attempted or displayed.
event_idsample_purchase_001A unique identifier for this occurrence, reused if the same event is retried.
occurred_at2026-01-15T10:30:00ZWhen the action happened, with a documented time-zone convention.
value19.90The monetary basis: gross, net or another explicitly named definition.
currencyUSDThe currency associated with the value; do not combine unlike amounts silently.
schema_version1The version of the contract that explains these fields.

Retries are not new actions. If the same purchase is sent again, an agreed event identifier can help a receiving system recognise the duplicate.

A changed meaning is a changed contract. Document when a field changes and how old and new records should be compared.

See what a small
validation check catches.

Edit the sample, or load a broken one. This browser-only exercise checks a few explicit rules without sending the payload anywhere.

Use fictional data only. Nothing leaves this page.

Different teams.
The same
underlying facts.

An MMP conversation works better when source definitions and product events are understood on both sides.

Acquisition: connect the source to the outcome.

Compare the actions that follow an install, not just the install count. Establish the attribution assumptions before comparing campaigns.

Product: make each step interpretable.

Define the moment behind an event. A clear activation definition helps teams distinguish a completed action from a screen view.

Analytics: reconcile the meaning.

Keep names, timestamps and observation windows aligned. Document differences before treating two numbers as a contradiction.

Useful data needs
an agreed definition.

There is no universal event plan. Start with the app, the data sources and the decisions the team needs to make.

Define the event vocabulary.

List the important actions, the properties that describe them and the owner of each definition.

Confirm collection boundaries.

Account for consent, platform restrictions and available source signals. Record what cannot be observed.

Validate before comparing.

Review sample payloads, required fields and reporting windows. Agree on the checks that make the numbers usable.

From an event record
to an interpretable report.

A chart is the last part of a longer chain. Keep the important assumptions visible at each step.

INPUT

Record what happened.

Keep the action, timestamp and source context together. Separate missing fields from deliberately unavailable information so the distinction is not lost downstream.

event + time + context
PREPARATION

Apply documented rules.

Handle retries, define reporting dates and review incomplete records. A processing rule should be understandable without reconstructing a series of dashboard filters.

validate + reconcile
INTERPRETATION

Describe the comparison.

Name the cohort, event and observation window. Explain exclusions and data gaps alongside the number so another team can reproduce the reading.

definition + window

Details worth resolving
before data arrives.

What happens if an event arrives late?

Decide whether reporting follows the occurrence time or receipt time, and how previously displayed periods are updated. A late event should not be interpreted as a new user action simply because processing happened later.

Can app and server events describe the same action?

Yes. Agree on the authoritative source and how duplicate reports of one action are recognised. Combining two sources without reconciliation can make activity appear larger than it is.

Should every property be collected?

No. Start with a specific purpose and collect only the fields needed for it, subject to applicable consent and platform requirements. The examples on this page do not require real customer identifiers.

Does this website include an SDK or a reporting backend?

No. The inspector and payload check are local demonstrations. SDK availability, collection endpoints, attribution rules, supported integrations and operational requirements must be confirmed separately.

Bring the event list, not just the dashboard.

A short overview of your app, source data and reporting gaps is enough to begin.

What are you connecting?

Describe the app environment and the reporting problem.

No credentials needed. Read the .