Once events exist, Asemic stops asking questions and starts making offers. Suggestion cards on the Data Model page propose metric packs: coherent bundles of properties and metrics like daily activity or retention, each applied with one click. The point is to get a studio-grade model without writing definitions by hand, while keeping every addition reviewable before it goes live.

How the cards behave

“Add to draft” applies a pack: its properties and metrics land in your working draft. Nothing is live until you publish.
A pack appears only when its prerequisites exist (revenue packs need an event with the Payment role; retention needs Registration) and retires once its contents do, so the sequence paces itself: as you accept packs, new ones unlock.
Hint cards have no apply button. They point out structural gaps instead: no event tagged as registration, a payment event missing its amount column. Fix the gap on the events screen and the hint retires.
Dismissals are per-project: if a teammate dismisses a card, it stays dismissed for everyone. Restore any of them via “Dismissed suggestions”.

The packs

Packs build on one another, roughly in this order:

Daily activity: DAU
Engagement: WAU, MAU, stickiness
Cohorts: registration and activity cohorts
Retention: D1 / D7 / D30
Revenue & payers: revenue, payer counts
ARPDAU / ARPPU
LTV
Engagement depth
Lifecycle: churn, resurrection
Payer mix
Long-horizon retention

You don’t need all of them to get value; daily activity plus retention is a solid start, and packs remain available as your model grows.

When the draft looks right, the next step is publishing it.