Student pricing is available for eligible university email holders. View plans

NextSprints
NextSprints Icon NextSprints Logo
⌘K
Product Design

Master the art of designing products

Product Improvement

Identify scope for excellence

Product Success Metrics

Learn how to define success of product

Product Root Cause Analysis

Ace root cause problem solving

Product Trade-Off

Navigate trade-offs decisions like a pro

All Questions

Explore all questions

Meta (Facebook) PM Interview Course

Practice Meta-focused PM cases

Amazon PM Interview Course

Practice Amazon-focused PM cases

Apple PM Interview Course

Practice Apple-focused PM cases

Google PM Interview Course

Practice Google-focused PM cases

Microsoft PM Interview Course

Practice Microsoft-focused PM cases

All Courses

Explore all courses

1:1 PM Coaching

Practice in a one-to-one session

Resume Review

Narrate impactful stories via resume

Guides Pricing
nextsprints logo

Not a member?

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement.

nextsprints logo

Register to continue.

Login with Google Login with LinkedIn

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement .

Company focus

AppsFlyer
Product Trade-Off Hard Member-only

For AppsFlyer's Audiences product, should we focus on increasing the number of integrated ad networks or improving the granularity of audience segmentation options?

Prepared by NextSprints

15 mins
Report an error
Strategic Thinking Data Analysis Product Roadmap Planning AdTech Mobile Marketing Analytics Product Strategy Feature Prioritization User Segmentation Ad Tech Mobile Attribution
Product Management Trade-Off Question: AppsFlyer Audiences feature prioritization between ad networks and user segmentation

Introduction

The trade-off we're examining for AppsFlyer's Audiences product is whether to focus on increasing the number of integrated ad networks or improving the granularity of audience segmentation options. This decision is crucial for the product's growth and effectiveness in the competitive mobile attribution and marketing analytics space. I'll analyze this trade-off by considering various factors including user impact, technical feasibility, and business alignment.

Analysis Approach

I'd like to start by asking a few clarifying questions to ensure we're aligned on the context and constraints of this decision. Then, I'll walk through a structured analysis of the trade-off, considering both short-term and long-term implications.

Step 1

Clarifying Questions (3 minutes)

  • Context: I'm thinking about the current market position of AppsFlyer. Could you share how our market share compares to competitors like Adjust or Branch?

Why it matters: Helps determine if we need to focus on differentiation or market expansion. Expected answer: AppsFlyer has a strong market position but faces increasing competition. Impact on approach: If we're market leaders, we might prioritize innovation; if not, we might focus on matching competitor features.

  • Business Context: Based on our revenue model, I assume Audiences is a key revenue driver. What percentage of our overall revenue does it currently contribute?

Why it matters: Helps prioritize this decision against other product initiatives. Expected answer: Audiences contributes significantly, perhaps 30-40% of revenue. Impact on approach: A high revenue contribution would justify more resources and risk-taking.

  • User Impact: I'm curious about our user segments. What proportion of our clients are enterprise vs. small to medium-sized businesses?

Why it matters: Different client sizes may have different needs for network integrations vs. segmentation granularity. Expected answer: Mix of enterprise and SMB clients, perhaps 60/40 split. Impact on approach: Would tailor solution to meet needs of dominant client segment while not neglecting others.

  • Technical: Regarding our current architecture, how modular is it for adding new ad network integrations?

Why it matters: Affects the feasibility and resource requirements for expanding network integrations. Expected answer: Moderately modular, but some legacy systems create challenges. Impact on approach: High modularity would favor network expansion; low modularity might lean towards improving existing features.

  • Resource: Can you give me an idea of our current team capacity? Are we staffed to handle both initiatives simultaneously, or would we need to choose one?

Why it matters: Determines if this is truly an either/or decision or if we can pursue both to some degree. Expected answer: Limited resources, need to prioritize one initiative. Impact on approach: Would necessitate a more focused strategy rather than trying to do both partially.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Jan 22, 2025