Back to GrowthDex
Growth idea action plan

App Store source mix split between search, browse, and referrer

Break App Store acquisition into search, browse, app referrer, web referrer, and custom campaigns before moving spend or rewriting the listing.

rare tactic
Best-fit channelApp Store · Analytics · Attribution
Stage + contextattribution · channel mix · mobile analytics · distribution review
BudgetFreebudget tier
Suggested operator signalTarget users who complete the tactic’s intended next action

Why this can grow a startup

A single install total hides which route is actually carrying the store. Apple lets teams see whether discovery came from search, browse, another app, the web, or a custom campaign. That matters because each source suggests a different next move. Search points to metadata and intent match. Browse points to merchandising. Referrers point to partner routes or owned distribution. The split turns App Store optimization from guesswork into route-specific work.

Source-backed example

Apple's acquisition-source reporting shows how many users discover and download an app from App Store search, App Store browse, app referrer, web referrer, and custom marketing campaigns.

Source-reported evidence

Source: App Store Connect Analytics · Browse App Store Connect Analytics tactics

Apple reports acquisition by App Store search, App Store browse, app referrer, web referrer, and custom marketing campaigns.

Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.

Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.

Source discovered: May 29, 2026

App StoreAnalyticsAttributionattributionchannel mixmobile analyticsdistribution review
GrowthDex operator note

When to use it

Use this when App Store, Analytics, Attribution is relevant to attribution, channel mix, mobile analytics and you can run a bounded test with a free budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

How to do it

  1. Choose one target segment and define the exact next action this tactic should prompt.
  2. Adapt the tactic to App Store and Analytics, using evidence from App Store Connect Analytics as context—not as a promised result.
  3. Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
  4. Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
  5. Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Next move

Compare a stack for your situation

Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.

Build my stack

Explore the context

Close the loop

Did you launch this experiment?

Report a launch to help us understand which growth ideas founders put into practice.

This report uses a pseudonymous browser ID. Prompts, names, email, or free-text are not included in outcome events.

Advisory bridge

Apply this with an operator

Turn isolated search tactics into a crawlable visibility system tied to demand and proof.

Work with Ian

SOURCE HUB

More tactics from App Store Connect Analytics

Explore related GrowthDex examples and evidence connected to App Store Connect Analytics.

Open App Store Connect Analytics source hub