Data Collection

Data EngineeringData Integration

AE Tracking Plan Generation

Automatically generate an AE tracking plan (event list, property design, common properties, user properties) from a product description, match an industry template, and upload it to the AE project, taking tracking-plan design from zero to one in a single conversation.

IndustriesGamesE-commerceToolsSocialContent

Agent · Skills Live

skill · loadedindustry+100

Run this Skill on my data

Tracking schema

events · properties

event · payment3 props

user_idstring

pay_amountnumber

channelstring

Analysis readyevidence attached

The AE Tracking Plan Generation Skill is a plan-design capability in ThinkingAI's industry Skill library. Starting from a natural-language description of the product scenario, it helps product and operations teams automatically match an industry template and generate a complete AE tracking plan, covering the event list, event properties, common properties, and user properties, and upload it to the AE project in one click, going from business description to an executable plan in a single step. This is ThinkingAI's decade of industry experience, packaged into ready-to-use Skills.

Live walkthrough

AgentSave as AgentExport session

ae-tracking-plan-generation

Our new SLG project 'Throne Expedition' goes into the dev schedule next week and the tracking plan is still blank. The core loop is grind stages to earn coins, pull heroes to boost power, monetization runs through IAP, and alliance features come later. Give me a tracking plan I can upload straight into the AE project, not a generic template.

Anchor the business context: IAP revenue model + the 'grind stages → earn coins → pull heroes → boost power' core loop

Confirmed four business dimensions: revenue model / core loop / currency system / feature entry points

Match an industry template

Matched the built-in SLG genre template

Detail module by module: six modules: registration & login / payment / economy / stages / alliance / events

Fill in properties and definitions: event properties, super properties, user properties, and amount units

38 events / 96 event properties / 12 super properties / 9 user properties

Naming and type self-check: snake_case, type uniqueness, and collision check against preset properties

0 conflicts

Call ae-cli to upload the plan to the AE project

Plan generated and uploaded. The full plan has six modules, 38 events, and 96 event properties, plus 12 super properties and 9 user properties. The event design is mapped from your revenue model and core loop; the SLG template is only a starting point, not a shell dropped on top.

1. Tracking plan event table (selected from the six modules)

One representative event per module; the full list of all 38 events is in the uploaded plan:

Module	Event name	Key properties (type)	Trigger timing
Registration & login	register	register_channel(string), os(string)	When the registration flow completes
Payment	payment	pay_amount(number), product_id(string), pay_channel(string)	When the payment callback confirms success
Economy	currency_change	currency_type(string), change_amount(number), change_reason(string)	When coin / gem balances change
Stages	stage_end	stage_id(string), result(string), duration(number)	When the stage results screen appears
Alliance	alliance_join	alliance_id(string), join_type(string)	When joining an alliance succeeds
Events	activity_reward	activity_id(string), reward_type(string)	When an event reward is successfully claimed

← Scroll to see more

A note on payment: amount events reported from the client are easy to lose and easy to tamper with, so the plan marks it as server-side reporting. The pay_amount type is set to number. AE locks a property's type on first report and it cannot be changed afterward, so this definition has to be nailed down at the plan stage.

2. Plan design principles

Business dimensions first: map out the revenue model, core loop, currency system, and feature entry points before mapping events. If you just list event names without working through the dimensions, the miss rate on critical events runs over 40%.

Uniform snake_case naming: all event and property names in lowercase with underscores. AE event names are case-sensitive, so Payment and payment get recorded as two separate events.

Types defined up front: amounts, durations, and counts are all number. A type locks on first report, so getting it wrong at the plan stage is the most expensive mistake.

Consolidate super properties: channel, version, and server ID go into super properties and are carried uniformly, not redefined one by one across the 38 events.

Conclusion

The plan is uploaded to the AE project and engineering can implement against it directly. Designing a comparable SLG plan by hand from scratch takes about 10 days on average; this version was generated in a single conversation, and with past cases as a reference, implementation runs about 3 days, cutting the overall cycle by 70%. As a next step, chain the 'AE Tracking Code Generation' Skill to translate the 38 events straight into SDK code for each platform.

The plan is uploaded to the AE platform and can be viewed and edited under 'Tracking Plans' in the admin console; the original xlsx has been synced to the project attachment library.

On your data

That was a simulated run

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

The problem

The tracking plan is the starting point of the analytics system, yet more than 60% of projects run into trouble at the tracking-design stage. Designing a complete tracking plan from scratch for a new project takes 1 to 2 weeks on average, and directly reusing a generic template leaves a key-business-event omission rate above 40%. A more subtle problem is missing dimension definitions: business dimensions like the revenue model, core gameplay loop, currency system, and feature entries directly shape the tracking plan's structure, but most teams only list event names without mapping out business dimensions, so the plan cannot support core analysis needs once live.

What it does

Five-stage interactive generation: anchor the business scenario, load the industry template, refine module by module, complete properties and definitions, and upload to the AE project. No skipped steps, no omissions

Built-in 12+ industry templates: SLG, MMO, card, casual, match-3, runner, tower defense, shooter, racing, short drama, tools, and other genre templates match directly

Business dimensions first: map out the revenue model, core loop, feature entries, and currency system before mapping event design, ensuring the plan can support core analysis needs

Upload to the AE project: once complete, the plan uploads directly to the AE platform, with zero gap from design to production

When to use it

A new project designing a tracking plan from scratch that needs an industry-standard template for a fast start

Existing partial tracking with key business dimensions missing that needs its events and property design completed

Standardizing the tracking definition across product lines using a unified template

Uploading a completed tracking plan to the AE project for production

Projects in different industries or genres needing a dedicated template rather than a generic plan

In the field

Case

A newly launched SLG game · generating a tracking plan from scratch

The operations team originally expected 10 days to design the tracking plan manually. With the AE Tracking Plan Generation Skill, the system anchored the IAP revenue model and the "grind levels, earn coins, pull heroes, boost power" core loop, automatically matched the SLG template, and output event and property design for six modules (registration and login, payment, economy system, alliance, levels, and events), then uploaded it to the AE project in one click. The dev team completed implementation against it within 3 days, cutting the design cycle by 70%.

FAQ

How does this differ from the AE Tracking Code Generation Skill?

Tracking Plan Generation produces the plan document, defining event names, property names, and data types; Tracking Code Generation produces executable code. The former is design, the latter is implementation, run in that order.

Can the industry template be modified?

Yes. The template is a starting point, not an endpoint. The Skill refines it module by module based on your actual business scenario, so the final plan fits your product exactly.

How is the plan uploaded to AE once designed?

In the final stage the Skill calls ae-cli to upload the plan xlsx to the AE project, after which you can view and manage the plan in the AE admin console.