Skip to content

Message experiments

Replace copy debates with a learning habit.

Create campaign variants, control allocation, and compare consistent delivery and engagement signals without separating the experiment from the send.

Illustrative experimentTwo variants
Overview
Audience
Messages
Delivery
Settings

Live workspace

Season message test

Audience

24k

Split

50 / 50

Primary signal

Open
Current flow
Variant ALead with the reward
Variant BLead with the deadline
Decision ruleReview after completion

Example data for product illustration. Not customer performance.

A test is useful only when the decision is clear.

PushHub keeps the hypothesis, variants, traffic split, campaign, and outcome close enough for teams to act on what they learn.

How it works

A lightweight discipline for better player messages.

01

Name the decision

Define what the team wants to learn before changing the copy.

02

Create variants

Change one meaningful message dimension while keeping the audience comparable.

03

Allocate traffic

Choose a deliberate audience split and launch through the campaign workflow.

04

Interpret carefully

Compare consistent signals and retain the result with campaign history.

Capability depth without the fine-print surprise.

Current and planned capabilities are labeled directly, so teams can evaluate PushHub without confusing vision for availability.

Live

Campaign variants

Create alternative titles and bodies alongside the base campaign message.

Live

Traffic allocation

Assign explicit percentages across variants before launch.

Live

Variant reporting

Review variant delivery and engagement results in campaign context.

Roadmap

Automatic winner selection

Planned optimization will require explicit guardrails, a goal, and a minimum evidence threshold.

In the game

Questions worth testing.

01

Value framing

Learn whether players respond better to the reward or the experience it unlocks.

Message angle
02

Urgency

Compare a neutral reminder with a deadline-led version.

Timing frame
03

Specificity

Test a generic announcement against progression-aware context.

Personal relevance

Experimentation should protect interpretation.

PushHub presents delivery and response signals without claiming statistical certainty that the current product does not calculate.

Comparable allocation

Traffic splits are explicit and stored with variants.

One campaign context

Audience and delivery conditions remain attached to the test.

No false certainty

Automatic statistical significance and winner selection remain Roadmap.

Questions teams ask before they commit.

The current campaign workflow supports alternative title and body content with explicit allocation.

Build the next player return.

Start with one app, one meaningful moment, and one audience worth reaching.