Browse Business Analysts Section 4: Analytics & Tracking Requirements

Analytics Event Specification for a Screen

11 fill-in slots · from The AI Prompt Handbook for Business Analysts

Your details

0/11 filled

Analytics Event Specification for a Screen

Define the analytics tracking events for a screen in our app.

SCREEN NAME: [Name as it should appear in analytics]
SCREEN PURPOSE: [What the user does here]
ANALYTICS PLATFORM: [Firebase / Mixpanel / Amplitude / Segment / custom]

UI ELEMENTS THAT NEED TRACKING:
1. [Element 1]: [What it is, what happens on tap]
2. [Element 2]: [What it is, what happens on tap]
3. [Element 3]: [What it is, what happens on tap]

For each trackable interaction, provide:
1. Event name (following [naming convention, e.g., screen_element_action])
2. Screen name parameter
3. Element description (human-readable)
4. Event parameters:
   - item_name: [What was tapped]
   - item_type: [Category of element]
   - [Any contextual parameters: item_id, position, state, etc.]
5. When this event fires (on tap, on view, on success, etc.)

Also specify:
- Screen view event (fires when the screen appears)
- Screen exit event (if needed)
- Any events tied to feature flags or experiments

Highlighted [slots] are still empty. Downloads are plain .txt — paste into any AI assistant.