Pre-Revenue App Metrics: A Guide to Attribution and Early Traction
Learn how to pair customer evidence with activation and repeat use, track early sources manually, and connect paid app campaigns to in-app behavior.
Before your app earns revenue, show who is finding it, what they do, and whether they return.
- Pair customer evidence with an activation and repeat-use signal.
- Use a manual source log for conversations, referrals, and founder-led outreach.
- Use mobile attribution when paid campaigns need to connect to app actions.
- Report each number with its date range, denominator, and next learning goal.
Before revenue, show which users have the problem, what they do after finding your app, whether they return, and whether anyone commits time or money to testing it. Record the user type and the problem each person describes alongside their first meaningful product action and any return visit. For a consumer subscription app, this connects customer demand to observed product use.
A pre-seed or seed company can bring evidence of demand and learning; a company seeking a later round needs stronger proof that acquisition, retention, and revenue can scale. The right measurement setup depends on how your first users arrive: founder conversations call for a manual log, tagged web campaigns call for campaign parameters, and paid mobile acquisition calls for app attribution that connects attributed installs with in-app behavior.
1. What can you show investors before your app has revenue?
Show a connected chain of evidence: a specific user has a real problem, that user tries the product, reaches a meaningful action, and returns or makes a concrete commitment. CRV's guide to startup traction describes early traction as verifiable market acceptance and says structured pre-revenue demand can include design partners, pilot commitments, pre-orders, and letters of intent. For each commitment, name the buyer, the use case, what the customer agreed to do, and what happened afterward.
Track the next action that shows someone reached value, such as completing setup, saving a first item, finishing a first session, or using a core feature a second time. Choose an action that reflects your app's actual promise; a meditation app might measure a completed first session, while a budgeting app might measure a connected account and first budget.
Qualitative evidence helps explain why people act or leave. First Round Review's account of startup growth by stage recommends learning from customer conversations about who converts, who succeeds, and where users encounter friction. If several new users independently describe the same onboarding confusion, that is a concrete product question to test; record the repeated observation and the change you make in response.
The proof investors expect changes with the company stage, and no single conversion or retention threshold fits every app. Allied VC's early-stage traction guide describes pre-seed and seed evaluation in terms of idea validation, product-market-fit potential, team strength, engagement, retention, customer feedback, pilots, and letters of intent. The same guide describes later-stage rounds as requiring clearer evidence of scalable growth and a working business model, so present a pre-revenue company as a learning and validation story rather than suggesting it already has repeatable revenue.
The strength of demand also depends on who takes the action and what it costs them. CRV places revenue from independent customers at the top of its diligence evidence hierarchy, followed by retention, structured pre-revenue demand, and team momentum. Before revenue, a signed pilot, a design partner who tests weekly builds, or a paid pre-order puts a more concrete action behind interest than a waitlist entry alone.
Use a simple evidence ladder to choose what to collect next:
| Signal | What to record | What it helps you learn |
|---|---|---|
| Problem evidence | User type, problem described, date, and a short direct quote | Whether the same need appears across relevant users |
| Product reach | Source, campaign if known, and new-user count | Where early interest is arriving |
| Activation | The first product action that represents value, with users who completed it | Whether a new user reaches the app's core promise |
| Repeat use | Users who return within a product-appropriate period | Whether initial value leads to another useful session |
| Customer commitment | Pilot, design partnership, pre-order, or letter of intent, including terms and next date | Whether interest has become a specific action |
Present counts alongside a few representative conversations. A count shows how often a behavior happened; a user quote or observed blocker helps explain why. Keep direct evidence distinct from your interpretation, and label planned experiments as plans rather than completed results.
2. Which attribution method fits how you find your first users?
Pick the method that observes the route your users actually take. A tracked campaign link records tagged traffic, a self-reported source question captures what a person remembers, a CRM or spreadsheet organizes direct conversations, and a mobile measurement setup connects paid campaign acquisition with in-app events.
| How users arrive | Method | What the record can establish | Best fit |
|---|---|---|---|
| Friends, community, word of mouth, or an in-person recommendation | Ask the user how they first heard about the app | The source the user recalls and describes | Early demand driven by relationships and conversations |
| Founder outreach, product interviews, prospective design partners, or pilots | Spreadsheet or lightweight CRM | Who you contacted, what they need, current status, and the next action | Low-volume, hands-on customer discovery |
| Web ads, newsletter placements, or campaign links | Tagged campaign URL | Which tagged source, medium, and campaign brought a recorded visit | Web campaigns where the same naming scheme is used consistently |
| Paid campaigns that lead to an iOS or Android app | Mobile app attribution | Which supported paid source receives credit for an attributed install, and the app events that follow | A mobile app buying ads and comparing campaign-to-app behavior |
Airbridge's UTM guide describes UTM parameters as URL tags carrying traffic-source and campaign details that analytics tools can read when someone clicks. Use a stable set of source, medium, campaign, and content labels so a campaign's visits can be separated by channel or placement.
Ask about sources that never arrive through a tagged link. CallRail's self-reported attribution guidance describes asking customers how they heard about a business as a first-party signal that can capture referrals and offline discovery. For an app, add one optional question to signup or an early feedback conversation, such as “How did you first hear about us?” Keep an “other” answer and the user's own words; you can standardize categories during review.
Manual and digital signals complement one another. Someone may hear about the product in a community, click a tagged link several days later, and finally install after a recommendation from a friend. Preserve the direct answer and the tagged campaign as separate fields, then use the record to understand the sequence instead of assigning one source to every part of the decision.
For a small consumer subscription app, the most practical starting combination is usually a simple source question plus the existing product analytics for organic or founder-led discovery. Add campaign tags when you start distributing links systematically. Add mobile attribution when you spend on supported advertising channels and need campaign-level visibility into attributed installs and app actions.
3. How do you build an investor-useful manual source log?
A good manual log connects a person and their source to a dated product outcome or a clear customer commitment. One spreadsheet can handle early volume; as prospects and follow-ups multiply, a CRM can keep an owner and next step visible. Bitrix24's founder CRM guide identifies lead source, owner, current value, risk, and next step as useful early records. Adapt those fields to an app founder's work by separating a user's first product action from a sales-style opportunity.
-
Choose a small set of fields before collecting names. Give each person a record ID, first-contact date, user type, self-reported source, campaign label when available, and the person on your team responsible for follow-up. A short source list might include friend referral, community, creator or newsletter, paid social, search, and unknown; retain a note with the exact answer when a user names a specific group or person.
-
Ask the same source question at the same moment. Put the question in signup or ask during the first onboarding conversation. Keep the wording stable across weeks so you can compare responses. When the user gives more than one source, save the first-heard source and the source that prompted the install separately if they remember both.
-
Record what happened after discovery. Add a date for first open, the first action that represents value, and a return-use date if one occurs. For people who participate in interviews or pilots, add the problem they described, the agreed test, the next meeting or deliverable, and whether the commitment was completed.
-
Keep quotes short and specific. Save the user's exact words about the problem, the point where the product helped, or the reason they stopped. A concise note such as “I made a weekly meal plan after adding my dietary preferences” is more useful than a broad label like “likes the app.” Protect personal information by limiting access to what the team needs and excluding sensitive details from an investor summary.
-
Review source-to-outcome patterns on a fixed cadence. Once a week, compare people by source, activation, and return use; once a month, summarize what changed and which experiment follows. Keep the denominator visible. “Eight of 20 community referrals finished setup” makes the count and rate interpretable; “community is working” is an interpretation that needs the underlying count.
-
Separate a conversation from a commitment. A positive interview is useful problem evidence, while a pilot with a named owner, start date, and defined test is a stronger customer commitment. Record the commitment's status and next date so a possible future deal does not appear as completed demand.
For an illustrative comparison, assume a founder speaks with 12 people referred by a hobby community and 10 from a paid campaign. If 5 community referrals finish the first value action and 2 return the following week, while 2 paid-campaign users finish it and 1 returns, those assumed figures provide an early comparison to investigate. Interview community referrals about what helped them complete the value action, inspect the setup step for both groups, and compare the next cohort using the same activation and return windows.
The log earns its place when it changes a decision. If users from one source activate but do not return, investigate the promise and product experience for that audience. If interviews show a repeated blocker before activation, fix or test that step; if prospects agree to pilots but do not start, log the stall reason and the next action.
4. What should a paid-acquisition mobile app measure before revenue?
For a consumer app running paid campaigns, connect the campaign, attributed install, first value action, and repeat use in that order. Keep a separate conversation log for what users say about the problem and their source, because campaign attribution and customer interviews answer different questions.
-
Name the event that represents first value. Write down the user's meaningful action in plain language, the event that records it, and the time window in which a new user should reach it. Choose a real product outcome, such as completing the first guided session or saving a first plan, rather than a convenient action that says little about value. Keep the same event definition when comparing channels and weeks.
-
Make the acquisition groups comparable. Group users by the campaign or acquisition date that matters to your question, then use the same observation window for every group. For example, compare each campaign's first seven days after install when measuring early activation; use the same event definition and attribution rules in each group.
-
Follow the path from install to activation. Count attributed installs, then the number and share who complete the chosen action. If you assume 100 attributed installs and 24 users who complete activation during the same window, the activation rate is 24 divided by 100, or 24%. Report both the rate and the underlying counts so a small cohort remains visible.
-
Inspect where people leave and whether they return. A funnel shows the steps users complete and where participation drops; a retention view follows a defined group over time. A sharp drop before account setup points to a different product question than a drop after the first successful session. Compare cohorts formed with the same acquisition period and event rules.
-
Add spend only when the inputs are consistent. When campaign spend and app outcomes use the same campaign and date window, calculate cost per attributed install or cost per activated user. Compare those acquisition costs with activation and return patterns to see how much product progress each campaign's spend is buying before revenue.
Airbridge Core Plan is one option for a mobile app buying paid acquisition that needs to compare campaign sources with in-app behavior. The Airbridge pricing page lists Core paid advertising attribution for Google, Meta, Apple Ads, and TikTok, and standard event support with install, purchase, and sign_up among the examples. Choose a standard event as activation when it represents the value your app promises.
Airbridge's report documentation describes Funnel Report as a way to analyze a cohort's user journey and monitor drop-off at each funnel step. It describes Retention Report as a way to monitor a cohort's retention. These views let a small team inspect whether a campaign cohort reaches its first chosen step and whether the group returns, even while revenue remains zero.
The plan's price is one decision input for a founder testing paid acquisition. Airbridge's U.S. pricing page lists a 30-day free trial, then $40+/mo, with 500K data points per month included and no annual contracts. A paid attribution setup makes sense when channel-level app behavior will change a spending or product decision, while a manual source log remains useful for referrals, community discovery, and direct user feedback.
Before turning on a dashboard, confirm these items with the team:
- The activation event exists in the plan's supported event set and reflects a meaningful user action.
- Your install, activation, and return windows have one written definition each.
- Someone owns weekly review of campaign results and the customer notes behind them.
- Every reported rate includes its numerator, denominator, and time period.
5. How should you read activation and retention cohorts as an early signal?
A cohort is a group of users who share a starting point, such as installing in the same week or arriving from the same campaign. Compare each group using the same activation event and follow-up window. This keeps newer users from being compared with older users who had more time to return.
Y Combinator's guide to cohort retention explains that cohort analysis follows groups of new users separately, giving a clearer view of how individual users continue using a product or stop. It recommends reading the curve's shape and whether it flattens, rather than relying on the absolute level alone. A flattening curve suggests a group of users continues to return over time; a declining curve gives the team a reason to study where value fades.
Choose a return period that matches how often your app should be useful. A daily social habit can be measured with daily return behavior, while a utility people use for a weekly task may need a weekly period. State the period in the report so “retention” means a specific behavior, such as “opened the app in week two,” instead of an undefined label.
Activation and retention answer different questions. Activation tells you whether users reach the first useful moment; retention tells you whether they continue to find a reason to come back. Read the two together: high activation with weak repeat use can point to a gap between the onboarding promise and continuing value, while modest activation with strong repeat behavior among activated users can suggest that the product serves a narrower group well.
Add customer context before deciding what to change. Interview a few users who activated and returned, and a few who stopped before the first value action. Ask what users hoped to do, what they did, and what prompted a next session or the decision to leave. First Round Review's growth-stage guide says customer conversations help early-stage teams understand who converts and succeeds; it gives the example of addressing onboarding confusion when three of five interviewed customers report it.
Compare retention across apps with a similar user group, core action, and expected use frequency, using the same observation period. A weekly return rate for a weekly planning app answers a different question than a daily return rate for a social app. Use your own consistently defined cohorts to see whether the product's repeat-use pattern is improving over time.
6. What belongs in an investor update when revenue is still zero?
Write a short update that separates what happened from what you think it means. Include the reporting period, source mix, activation and repeat-use counts, customer commitments or direct feedback, the experiment underway, and the question you will answer next.
| Update section | Include | How to keep it clear |
|---|---|---|
| Period and stage | Date range, product state, and fundraising context | Identify the exact weeks or month covered |
| Demand | New users or prospects by source, with counts | Label self-reported sources and tagged campaign sources separately |
| Product use | New users, activation event and count, and return window and count | Include the numerator and denominator for each rate |
| Customer evidence | A short user quote, pilot status, or defined commitment | Separate feedback, intent, and completed action |
| Learning | The strongest pattern and what you changed or learned | Mark interpretation as interpretation, and connect it to evidence |
| Next test | One specific question, action, owner, and review date | Make the next measurement decision visible |
| Business context | Runway, relevant spending, and the current acquisition test | Add figures when they help explain the period's operating choices |
Visible's investor-update guide recommends a consistent format, repeatable KPIs, and clear requests for investor help. Its investor-update FAQ recommends business-relevant metrics and separating wins from losses. For a hypothetical four-week update, assume 40 community-referral users, 30 paid-campaign users, 18 of 70 completing the first-session event, and 7 returning in week two; the update could read: “Over four weeks, 18 of 70 new users completed our first-session event, and 7 returned in week two. Interviews pointed to setup confusion, so we simplified that step and will compare the next cohort.”
A useful update includes the metric definition next to the number. “Activation: completed first guided session within seven days of first open; 18 of 70 new users” is interpretable across updates. If the event or window changes, label the change and treat the new series as a new definition.
A seed-stage example in First Round Review's account centers investor updates on the month's learning instead of only summarizing metrics and milestones. The leaders then ask what insights they can apply and what questions the learning raises.
Keep claims proportional to what the evidence shows. A waitlist measures signups, interviews capture reported needs, app events show recorded behavior, and a signed pilot records a defined commitment. Put the next learning question beside those results, such as whether the setup change improves first-session completion for users from paid campaigns.
A monthly update can help a small team create a steady learning record while the product and channel mix are changing. Include an investor ask only when a specific introduction, user conversation, or skill would help resolve the next business question. Y Combinator's guide to talking with users encourages founders to speak with a broad range of people who could affect the product's success, which can help a founder define a targeted request instead of asking generally for “feedback.”
FAQ
Can I show traction before I have paying customers?
Yes. Show verified user behavior, customer conversations, repeat use, and specific commitments such as a pilot or design partnership. Label each signal accurately so an interview, a signup, a returned user, and a signed agreement remain distinct forms of evidence.
Should I start with a spreadsheet or mobile attribution?
Use a spreadsheet or lightweight CRM when your first users come through direct conversations, referrals, and small numbers of outreach. Add mobile attribution when you are paying for app installs on supported channels and need to connect campaign acquisition with in-app behavior.
What is a good activation event for a pre-revenue app?
Choose the first action that shows a user reached the app's central value. For an app built around guided workouts, that could be completing a first workout; for a planning app, it could be saving a first plan. Keep the event and its observation window consistent across cohorts.
How many users do I need before comparing cohorts?
For a small cohort, put its size and event counts beside each rate, then use early patterns to choose focused interviews and the next test. Compare successive cohorts using the same definitions to see whether the pattern persists.
Is retention useful when the app has no revenue?
Yes. Retention shows whether users return within a period that fits the app's intended use. Pair the rate with the cohort size, measurement window, and user feedback so the team can connect repeat behavior to product value.
Get Started Free
See how these criteria hold up on the real thing.
