Claude Prompts for Generating Actionable User Stories for Tracking Implementation
Stop writing tracking implementation user stories from scratch. Use these expert-crafted Claude prompts to generate clear, consistent, and developer-ready stories for your analytics events. This collection helps you define user actions, properties, and acceptance criteria in seconds, ensuring your tracking is implemented correctly the first time. Boost your productivity and achieve data consistency across your product.
Build a standard user story for tracking a crucial user action, defining event properties and trigger conditions.
Generate a user story for tracking the event '[Event Name]'. As a [User Persona], I want the system to track when I [User Action], so that the product team can understand feature engagement. The story should include:
1. A clear title.
2. A standard 'As a..., I want..., so that...' format....
User Property Update Story
Draft a user story for setting or updating a specific user property, crucial for user segmentation and analytics.
Draft a user story for setting a user property. The goal is to update the property '[Property Name]' with the value '[Property Value]' when a user performs the action '[Triggering Action]'. Include the user story format, technical notes on when the property should be set (e.g., on login, on profile update), and acceptance criteria.
Page View Event Tracking Story
Generate a user story to track views of a specific page or screen, including relevant properties and trigger logic.
Generate a user story to track a 'Page View' event for the '[Page Name]' page. The story should specify the event name (e.g., 'page_viewed') and include properties like 'page_name', 'page_path', and any relevant URL parameters like '[Parameter Name]'. Define the acceptance criteria for when this event should fire.
New User Sign-Up Tracking Story
Quickly generate a comprehensive user story for tracking new user sign-ups, capturing method and date.
Create a user story for the 'User Signed Up' event. The story should track the sign-up method (e.g., 'email', 'google_oauth', 'facebook_oauth') as a property. Also, include a user property update to set the 'signup_date'. Provide clear acceptance criteria.
User Login Event Tracking Story
Generate a tracking story for user login events, capturing method and session status to monitor activity.
Draft a user story to track the 'User Logged In' event. Include properties for 'login_method' (e.g., 'password', 'sso') and 'is_new_session'. The acceptance criteria should state that this event fires upon successful authentication.
Gherkin ACs for Tracking Events
Generate BDD-style (Given, When, Then) acceptance criteria for a specific tracking event, ensuring precise implementation details.
Given the following user story for tracking:
'As a Product Manager, I want to track when a user clicks the 'Add to Cart' button, so that I can measure purchase intent.'
...
Track Specific Button Clicks
Create a detailed user story for tracking a specific button click, including button identity and location.
Generate a user story for tracking a 'Button Clicked' event. The button is named '[Button Name]' and is located on the '[Page/Component Name]' screen. The event should include properties like 'button_name', 'location', and 'page_path'. Provide acceptance criteria.
Form Submission Tracking Story
Generate a tracking story for form submissions, differentiating between success and failure states with clear criteria.
Draft a user story to track the '[Form Name] Form Submitted' event. The event should have a 'status' property ('success' or 'failure'). If it fails, include a 'failure_reason' property. Specify the trigger conditions for both outcomes in the acceptance criteria.
Search Performed Event Tracking
Create a user story to track search queries and their corresponding result counts within your application.
Generate a user story for tracking a 'Search Performed' event. The event must include the 'search_term' and 'results_count' as properties. The acceptance criteria should specify that the event fires after the search results are returned to the user.
Product Added to Cart Story
Generate a specific tracking user story for 'Add to Cart' events, detailing product properties and acceptance criteria.
Create a detailed user story for tracking the 'Product Added to Cart' event. The story must specify the following event properties: 'product_id', 'product_name', 'category', 'price', 'quantity', and 'currency'. Write clear acceptance criteria for a successful addition to the cart.
Order Completed Tracking Story
Generate a user story for the critical 'Order Completed' event, capturing all essential revenue and order details.
Draft a user story for the 'Order Completed' event. This is a critical revenue event. The story should include properties for 'order_id', 'total_revenue', 'tax', 'shipping_cost', 'currency', 'coupon_used' (boolean), and 'number_of_items'. Ensure the acceptance criteria specifies this event fires only on the post-purchase confirmation page.
Client-Side Error Tracking Story
Create a user story to track client-side errors, capturing messages, codes, and component details for debugging.
Generate a user story to track a generic 'Error Occurred' event on the client-side. The event should capture 'error_message', 'error_code', 'component_name', and 'page_path'. The acceptance criteria should state that this event is triggered by the global error handler.
Feature Flag Exposure Tracking
Generate a user story to track user exposure to feature flags, ensuring accurate experiment analysis for variants.
Draft a user story for tracking user exposure to a feature flag. The event should be named 'Feature Flag Exposed' and include properties 'feature_flag_key' and 'variant' (e.g., 'control', 'treatment'). The acceptance criteria should define that this event fires once per session when the feature is first evaluated for the user.
Subscription Upgrade Tracking Story
Generate a user story for tracking subscription upgrades, capturing plan details, billing cycle, and MRR changes.
Create a user story for the 'Subscription Upgraded' event. It should include properties like 'previous_plan', 'new_plan', 'billing_cycle' ('monthly' or 'annual'), and 'mrr_change'. Also, create a user property update for 'current_plan'.
Event Property Data Dictionary
Create a markdown table defining property names, data types, and descriptions for a new tracking event to ensure consistency.
For the event '[Event Name]', generate a markdown table that lists the following properties: '[Property 1]', '[Property 2]', '[Property 3]'. The table should have three columns: 'Property Name', 'Data Type' (e.g., String, Integer, Boolean, Timestamp), and 'Description/Example'. This helps ensure implementation consistency.
Content Shared Event Tracking
Track when users share content, capturing content ID, type, and the sharing platform to measure virality.
Generate a user story for a 'Content Shared' event. The event should track the 'content_id', 'content_type' (e.g., 'article', 'video'), and 'share_platform' (e.g., 'twitter', 'linkedin', 'copy_link').
Checkout Started Funnel Event
Create a user story for the 'Checkout Started' event, a critical e-commerce funnel step, detailing cart properties.
Draft a user story for the 'Checkout Started' event. This event should fire when a user clicks the 'Proceed to Checkout' button from their cart. Include properties for 'cart_total', 'item_count', and 'currency'.
Password Reset Request Tracking
Track 'Password Reset Requested' events, monitoring account security and identifying potential user friction points.
Generate a user story for tracking the 'Password Reset Requested' event. The event should fire when a user submits their email on the 'Forgot Password' page. No sensitive data should be tracked. Include a property for 'request_source' (e.g., 'login_page', 'settings_page').
Item Added to Wishlist Tracking
Track when users add items to a wishlist, capturing product details and user actions to measure interest.
Create a user story for the 'Item Added to Wishlist' event. The story should specify event properties like 'product_id', 'product_name', and 'category'. The acceptance criteria should detail the user action of clicking the 'Add to Wishlist' icon or button.
Notification Interaction Tracking
Generate a tracking story for interactions with in-app or push notifications, detailing ID, type, and user action.
Draft a user story to track the 'Notification Interacted With' event. The event should include properties for 'notification_id', 'notification_type' (e.g., 'promo', 'transactional'), and 'action_taken' (e.g., 'opened', 'dismissed').
Trial Started Event Tracking
Generate a user story for the 'Trial Started' event, capturing trial plan, duration, and start date for SaaS metrics.
Generate a user story for the 'Trial Started' event. This should fire when a user successfully starts a free trial. Include properties for 'trial_plan_name' and 'trial_duration_days'. Also, create a user property for 'trial_start_date'.
Subscription Cancellation Tracking
Track 'Subscription Canceled' events, including plan, reason, and MRR at cancellation to analyze churn.
Create a user story for the 'Subscription Canceled' event. The event should include properties like 'plan_name', 'cancellation_reason' (from a user survey), and 'mrr_at_cancellation'. Also, update a user property 'is_active_subscriber' to false.
Outbound Link Click Tracking
Track when users click outbound links, capturing destination URL, link text, and current page for engagement analysis.
Draft a user story for an 'Outbound Link Clicked' event. The event should be triggered when a user clicks an external link. Include properties for 'destination_url', 'link_text', and 'current_page_path'.
Filter Application Tracking Story
Generate a user story for tracking 'Filter Applied' events, detailing filter types and values on specific pages.
Generate a user story for the 'Filter Applied' event. This should fire when a user applies one or more filters on the '[Page Name]' page. The event properties should include 'filter_type' (e.g., 'price_range', 'category') and 'filter_value' (e.g., '$50-$100', 'electronics').
Video Playback Start Tracking
Track the start of video playback, capturing video ID, title, duration, and play method to measure content engagement.
Create a user story for a 'Video Playback Started' event. The event should include properties like 'video_id', 'video_title', 'duration_seconds', and 'play_method' ('autoplay' or 'manual_click').
Video Playback Milestone Tracking
Track video playback progress at key milestones (25%, 50%, 75%, 100%), capturing video details and percentage reached.
Draft a user story for a 'Video Playback Milestone' event. This event should fire when a user reaches 25%, 50%, 75%, and 100% of a video's duration. The event properties must include 'video_id', 'milestone_percentage', and 'video_title'.
Account Deletion Tracking Story
Track 'Account Deleted' events, capturing user tenure and, if available, reasons for leaving for lifecycle analysis.
Generate a user story for the 'Account Deleted' event. This event should fire when a user confirms they want to permanently delete their account. Include properties like 'user_tenure_days' and 'reason_for_leaving' if available.
Turn these prompts into a reusable workspace
Save your favourite prompts once, reuse them with Alt+P, keep a live Table of Contents of long chats, and export conversations when you're done.
