Roblox Journeys First Indie Instrument Worksheet - 2026

If you searched roblox journeys worksheet after November 3, 2026, you do not need another “Sankey shipped” celebration. You need a fill-in first-evening instrument worksheet that forces tool choice, stage/node naming, Hub publish, server-side LogJourneyEvent hooks, session ID policy, a two-path smoke, and a signed go/no-go before anyone pastes an empty chart into Discord.

Roblox announced Analytics: Understand Complex Player Funnels With Journeys. Official setup lives in Journey events. The call signature is on AnalyticsService. Config automation sits in Journeys configs.

This URL is that lab. It is not the what-changed map. It is not the Stop on funnels as journeys. It is not the 12 free Journey event checks. Those own curriculum, refusal, and pass/fail cards. This URL owns the fill-in instrument evening.

Why this matters now

Teams hear “Journeys GA,” paste a Hub snippet into a LocalScript, Play Solo once, and declare analytics live. Names drift from Hub. Session IDs never appear on recurring shops. Partner decks inherit cartoon funnel % for branching shops. The board asks why the Sankey is empty. You skipped the worksheet.

Direct answer: Tonight, fill Sections A–H. Green means you may publish hooks to a test place and run a two-path smoke. Red means HOLD — fix tool choice, naming, or server placement. Do not claim a KPI until Section H is signed. Pair refusal energy with the Stop and prove gates with the checks listicle.

Who fills this worksheet

Time: 90–150 minutes first pass on a copy place; 30 minutes to re-run before a second journey.
Honest limit: Journey events docs + AnalyticsService + your Hub publish are authorities. Event delivery can lag — empty-for-five-minutes is not automatic product death.

Non-repetition

Official facts you must quote (not invent)

From Journey events and the Nov 3 announcement:

1. Journeys model branching paths; funnels remain for ordered sequential steps.
2. Stages contain alternative nodes; any node can complete a stage.
3. Create in Creator Hub → Analytics → Journeys; Acknowledge to publish.
4. Log with AnalyticsService:LogJourneyEvent from server code after validating actions.
5. Journey and node names must exactly match the published config.
6. Use a journey session ID when the same player can repeat the journey.
7. Automatic __entry__ is stage 0 — do not configure or log it.
8. Limits: 2–10 stages, 1–10 nodes/stage, ≤50-character names, character rules.
9. Sessions vs Users views answer different questions.
10. Saving an edit publishes a new version; Users stick to first acquired version.

Pasteable diligence line:

We ran a Journeys first-evening instrument worksheet: confirmed branching tool choice, published Hub config with frozen names, mapped server LogJourneyEvent hooks with session policy, drove two intentional paths on a published place, and signed go/no-go before any partner Sankey claim.

Section A — Lab lock (fill in)

A-gate: If the flow is truly linear with no alternatives, latch KEEP_FUNNEL and stop this worksheet — do not invent a Journey for ceremony. If branching and you still lead decks with unlabeled funnel %, stop and refuse first.

Beginner first path (twenty minutes)

1. Write the player flow in three bullets.
2. Circle alternatives (or, or, or).
3. Fill Section A + B.
4. Do not paste production economy hooks yet.

Section B — Tool choice (fill in)

B-gate: Y + Journey continues. N + Funnel → HOLD this worksheet. Y + still planning a linear funnel → red until tool choice flips.

Decision cheat

Section C — Stage & node naming sheet (fill in)

Rules reminder: 2–10 stages; 1–10 nodes/stage; ≤50 chars; no journey name starting with _; no node starting with __; no commas/quotes/apostrophes in nodes; unique nodes within a stage.

C-gate: Any forbidden character or missing freeze → HOLD publish. Marketing nicknames belong in Discord, not in node strings.

Naming anti-patterns (refuse)

Section D — Hub publish (fill in)

D-gate: Unpublished draft → red. Wrong experience → red. Screenshot missing → redo before code.

Hub publish checklist (speak aloud)

1. Correct universe/experience.
2. Journey name matches Section C.
3. Every node typed exactly.
4. Acknowledge publish.
5. Copy snippet once — then put it on the server.

Section E — Server hook map (fill in)

E-gate: Any client-side log → HOLD. Any “fire on button down before server confirms” → HOLD.

Paste scaffold (adapt — do not ship blindly)

local AnalyticsService = game:GetService("AnalyticsService")

-- Call only after server validation of the player action.
AnalyticsService:LogJourneyEvent(
    player,
    "YOUR_JOURNEY_NAME",
    "YOUR_NODE_NAME"
    -- , journeySessionId  -- add when recurring
)

Exact strings must match Section C / Hub publish.

Section F — Session ID & custom fields (fill in)

F-gate: Recurring shop with OMIT → red. Once-per-player onboarding with random new GUIDs every UI flicker → rewrite policy.

Session policy cheat

Section G — Two-path smoke (fill in)

G-gate: Empty chart with no triage → HOLD KPI. Wrong Analytics tab → redo. Only Path A driven → incomplete.

Smoke triage (if empty)

File notes; do not Sev-1 “Journeys broken” without this table. See also the checks listicle check 9.

Section H — Go / no-go receipt (sign)

RECEIPT: JOURNEYS_INSTRUMENT_WORKSHEET_v1
date_utc: ________
operator: ________
experience: ________
journey_name: ________
tool_choice: Journey / Funnel / Abort
hub_published_y_n: ________
server_only_y_n: ________
session_policy: ________
two_path_smoke_y_n: ________
decision: GO_SMOKE_OK / GO_KPI_CANDIDATE / HOLD / ABORT_KEEP_FUNNEL
owner_sign: ________
notes: ________

