Hey @intrepidexposures293,
The easiest way to randomize content is by using Split Test action, although I am not completely sure that is how I would handle the entire objective.
This is the framework I created at ActiveCampaign to achieve a similar function. The forums probably aren’t the best place to demonstrate this, but I’ll try. Stay tuned for a more thorough explanation from me in the future.
Everything is built around the single responsibility design principle.
Tier 1: The Attribution Router
This is the only automation that has a trigger. Every other automation is triggered by a parent automation like this one. This starts when a contact is first created.
The single purpose of this automation is to route contacts into appropriate sub-automations (Tier 2: Controllers) based on the contact’s attributes. You could gather attributes explicitly when a contact fills out a form, or implicitly based on user behavior etc…
Based on the contact’s attributes, route them into one or more of the Tier 2: Controller Automations
Tier 2: Controller Automations
The single purpose of controller automations is to control the order that you route contacts into Tier 3: Message Automations. In my case, I want to send messaging about our ecommerce deep data integrations to our ecommerce (attribute) customers right away. I may not want to send messaging to a brick and mortar salon about deep data at all. But I would want to send messaging related to our automations, campaigns, and crm to both.
In that example, I would create two Tier 2 automatios: T2 - VERTICAL: Ecommerce, and T2 - VERTICAL: Small Business. I would use the Tier 1 automation created above, to route the contact into the most appropriate Tier 2 controller automation based on their attributes (ecommerce or not).
Tier 2 automations are made up of a series of “Enter automation” actions, and goals. Goals are designed with both a leap action, and a wait until action. If a user has completed an automation, the goal will “jump” them over the enter automation. If the contact hasn’t finished an automation, then the goal will wait until the contact has finished the automation.
When the Tier 2: automation is finished, it drops them back into the Tier 1 Router, to detect if there has been any changes in the user’s attributes, and the loop is finished.
Tier 3: Function Automations
Tier 3 Function Automations’ single responsibility is to message the user, or to drive some sort of user behavior. We measure this by using goals.
We also use the goal to “jump” a user down to the bottom, if they have opened the first email. In this example, the automation sends the first email, and then waits a day. If the contact opens the email in the first day it jumps the second email and ends the automation. If the contact doesnt open the first email, it sends the second email and ends the automation.
This is just an example, please don’t be so aggressive with your own contacts.
You could also replace the goal, with an event. So that way if the user has completed your event, or visited your webpage, or done any number of other things, before entering the automation then you could also just skip them to the end of the automation. For example, if they have already connected the “ecommerce integration” then you dont need to introduce it to them, and you could just skip them to the bottom.
I hope this all makes sense! I am happy to answer any other questions about this since it can be a bit confusing, and will try and get an ebook to you shortly!
