What Composer Is For
Composer turns synced brand evidence into strategy output you can review, refine, and hand off. It is built for grounded planning: what to do next, how to structure flows, how to sequence campaigns, and how to brief a single email.
- Generate next-play suggestions from available brand evidence.
- Build lifecycle flow strategy for core flows, repurchase, cross-sell, or suppression work.
- Plan multi-send campaign sequences for launches, promos, education, or winback moments.
- Create a focused single-email brief with audience, angle, offer, and execution notes.
- Use shared Trajectory audience logic so strategy and calendar planning stay aligned.
Recommended Workflow
- 1Check Evidence first to confirm Composer has enough synced data for the selected brand.
- 2Review Audience Logic and prepare or map missing Trajectory audiences when execution readiness matters.
- 3Choose the Composer mode that matches the output you need.
- 4Fill only the context fields that materially constrain the strategy.
- 5Add extra context for brand voice, inventory, offer limits, compliance notes, or must-use angles.
- 6Generate the output, then review missing-data warnings and execution notes before using it.
- 7Copy the result or reopen it later from History; archive old jobs when they are no longer useful.
Composer Modes
Suggestions
Use this when you want Composer to find the best next plays. Choose a focus area such as flow revenue, campaign revenue, deliverability safety, or product journey.
Flow Strategy
Use this for lifecycle logic. Pick the flow type, product focus, offer, and channel to generate architecture and implementation guidance.
Campaign Sequence
Use this for a multi-send push. Provide the marketing moment, sequence type, dates, products, offer details, budget guardrails, and whether SMS belongs in the plan.
Single Brief
Use this for one email. Composer requires an email title, goal, and audience so the brief has a clear job and target segment.
Best habit
Evidence And Readiness
Evidence status
Shows whether Composer has enough synced sections to ground strategy for the brand. Ready is strongest; partial or missing means review unavailable sections.
Unavailable sections
Specific data sources Composer could not use. Treat them as context limits when judging the output.
Refresh evidence
Reloads the Composer payload from Turbine. Use this after a sync finishes or after audience setup changes.
Additional context
Your manual constraints. Add details the synced data cannot know, like inventory risk, creative direction, margin limits, or client preference.
Audience Logic
Shared with Trajectory
Composer uses the same audience keys and readiness checks as Trajectory, so segment setup helps both strategy generation and calendar execution.
Includes
Audience definitions Composer can use as likely target groups. These guide strategy and may appear in generated segment logic.
Exclusions
Suppression or safety audiences that keep strategy from recommending risky targeting.
Prepare audiences
Creates or refreshes planner-managed Klaviyo segments when the connection has the required segment scopes.
Map existing
Links a required audience key to an existing Klaviyo segment so Composer and Trajectory can reference the same audience.
Count sync
Refreshes segment counts in Turbine. Composer may lock audience changes while a clean catalog snapshot is syncing.
Reading Output
Recommendations
Prioritized strategy moves with supporting descriptions and evidence when available.
Flow Architecture
Lifecycle steps, goals, logic, and implementation guidance for flow strategy outputs.
Emails
Campaign or brief-level email plans, including audience, angle, offer, content direction, and execution details.
SMS Touchpoints
SMS-specific moments generated when the selected mode and input allow SMS.
Brief Details
The core strategic context: audience, angle, offer, timing rationale, progression, and segment logic.
Execution Notes
Subject-line direction, content blocks, design notes, A/B tests, implementation notes, and QA checks.
History And Copying
History
Recent Composer jobs for the selected brand. Pick a job to reopen its output without regenerating.
Status
Jobs can be queued, running, completed, failed, or archived. Failed jobs show a cleaned-up error when possible.
Copy
Copies the full structured Composer result as JSON. Use this for handoff, review, or external drafting workflows.
Archive
Removes a job from visible history for the brand. It does not send, delete, or change anything in Klaviyo.
Working Safely
- Composer output is strategy content. It does not send to Klaviyo or create live campaigns.
- Review missing-data warnings before treating a recommendation as complete.
- Do not ignore audience-readiness warnings if you plan to execute through Trajectory or Klaviyo.
- Use extra context for facts Composer cannot infer from data, especially inventory, compliance, offer limits, and brand voice.
- QA every generated brief before client delivery or build work. Composer accelerates thinking; it does not replace approval.
Common Questions
Does Composer create Klaviyo drafts?
No. Composer creates strategy output. Trajectory handles calendar planning and Klaviyo draft creation.
Why can Composer generate when audiences are missing?
Strategy can still be useful, but execution readiness may be incomplete. Prepare or map audiences before building drafts.
Why is Single Brief stricter than other modes?
A single email needs a title, goal, and audience to avoid vague copy direction. Composer blocks generation until those are present.
What should I do with missing data warnings?
Treat them as limits on confidence. Refresh evidence after sync, add manual context, or use another tool to verify the underlying signal.
Related Guides
Trajectory guide
Move from Composer strategy into a calendar plan and Klaviyo draft workflow.
Revive guide
Use repeat-purchase and winback evidence before asking Composer for strategy.
What Leakio reads from Klaviyo
Understand the source data that grounds Composer evidence and audiences.