Publish

Everything you’ve built so far (events, properties, metric packs) lives in a draft: a working copy only your project sees. Publishing turns the draft into the model that charts and dashboards actually use. The separation exists so you can experiment freely without breaking the numbers your team relies on.

Review before publishing

Select “Publish” in the header. The “Review changes before publishing” dialog compares your draft against the currently published model and shows what will be added, changed, and removed.

Read the removals carefully; they are called out prominently for a reason: publishing replaces the whole model. Anything in the published model that is not in your draft is dropped. If a metric you expect to keep shows up as removed, cancel and check whether it was deleted from the draft by accident.

What publishing creates

Confirming creates an immutable model version. Published versions don’t change; the draft remains your working copy, and the next publish creates the next version.

If you want to throw the draft away instead, “Reload from engine” discards it and resets your working copy to the published model.

After publishing

The model is defined, but charts don’t have data until it is computed for a date range. That’s the last onboarding step: Backfill.