Collection & launch
01Focus attention on a strategic edit without duplicating the merchant catalog.
Campaign Experiences
Use Campaigns when the reason a shopper arrived should shape the product edit, message, journey, and next merchant action.
For brand, media, commerce, and agency teams.
Search · Social · Email · QR → Campaign Experience

When to use Campaigns
A Campaign starts from a specific reason for arrival — a collection launch, paid ad, creator story, fit problem, event, email, or QR — and turns that context into a tighter product and decision experience.
Focus attention on a strategic edit without duplicating the merchant catalog.
Keep the landing experience aligned with the proposition that earned the click.
Carry a style story into a shoppable decision path rather than a generic catalog grid.
Give physical or event-driven traffic a focused digital continuation.
Campaign operating model
Campaigns reuse the shared VisuTry decision runtime; the differentiator is the context around that runtime, not a separate feature stack.
Traffic source or brief
Focused catalog subset
Campaign Experience
Configured Merchant Actions
Experience + source context
Brand & agency workflow
Brand teams keep reviewed merchant products and identity consistent while commerce or agency teams adapt the experience to a media brief, audience, collection, or source. That separation avoids disconnected campaign microsites and duplicated product truth.
Reference Experience
AKILA · Statement Frames is a Reference Experience assembled from public catalog information. It demonstrates the focused Campaign format and does not imply a customer or partner relationship.
Reference Pilot / Simulation for style-led campaign merchandising.
Open Reference CampaignReference Experience · Not a customer case study or performance claim.
Founding Merchant Pilot
Use your real frames, one hosted Experience, and observable shopper intent before making a larger commitment.