An analysis ticket tracks a piece of marketing analysis or research work. Use it when the output is an insight, recommendation, or data finding, rather than a deployed campaign.
Analysis tickets use the reference prefix ANL-#.
How analysis tickets differ from campaign tickets
Analysis tickets follow the same pipeline as campaign tickets (Backlog through to Done) with two differences:
There is no Content section. Analysis tickets do not produce campaign content or assemble a native campaign.
The Launch section is sign-off only. There is no assembly step and no deploy action. Signing off at Launch marks the analysis complete and moves the ticket to Done.
The Planning section has the same structure as a campaign ticket: a free-form plan document and three dedicated planning fields (channels, audience, send date). Use these fields to define the scope of the analysis: the channels being studied, the audience segment in question, and the deadline for delivering the output.
When to use analysis tickets
Use an analysis ticket when the work is structured research with a defined scope: specific metrics, a time period, and a breakdown you already know you need. If the question is more open and you are still working out what to look at, use an investigation ticket instead.
Using Xperts on analysis tickets
You can assign an Xpert to an analysis ticket at any stage. The same run rules apply as for campaign tickets: one run at a time, you cannot cancel a run in progress, and Xperts cannot sign off. See Xpert runs for details.
Linking to campaign tickets
If the output of an analysis is a campaign recommendation, link the analysis ticket to the follow-on campaign ticket with a relates to link. This keeps the chain of reasoning visible without creating a blocking dependency.