Attributes + eligibility
06 / CAMPAIGN OPERATIONS
The right story.
The next customer moment.
Keep audience preparation, creative readiness and delivery in one campaign workflow. Make repeatable steps explicit and follow what happened to each recipient.
Updated October 22, 2026 · Shuffll EngageCAMPAIGN CONTROL BOARDA place for every step.ILLUSTRATIVE WORKFLOW
PREPAREAudienceWho belongs? CreativeWhat is ready?
Template + recipient inputs
GENERATEVideo outputA usable result.
Review readiness + status
DELIVERConfigured channelThe next moment.
Schedule + recipient outcome
Connect audience, creative and timing
Begin with the audience definition and the intended next step. Prepare the recipient attributes used by the creative rules, review the template and confirm the channel configured for the workspace. Eligibility and timing are part of the campaign design, not details to leave until after generation.
The delivery workspace brings audiences, schedules and recipient outcomes into view. A repeatable campaign still needs a ready creative foundation and an appropriate audience for each run.
Keep the milestones visible
PREPAREReady to generate
Review audience, media and eligibility.
GENERATEUsable video output
Inspect completion or failure for the requested output.
DELIVERRecipient outcome
Check the configured channel and its recorded delivery state.
A finished export does not mean a message was sent. A send accepted by a provider is also different from confirmed receipt or a viewer action. Keep those distinctions in reporting and in any downstream automation.
Automate the supported steps
Use the workspace controls for the campaign and the documented interfaces for external operations. Confirm each intended step against the enabled release: a broad workspace workflow does not imply that the same step is available through API V1.
The documented fixed-video API V1 can manage campaigns, recipients, generation jobs and results. Message sending and customer webhook subscriptions are outside that contract. Workspace export notifications are explained separately in the webhook guide.
QUESTIONS, WITH CONTEXT
Go one question deeper.
Explore the details that matter for this part of the workflow.
Preparing a campaign
Make the recipient and timing choices deliberate.
What belongs in a campaign delivery plan?
Specify the intended audience, relevant recipient fields, creative version, eligibility conditions, timing and configured delivery channel. Define what outcome you need to observe after the message, as well as the usable video output itself.
Can campaign schedules and audiences be managed together?
The workspace brings audience preparation, eligibility and schedules into the campaign workflow. Available channels and controls depend on the workspace configuration. Confirm the required setup before treating a schedule as a complete delivery plan.
Does automation remove the need for a readiness review?
No. Repeatable steps still depend on prepared media, appropriate recipients and correctly configured delivery. Review the representative output and required permissions before allowing automation to advance a campaign.
Delivery and outcomes
Use each milestone for the question it actually answers.
How is generation status different from delivery status?
Generation status describes the work of producing a video. Delivery status describes the configured messaging workflow. A generated result may exist before any message is sent, and a send accepted by a provider is not the same as confirmed delivery.
Can API V1 send the campaign messages for me?
Message sending is outside the documented fixed-video API V1 contract. Confirm the workspace delivery configuration or another supported integration path for that step; do not infer sending from campaign creation or generation.
How should failed recipients appear in reporting?
Keep failures visible at their actual stage: preparation, generation or delivery. Inspect the recorded outcome and supported recovery path before retrying. A failure or missing observation should not be counted as a successful customer exposure.
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.