Lesson Goal

In Lesson 8 you designed your first safe A/B tests for offers and prices.

In this lesson you will:

• Define simple player segments based on behavior, not stereotypes.
• Map segments to fair, tailored offers that fit their playstyle and budget.
• Avoid common pitfalls that turn segmentation into pay‑to‑win pressure.

You are moving from “one size fits all” monetization to small, thoughtful variations that respect different kinds of players.

Step 1 – Define Simple, Observable Player Segments

Segmentation starts with how players actually behave, not imagined psychology.

Using your analytics and in‑game events, sketch a first pass at segments like:

• New players – installed recently, low playtime, no purchases yet.
• Engaged non‑spenders – high session count, many days played, still no purchases.
• Early spenders – made at least one purchase in the first 7–14 days.
• Long‑term supporters – multiple purchases over weeks or months.

For each segment, write a short, neutral description:

• New players: “Trying the game, still deciding if it is worth time and attention.”
• Engaged non‑spenders: “Clearly enjoy the game but either cannot or do not want to spend yet.”
• Long‑term supporters: “Enjoy the game enough to support it financially and care about its future.”

Avoid value judgments like “whale” or “cheap”; you are describing patterns, not moral worth.

Mini‑task:
Pick 3–4 segments you can identify today with your existing events (installs, sessions, purchases) and write one neutral description sentence for each.

Step 2 – Decide What Each Segment Actually Needs

Each segment has different frictions and desires. Your offers should help them, not exploit them.

Ask for each segment:

• What is blocking them right now? (materials, time, difficulty, clarity, cosmetics?)
• What would make their experience feel better without forcing payment?
• How much risk can you safely take with them (for example, new experiment vs stable baseline)?

Examples:

• New players:
  • Need clarity on value; good fit for low‑price, high‑clarity starter bundles.
  • Sensitive to perceived greed; avoid aggressive timers or pressure.
• Engaged non‑spenders:
  • Respond well to earnable cosmetics and optional, value‑driven bundles.
  • Do not gate core progression; keep the game fun without paying.
• Long‑term supporters:
  • Often want more ways to support (cosmetics, season‑like passes, supporter bundles).
  • Need strong guardrails against feeling milked or betrayed.

Mini‑task:
For each of your chosen segments, list one friction and one positive desire. You will use these when designing segment‑specific offers.

Step 3 – Design Segment-Specific Offers That Stay Fair

Now you will design one offer idea per segment, grounded in the needs you just wrote down.

Guidelines:

• Offers should improve quality of life, not erase all challenge.
• Avoid “must pay or get stuck forever” designs; always leave earnable paths.
• Keep price points and value consistent enough that players do not feel cheated when they move between segments.

Examples:

• New players:
  • A welcome bundle with a cosmetic + small resource boost at a clear discount.
  • Only shown in the first few days and explained upfront.
• Engaged non‑spenders:
  • Occasional cosmetic‑only bundles or “support the dev” packs with no gameplay power.
  • Earnable cosmetics through events to show respect for time‑rich, cash‑poor players.
• Long‑term supporters:
  • Larger supporter bundles or cosmetic passes with clearly listed contents and no hidden power.
  • Discounts or perks that acknowledge their history (for example, titles, skins, or small thank‑you gifts).

Mini‑task:
Write a one‑line offer concept for at least two segments (name, what it gives, why it is fair). Keep it short and without exact pricing for now.

Step 4 – Choose Where and When Each Segment Sees Offers

Segmentation is not only about what you show; it is about where and when you show it.

Decisions to make:

• Entry points:
  • New players: subtle prompts on main menu or after a positive moment (unlock, victory screen).
  • Long‑term supporters: clearly labeled store sections, not surprise pop‑ups.
• Timing:
  • Avoid interrupting first‑time user experience with hard sell screens.
  • Align offers with natural milestones (chapter complete, new mode unlocked, anniversary).
• Frequency:
  • Limit how often any segment sees blocking paywalls or pushy pop‑ups.
  • Use soft reminders (small badges, store highlights) over constant dialogs.

Mini‑task:
For one segment and one offer, decide:

• Which screen it appears on.
• Which moment triggers it.
• How often the player can see it before it quiets down.

Write this as a three‑bullet mini spec.

Step 5 – Connect Segmentation to Your Analytics and A/B Tests

Segmentation becomes powerful when it connects to the A/B testing discipline you built in Lesson 8.

For each segment‑offer pair:

• Assign a clear segment_id (for example, new_player, engaged_non_spender, supporter).
• Tag offer view and purchase events with:
  • segment_id
  • experiment_id (if part of a test)
  • offer_id or bundle_id

This lets you answer questions like:

• “Do engaged non‑spenders respond better to cosmetics or resource boosts?”
• “Does this supporter bundle increase revenue without hurting retention?”

You can then:

• Reuse the A/B test template from Lesson 8, but scoped to specific segments.
• Compare behavior within a segment first, then across segments.

Mini‑task:
Pick one segment‑offer pair and define:

• segment_id
• offer_id
• experiment_id (if you plan to test variants)

Add these three IDs to your analytics checklist.

Step 6 – Ethics Check: Avoid Punishing the Wrong Players

Segmentation can easily drift into punishment if left unchecked. Run a quick ethics check on your plan:

• Are you charging more to players who have already supported you the most?
• Are you hiding the best value behind aggressive FOMO or paywalls?
• Would a reasonable player feel tricked if they saw how other segments are treated?

Safer patterns:

• Use segmentation to soften friction (for example, gentle boosts to struggling players).
• Give long‑term supporters more ways to celebrate their involvement, not to buy power.
• Keep core progression and competitive integrity fair across segments.

If any part of your plan feels embarrassing when explained out loud to another developer or player, scale it back.

Mini‑task:
For each segment, write one sentence starting with:
“We are not allowed to…” and fill in a practice you want to avoid (for example, “We are not allowed to lock story content behind segment‑only paywalls.”).

Step 7 – Fold Segmentation into Your Live Ops Roadmap

Finally, plug segmentation into the roadmap and calendar from Lesson 7:

• Mark which events or promotions will be:
  • Global (everyone sees the same thing).
  • Segment‑tuned (content or offers change based on segment).
• Plan review points where you check:
  • Whether segments still reflect real behavior (they may drift over time).
  • Whether any segment is being over‑targeted with pay prompts.

You do not have to launch every segment‑specific idea at once. Start small:

• One new‑player offer.
• One supporter‑focused cosmetic bundle.
• One engagement‑focused event with earnable rewards for non‑spenders.

Then review data and adjust.

Your Checklist Before Moving On

Before you continue to the next lesson, make sure you have:

• 3–4 clear player segments defined from real behavior data.
• At least one offer concept per key segment, written in plain language.
• A plan for where and when each segment will see its offers. -, Analytics tags (segment_id, offer_id, experiment_id) planned for segmented offers.
• A short ethics rule list that prevents unfair or predatory segmentation.
• Segmented offers penciled into your live ops calendar from Lesson 7.

With this in place, your monetization system becomes more like a set of tailored, player‑friendly experiences and less like a one‑size‑fits‑all store. In the following lessons, you will connect segmentation and offers to deeper lifetime value thinking and platform constraints so you can grow revenue sustainably.