Shuffll Engage

01 / AUDIENCE & PERSONALIZATION

Know the audience.
Shape the story.

Personalization starts with relevance. A customer’s interests, behavior and place in the journey can inform which story they receive, which scenes belong, and how the message sounds.

Updated October 22, 2026 · Shuffll Engage
AUDIENCE SIGNALSInterestsBehaviorsSegments
THE CREATIVE RESPONSEA different scene.
A familiar voice.
A relevant moment.
Try the illustration ↗

From a signal to a creative decision

Shuffll Engage connects recipient attributes and audience rules to creative variations. A common creative foundation can contain alternative scene and voice choices. Rules determine the applicable version; a configured default keeps the story complete when no rule matches.

For example, an interest attribute can select a travel scene for one segment and a music scene for another. This is a campaign design example, not a claim that Engage infers interests without supplied data.

01Audience signals

Interests, behaviors, segments and recipient attributes supplied to the workflow.

02Creative rules

Match attributes to relevant scene or voice variants and define a default.

03Personal story

Apply relevant content and dynamic script values to the recipient’s experience.

What can change in the story?

Personalize the creative for an audience segment or for one person. Prepared scene and voice variants can change the voice-over, visuals, featured offerings, actors or presenters, script and next-step message. Configure the content and rules available in your workspace, then review representative versions and the unmatched default.

Voice-over
Select a prepared voice variant, spoken message or delivery style.
Visuals and scene selection
Choose a relevant setting, imagery or visual style through alternative video scenes.
Product and service offerings
Feature a relevant product, collection, service or offer within the selected creative variant.
Actors and presenters
Prepare alternative actor or presenter scenes and select the applicable scene variant. This is not a claim that an actor changes live inside generated footage.
Script and message
Use alternative narratives and populate dynamic script values from recipient information.
Call to action
Tailor the next-step message to the audience, recipient or journey stage using the supported delivery experience.
Scene inclusion and defaults
Skip a scene when its rule does not apply and retain a complete default for unmatched recipients.

An audience rule can select shared creative for a segment. Recipient attributes and dynamic values can refine the experience for one person. These workspace creative capabilities are separate from fixed-video API and MCP V1, where adding recipient records does not personalize rendered media.

One customer journey, many useful moments

Use the same approach for welcome experiences, product discovery, loyalty messages, milestone stories and other lifecycle campaigns. E-commerce and product video are applications of a broader audience-led platform.

Keep the audience definition, creative choices and delivery plan aligned. A campaign should explain who it is for, what changes and which configured channel carries the result. The connected workflow guide follows this through delivery and export notifications.

Review the experience before the rollout

Inspect representative recipients, alternative content and the unmatched default. Preview the prepared composition in the studio, check missing media or values, and confirm export and delivery readiness for the chosen workflow.

Audience rules describe who receives which content. They are distinct from a viewer choosing a branch inside a delivered video. See interactive features and real-time rendering for those boundaries.

Try the interactive audience illustration ↗

QUESTIONS, WITH CONTEXT

Go one question deeper.

Explore the details that matter for this part of the workflow.

Audience signals and rules

How the supplied data becomes a creative decision.

What information can inform a personalized video?

Supplied recipient attributes, interests, behavior-related fields and segment membership can inform configured creative rules. Decide which fields the campaign needs and how they arrive; this is not a claim that Engage independently discovers a person’s interests.

Link to this answer ↗
Can personalization change more than the first name?

Yes. The workspace supports scene and voice variants, dynamic script values and scene inclusion rules. The useful question is which creative decision should change for a segment, rather than how many personal fields can appear on screen.

Link to this answer ↗
What happens when no audience rule matches?

A configured default gives the recipient a complete story when no alternative matches. Review that default with representative missing or unmatched values before rollout; an untested fallback can make an otherwise tailored campaign feel incomplete.

Link to this answer ↗

Previewing and deploying variations

Check the versions and choose a supported delivery path.

How should I review different personalized versions?

Inspect representative recipients, each meaningful scene or voice variation and the unmatched default. Review the prepared studio composition, then check an exported sample for the actual workflow. Keep media readiness and missing script values visible during review.

Link to this answer ↗
Is audience personalization the same as a viewer choosing a branch?

No. Audience rules select content from supplied data. A viewer choosing a branch is a different interaction inside a delivered player. The current documented embed implementation does not establish branching stories or in-video forms.

Link to this answer ↗
Does API V1 personalize a video when I add recipients?

No. The documented fixed-video API V1 stores and manages recipients without personalizing the rendered media. The workspace’s broader creative rules are a separate capability surface. See the API release boundary before choosing an integration.

Link to this answer ↗
Product and release scope

This guide describes workspace capabilities and documented implementations. Availability depends on deployment, workspace configuration and the integration contract. Confirm the required features for your rollout with Shuffll.

Public API + MCP documentation ↗

YOUR AUDIENCE. YOUR NEXT CHAPTER.

See the workflow
with your own use case.

Start the conversation ↗