Analytics Naming Convention Reference
5 fill-in slots · from The AI Prompt Handbook for Business Analysts
Your details
0/5 filledAnalytics Naming Convention Reference
Help me establish (or document) a consistent analytics naming convention for our app. CURRENT EXAMPLES (if any): - [Existing event 1] - [Existing event 2] - [Existing event 3] ANALYTICS PLATFORM: [Firebase / Mixpanel / Amplitude / etc.] PLATFORM LIMITATIONS: [Max event name length, character restrictions, etc.] Please create a naming convention guide that covers: 1. Event name format (e.g., screen_element_action or feature.action.detail) 2. Screen name format (e.g., camelCase, snake_case, dot notation) 3. Standard parameter names (item_name, item_type, item_id, etc.) 4. Standard action verbs (tap, view, scroll, submit, dismiss, etc.) 5. Prefixes or namespaces for different feature areas 6. Examples for common patterns: - Screen view - Button tap - Form submission - Error occurrence - Toggle/switch change - List item selection
Highlighted [slots] are still empty. Downloads are plain .txt — paste into any AI assistant.