Apply AARRR to B2B SaaS vs B2C mobile game analytics

WHAT THIS TESTS: Whether you can move beyond memorizing the five pirate metrics and actually instrument them as trackable product events in two environments with fundamentally different user identities, sales motions, and monetization mechanics. The interviewer cares if you understand that analytics design must follow business model constraints, not just growth-hacking slogans.

A GOOD ANSWER COVERS: First, define each AARRR stage with one concrete instrumentation choice per model. For B2B SaaS, acquisition should track qualified trial starts or demo requests tied to an account ID, activation should be the first workspace action that delivers team value such as inviting a colleague or integrating a data source, retention should measure weekly active seats or feature adoption depth across the account, referral should capture in-product invite sends or case-study referrals, and revenue should instrument expansion events like seat upgrades or cross-sell module usage alongside contract renewal dates. For B2C mobile games, acquisition is an attributed install from a specific ad network or organic channel, activation is level-one completion or tutorial finish within the first session, retention is D1, D7, and D30 return sessions, referral is invite-code redemption or social share, and revenue is in-app purchase tier unlocks or rewarded ad views segmented by spender decile. Second, explain the structural differences in identity: B2B needs account-user hierarchy resolution because one buyer funds many users, while B2C is typically anonymous device-level until login. Third, note timing differences: B2B revenue events may lag activation by months due to sales cycles, so leading indicators like PQL score or team activation rate matter more than day-one conversions.

COMMON WRONG ANSWERS: Treating both models with the same generic events such as signup, login, and DAU. Proposing B2C style day-one purchase funnels for enterprise SaaS without acknowledging procurement delays. Ignoring account-level aggregation in B2B and suggesting you only track individual user behavior. Suggesting vanity metrics like total downloads or page views without connecting them to downstream revenue instrumentation. Failing to mention attribution needs for mobile games or sales-assisted touchpoints for B2B.

LIKELY FOLLOW-UPS: How would you handle the identity graph when a B2B trial user invites three teammates who never see the marketing site? What leading revenue indicators would you use if the B2B sales cycle is ninety days? How do you distinguish between a whale and a minnow in the game and why does it change your retention strategy? If a B2B customer churns, how do you know whether it was poor activation or poor expansion?

ONE CONCRETE EXAMPLE: Imagine a B2B project management tool. A strong instrumentation plan fires an Acquisition event when a user from a qualified domain starts a trial, an Activation event when the first project has three distinct collaborators add tasks within seven days, a Retention event when seventy percent of provisioned seats log in weekly, a Referral event when an admin exports a guest-access link used by an external domain, and a Revenue event when the account upgrades from a ten-seat to a fifty-seat plan. Contrast this with a puzzle game where Acquisition is a Unity Ads attributed install, Activation is finishing level five in session zero, Retention is opening the app on day seven, Referral is sending extra lives via a deep link, and Revenue is buying a currency pack within the first seventy-two hours.

Source: amplitude.com