Cannonball Campaign Workflow
This video require the Adobe Flash Player and Javascript enabled.
In this video we take a look at the essential building blocks of a campaign in Cannonball. Cannonball’s node based workflow makes it easy to create, visualise and modify comprehensive trigger based campaigns, using an interactive graphical interface.
TRANSCRIPT
These are the nodes that we can use to build our campaigns. We’ll look at each of these as we create more complex campaigns, but for now we’ll just add this first one, an Input Node, which will allow us to define which recipients are added to this campaign. Just drag the node onto our working area to create it.
The simplest campaign we can have is just a single email being sent out to all recipients. To create this just add an Output Node of type email, and choose some content (we’ll just use an existing page for now). Now that we have both an Input and an Output node, we can drag a connection between them. These connections define the paths our recipients can travel through our Campaign tree.
So this campaign has an Input, allowing recipients to enter the campaign, and an Output, allowing content to be sent to recipients.
Now we’ll add in a condition node, to limit which recipients can pass from the Input to the Output. Conditions can be based upon any of the User attributes in the system, or on recipient activity such as reading an email or clicking a link . For this example we’ll limit to just users with “Sydney” in their “City” attribute. Now we’ll reconnect the nodes so that recipients first pass through this condition, before they can receive the communication in the Output.
We can add another Condition stack to this node, so that all other recipients (that is, those who do not have “Sydney” in their “City” attribute) can be sent alternate content. Just create another Output node, and join that up to this second Condition stack.
Finally, you may wish to perform an A/B split, to directly test alternate content sections (such as banner variations). We’ll hook a splitter node in between our condition and the final content, with a 50/50 division of recipients. In the campaign reports we’ll be able to compare the result of each option to see which option is more effective.
