ThinkingAI Logo
Data AnalysisAnomaly Diagnosis

AE Analysis Model Selection

Not sure which AE analysis model to use? Intelligently recognize analysis intent, recommend the best-fit model based on real tracking metadata, and output a precise event and property configuration.

IndustriesAll industries
No credit card. Work email only.
Agent · Skills Live
skill · loadedindustry+100
Run this Skill on my data

Segment breakdown

by group
SegmentShareARPPU
High62%$248
Mid31%$96
Low12%$18
Analysis readyevidence attached

AE Analysis Model Recommendation and Configuration is a data-engineering capability in ThinkingAI's industry Skill library. When an analyst is unsure which model to use, it intelligently recognizes analysis intent, recommends the best-fit analysis model based on real tracking metadata in AE, and outputs a precise event and property mapping, avoiding skewed results from a wrong model choice or misconfiguration. This is ThinkingAI's decade of industry experience, packaged into ready-to-use Skills.

Live walkthrough

Agent
te-analysis-model-selection
The team stacked up four analysis requests this week and I'm not sure which model each should use: (1) the difference in daily PvP counts between paying and non-paying users; (2) how long it takes new users to go from registration to first payment; (3) the change in core-gameplay participation after a version update; (4) the drop-off at each step of the new-user tutorial. Map each one to a model and explain why.
Parse the analytical goal of each of the 4 requests: comparison / duration / trend / conversion
Query the tracking metadata of a sample casual competitive game DEMO, verify the events and properties truly exist
pvp_battle, register, payment, guide_step are all in the tracking plan
Check grouping capability: availability of the payment-status tag
Tag "payment status" already exists, usable directly for grouping
Match models to intent: distribution / interval / event / funnel, and generate a config for each
Find a tracking gap in request (4), generate a workaround
guide_step lacks a step-identifier property; provided both an add-tracking and a SQL option

All four requests mapped to a model: one each for distribution, interval, event, and funnel, with every config validated against real tracking metadata. Request (1) I already configured and ran end to end.

1. Model mapping for the four requests

Business questionRecommended modelWhy not anotherKey config
(1) PvP-count difference, paying vs. non-payingDistribution analysisEvent analysis only shows totals and averages; comparing "distribution shape" needs distributionEvent pvp_battle, grouped by tag "payment status"
(2) Interval from registration to first paymentInterval analysisA funnel only shows conversion rate, not "how long it took"Initial event register, subsequent event payment
(3) Change in core-gameplay participation after versionEvent analysisA trend-comparison scenario, no distribution or cohort logic involvedpvp_battle triggering users, grouped by #app_version
(4) Drop-off at each tutorial stepFunnel analysisRetention looks at return visits, not step sequencesguide_step ordered by step, 1-day window
← Scroll to see more

2. Request (1) already produced a result

Distribution analysis result: paying users have a median of 5 daily pvp_battle counts, non-paying users 2; by shape, 61.3% of paying users fall in the 4–8 range, while 57.8% of non-paying users cluster in 0–2. Core-gameplay engagement depth is strongly correlated with payment, so the operational hypothesis of "drive PvP participation → drive payment" has data support.

3. Request (4) has a tracking gap

The guide_step event has no step-identifier property, so a funnel can't strictly order by step. Two options: add a step_id property (recommended, solves it once and for all); or temporarily approximate step order via SQL sorted by #event_time, which produces numbers, but the step order will be distorted after any tutorial-flow redesign, so it's only fit as a stopgap.

Recommendation
Model-selection shorthand: use event for total-volume trends, distribution for shape differences, interval for elapsed time, funnel for step conversion, and retention for return-visit stickiness. All four configs have their event and property names validated against metadata and are ready to run.

On your data

That was a simulated run

Leave your work email and we will run a live walkthrough on your real business data.

No credit card. Work email only.

The problem

AE offers 10+ analysis models, yet more than 60% of analysts spend over 30 minutes agonizing over model choice for a specific need. Worse is the hidden bias from a wrong choice: the same business question yields completely different definitions under different models, and in about 40% of wrong-model cases the analysis conclusion is off by more than 30%. Configuration is just as subtle: the right model with the wrong event or property still distorts the result.

What it does

Intelligent intent recognition: automatically determine the best-fit model type from the user's described scenario, instead of making the user pick manually among 10+ models
Configuration from real metadata: query AE tracking metadata to ensure event and property names really exist, eliminating guessed or fabricated field names
Fallback when fields are missing: when a required field does not exist, automatically recommend a SQL alternative or a tracking-completion suggestion, so the analysis need is never blocked

When to use it

01

The analysis need is clear but you don't know which AE model to use

02

You know which model to use but aren't sure how to configure events and properties

03

Multiple models could meet the need and you need to compare and choose the best

04

Existing tracking fields don't meet the analysis need and you need completion suggestions

05

Guiding a new analyst to get up to speed on AE model selection and configuration

In the field

Case
A game operations team · behavior difference between paying and non-paying users
Operations originally used event analysis to count each group's core behaviors but could not compare distribution differences. The Skill recognized the intent as "compare behavioral characteristic differences across groups," recommended distribution analysis, and queried metadata to confirm the payment-status tag already existed. After configuration, it found paying users had a median daily PvP participation of 5 versus 2 for non-paying users, providing a basis for boosting core-gameplay participation to drive payment.

FAQ

Does this Skill recommend the model or configure it?

Both: it recommends the best-fit model first, then outputs the configuration (event names, property names, grouping dimensions, filters) based on real metadata.

What if a tracking field is missing?

The Skill clearly flags the missing field and provides a SQL-query alternative or a tracking-completion suggestion.

How do you choose when several models apply?

The Skill lists each model's strengths and limitations and recommends the best option based on the analysis-goal priority.

Related Skills

Equip your Agent with AE Analysis Model Selection

Book a demo and see how it works in your own business.

ThinkingAI Big Logo