Template

React Native event taxonomy for Growth Engineer runs

The Growth Engineer is only as useful as the product events it can inspect. This template gives React Native and Expo teams a starting taxonomy for activation, onboarding, paywalls, purchases, retention, and feedback loops.

Get Started for Free See Growth Engineer

Templates

React Native event taxonomy

Expo analytics events

mobile analytics event names

Growth Engineer event tracking

Best for

Expo apps adding analytics for the first time
React Native teams cleaning up inconsistent event names
Mobile products preparing Growth Engineer workflows

Workflow

Step 01
Define screen and step events for onboarding and activation.
Step 02
Track paywall view, paywall skip, purchase attempt, purchase success, and subscription context.
Step 03
Track the core value action and retention-relevant feature usage.
Step 04
Validate events in debug mode before relying on release data for Growth Engineer recommendations.

Why it matters

Evidence that agents can cite.

AnalyticsCLI SDK docs include onboarding, paywall, purchase, and React Native setup concepts.

Release/debug separation is built into the analysis workflow.

Explicit event tracking avoids hidden capture and keeps the taxonomy understandable.

Questions founders ask

How many events should a small app start with?

Start with 10 to 20 carefully named events that cover activation, value, monetization, and retention. Add detail only when it will change a decision.

Should event names mirror UI screens?

Use screen names when they represent meaningful journey steps, but prefer product language when the same action can happen in multiple UI locations.

Why does the Growth Engineer need event taxonomy discipline?

Clear event names make it easier for the agent to connect evidence to the product behavior and code surfaces that need attention.