SmartSweets — Kick Sugar, Keep Candy Week one · how the first test actually runs

One test, one week, one number back on Sunday.

The smallest possible first step on the Fruit Flavored Snacks launch — run beside the existing DTC/QVC work, never against it.

What it costs you

A short read of this page. No meeting, no fee, no budget commitment to look.

What it costs your team

Confirming access to whatever ad account and landing page the test runs against — a few minutes, once.

What you get back

One written read on Sunday, in the outcomes table below — not a call, not a deck to sit through.

SmartSweets Sweet Fish
SmartSweets Sourmelon Bites
SmartSweets Candy Salad
SmartSweets in store

Contents

Week one · seven parts
01The test
One arm, one variable, one page. 02How it's sized
The sample the read needs, or it isn't called. 03The week, day by day
Monday setup to Sunday read. 04What's tracked
A short, named list — nothing new invented. 05The pre-registered read
All four outcomes, written before the week starts. 06How you hear back
Daily note, Friday note, Sunday read. No calls. 07What gets cut
Named concepts, with the reason, in writing.
The test

One new creative angle for Fruit Flavored Snacks, read against what's already running.

The newest, least-proven line gets the first look — not the established candy range. Everything else about the account stays exactly as the team already runs it.

Baseline — already live
Control

The team's own current Fruit Flavored Snacks creative and page, untouched, spending exactly what it already spends.

Test — live day two
One new creative angle

A single new concept, at equal budget to the control, on the same landing page the team already owns.

How the read is sized, or it doesn't get called.

A one-week test only means something at a minimum sample. Below that, the honest answer is "not yet," not a guess dressed up as a result.

Sessions needed, each arm
1,500+ [A]

Working minimum for a readable delta at DTC conversion rates

Budget, each arm
set by the team

Held equal on both arms; the team's account, the team's number

Call made
Sunday

Or "too close to call," stated plainly

[A] marks a working estimate, not a SmartSweets figure — no analytics account was available to build this.

The week, day by day.

Mon
AMBaseline confirmed with the team: current spend, CTR, conversion rate. These are the team's numbers, never estimates from here.
PMNew creative finished and handed over for the team's own compliance review before anything runs.
Tue
AMTest arm goes live at equal budget to control. Nothing on the existing account is edited.
PMDelivery confirmed on both arms. Day-one numbers are noise, not a result.
Wed
AMTracking parity checked, not performance. Anything broken is named the same day.
Thu
AMHands off both arms. No budget shifts, no swaps — the restraint is part of the test.
Fri
PMWritten note: what's shipped, what's blocked, what's next. No meeting.
Sat
AMOne delivery check. Weekend traffic is part of the sample, not an anomaly.
Sun
PMSessions checked against the 1,500 bar, both arms read against the pre-registered table below, and one of the four outcomes called — in writing.

What's tracked — a short list, nothing new invented.

EventFiresStatus
Ad impression / clickMeta, via the existing ad accountalready exists
Landing page viewBoth armsalready exists
Add to cartDTC sitealready exists
Checkout completeDTC sitealready exists
Arm assignment tagUTM, on both creative setsadded this week

Built on whatever the team's own analytics already capture — the plan adds one tag, not a new stack.

The pre-registered read, written before the week starts.

ControlTestWhat it meansThe move
flatwinsThe new angle is realScale it against the existing budget
winsflatThe page, not the hook, is the constraintHold creative, test the landing page next
winswinsBoth arms are healthyKeep both running, no change forced
flatflatNeither moved the numberStop guessing at creative; look downstream

How you hear from me — daily note, Friday note, Sunday read.

Daily, Mon–Sat

A short written note: shipped, blocked, today. No call.

Friday

A fuller written summary of the week so far — still no meeting.

Sunday

The pre-registered table, filled in, with one of the four moves called — this is the ask closed out in writing.

What gets cut before it ever runs.

Every angle considered and set aside this week, named, with the reason — so nothing is quietly dropped.

ConceptWhy it's cut
Price-comparison calloutNo competitor can be named or implied in SmartSweets's own voice.
Health-claim angle beyond the sugar figureBlood-sugar language stays exactly as hedged on SmartSweets's own FAQ.
"Sugar-free" framingSmartSweets states 1–4g of sugar per serving, never zero.
Flavor-specific reduction percentagesOnly the 92% and 93% figures are verified on file; no others are used.
Broad plant-based claimKept only to the flavors it's actually true for.