H-gate: Unsigned receipt → no Discord “we’re on Journeys” claim.

Evening timeline (suggested)

Cut scope if time-boxed: one journey, ≤3 stages, two nodes max in the branching stage.

Worked fill — gear shop (example answers)

Use as a pattern, not as your production strings.

Worked fill — class pick (example answers)

Creator Discord paste (copy)

Filling the Journeys first-evening worksheet tonight: tool choice → frozen names → Hub publish → server LogJourneyEvent only → session policy → two-path smoke → signed receipt. No LocalScript Sankey folklore. No partner KPI until GO_KPI_CANDIDATE.

Section I — Version & rename discipline (fill when editing later)

First evening often ends at GO_SMOKE_OK. The next failure mode is a “quick rename” for marketing copy that silently publishes a new journey version.

I-gate: Rename without version note → HOLD KPI comparisons across the edit. Per Journey events, saving publishes a new configuration version; Users remain on the version they first acquired.

Rename recipe (safe)

1. Freeze old name sheet as v1.
2. Write v2 names in Section C duplicate.
3. Publish Hub edit.
4. Update server constants in the same PR.
5. Dual-label charts for one cohort window.
6. Cut over standup template to v2 with a dated note.

Common mistakes (worksheet-specific)

Monday re-run (twenty minutes)

Use when adding a second journey after the first evening succeeded.

1. Photocopy Sections A–C only.
2. Confirm the new flow is still branching (B-gate).
3. New journey name — do not overload the first journey with unrelated nodes.
4. Publish Hub; extend E hook map; keep F policy explicit.
5. Mini smoke: one intentional path + one drop-off path.
6. New receipt line on the same doc or a fresh H block.
7. Update Discord: “Second journey worksheet pass — still server-only.”

Company diligence four-liner

1. Scope — First Journeys instrument on a named branching flow after Nov 3 GA.
2. Cost — one copy-place evening vs weeks of empty-chart and funnel-cartoon diligence failures.
3. Evidence — Sections A–H + Hub screenshot + Sessions smoke or HOLD.
4. Owner — analytics/LiveOps signatory on the receipt.

Failure modes

Key takeaways

1. This worksheet is the fill-in evening, not the curriculum or the Stop.
2. Start with tool choice — branching vs linear.
3. Freeze exact journey/node names before Hub publish.
4. Acknowledge/publish in Creator Hub or code is fiction.
5. LogJourneyEvent is server-only after validation.
6. Recurring flows need a session ID policy in writing.
7. Prove with a published two-path smoke.
8. Sign Section H before Discord victory laps.
9. GO_SMOKE_OK ≠ automatic partner KPI — finish the checks kit.
10. KEEP_FUNNEL is a valid honest exit.
11. __entry__ stays automatic.
12. Version edits are schema events.
13. Sessions vs Users must be chosen deliberately.
14. Diligence line belongs in the zip cover.
15. Quotable: Fill the instrument worksheet before you trust the Sankey.

FAQ

What is the Roblox Journeys instrument worksheet?

A first-evening fill-in lab: tool choice, naming, Hub publish, server hooks, session policy, two-path smoke, and a signed go/no-go after Journeys GA.

How is this different from the 12 free checks?

Checks are pass/fail cards. This worksheet is the fill-in receipt you complete while instrumenting. Use both.

Can I finish in under an hour?

Sections A–D yes. Full E–G usually needs a published place smoke — budget 90–150 minutes first time.

Do I need Open Cloud tonight?

No. Hub create + server scripts are enough for the first evening. Open Cloud is optional scale later (Journeys configs).

What if Hub shows no data after smoke?

Run Section G triage; wait/refresh; diff names; confirm server path. See Journey events and the checks listicle empty-chart gate.

Should every game start with a shop Journey?

No. Start with the loudest branching argument (onboarding or shop). One journey done well beats five empty configs.

Is LocalScript logging ever OK for this worksheet?

No. Latch server-only. Client fires fail Section E.

When can I show investors a Sankey?

After GO_KPI_CANDIDATE (smoke OK + checks kit green), with Sessions vs Users labeled.

What if our flow is linear?

Latch ABORT_KEEP_FUNNEL. Keeping funnels honest is success.

Where do I learn the capability map?

What Roblox Analytics Journeys Changed for Creators - 2026.

Can multiple people fill one worksheet?

Yes — assign Operator in Section A and require one owner_sign on H. Pair programming helps on E (hooks) while one person owns Hub publish in D.

What if Acknowledge fails or Journeys is missing in Hub?

Confirm experience permissions and that Journeys appears under Analytics for your universe. Do not invent a spreadsheet Sankey as a substitute — HOLD and escalate access first.

Should I delete the old funnel during the first evening?

Not required. Annotate it HOLD_CARTOON with expiry if leadership still needs a bridge chart. Deleting before GO_SMOKE_OK removes your fallback narrative without proof.

How do custom fields fit the worksheet?

Optional in Section F. If used, write allowed values on the name sheet and include the filter set in the G standup view sentence.

Sources

• Journey events
• Analytics: Understand Complex Player Funnels With Journeys
• AnalyticsService
• Journeys configs
• Creator Roadmap 2026: Fall Update