Schema
How PLAYBOOK fits together.
Every Loop follows one shape: a member or staff action, wrapped in a mechanic, confirmed by proof. The reward waits on the trigger, and Rewards Vault pays it.
The product map shows the parts and how they connect. The data schema below it lists the records each part keeps, so your team can see exactly what is stored and what reports back.
01 – Product map
Action, mechanic, proof, reward.
A Loop is one campaign type. Each Loop runs as a Momentum Journey of one or more stages, and every stage moves through the same five steps.
One stage of a Momentum Journey
Stages repeat in sequence until the member reaches the goal.
1
Action
What the member or staff member does. Refer a friend, book a tour, leave a review.
2
The game shape around the action. Spin to Win, Scratch to Reveal, Scavenger Hunt, Bingo Card, Get in the Game, or Streaks and Tiers.
Optional
Handoff
Points the member to your own page: guest pass, booking form, or voucher. Moves no funds and holds nothing.
3
Trigger
The proof that the action happened. A verification code, a matched record, or what comes back from the handoff page.
4
Reward
Issued only on the trigger. Whole-dollar Bucks or a gift card, to the member, the friend, or both.
5
Vault
The recipient’s balance screen. Available funds, pending funds, and gift cards, with an SMS when a reward lands.
The engine under steps 3 to 5. Validates the trigger, holds and pays the reward, and keeps the ledger. Every Loop is powered by Rewards Vault.
Any participant trigger, in any platform, can carry a staff reward. Each one is set by action, frequency, and time period. Staff Loops pay on it, and staff payouts report separately from member rewards.
Two validation paths
Match. The trigger is matched to an existing validated record in your system.
Eligible on arrival. The trigger qualifies when it comes in. See Integrations.
Verification codes
6
Six-digit code confirms an opt-in.
6
Six-digit code verifies the friend in a referral.
02 – Data schema
The records behind every Loop.
Nine records, linked as shown. Arrows name the record a field points to.
Relationships
Playhas one or moreStages
Stagemay carry oneHandoff
Stagewaits on oneTrigger
Triggerissues zero or moreRewards
Triggermay credit oneStaff Member
Triggermay pay oneStaff Payout
Rewardlands in oneRecipient’s Vault
Recipientowns oneVault