How to safely test Daily Rewards in live using player-attribute segmentation

If your hub is connected only to the live game environment, you can still test a Daily Rewards program safely by limiting visibility to internal test accounts with a player attribute.

Recommended approach

1. Create or identify a test player account.
2. Set a dedicated player attribute for that account, for example test=true.
3. Add a segmentation rule to the Daily Rewards program so it is visible only to players whose test attribute is set to true.
4. Verify the program with the test account before exposing it to general players.

What this is useful for

• Testing in a live-connected environment without showing the program to all users.
• Validating reward visibility and claim behavior before launch.
• Reducing the risk of user-facing issues during setup.

Notes

• This approach relies on player-attribute-based segmentation.
• You will need a test account that can be marked with the chosen attribute value.
• The Daily Rewards program should remain hidden from regular players until the segmentation rule is removed or broadened.

Example

A common setup is to mark one internal account with test=true and configure the Daily Rewards program so only players with that attribute can see it.