Activities
Activities perform functions on leads, lists and campaigns such as sending out emails or changing lead information.
Add to list {x} | Adds the qualified leads to a particular list |
Assign to sales team, send alert type {y} | Assigns a sales rep to a lead (round robin) and sends an alert to sales rep |
Assign to {x], send alert type {z} | Assigns a specific sales rep to a lead and sends an alert to sales rep |
Change lead attribute {x} to {y} | Changes a chosen attribute for qualified leads to a user-determined value |
Change score {x} | Changes the score attribute for qualified leads based on arithmetic function (eg: + 10, -10) |
Notify assigned sales rep, send alert type {x} | Sends alert to a lead's sales rep |
Remove from campaign {x} | Removes leads from specified campaign |
Remove from list {x} | Removes leads from specified list |
Send alert {x}, send alert type {y} | Sends an alert to a specified email address |
Send email {x} | Sends an email |
Send email {x} over {y} days | Sends an email, spread out over a defined number of days |
Send lead in campaign {x} | Adds lead to a specified campaign |
Synchronize to CRM | Synchronizes lead details with CRM system |
Wait for {x} days | Waits for specified number of days before completing next automation steps |
Wait on weekdays {x} to {y} | Waits until a weekday between specific times |
Wait until {x} | Waits until a specific date before completing next automation steps |
Wait until {x} at {y} | Waits until a specific date and time before completing next automation steps |
Wait {y} day after {x} | Waits a number of days after a date specified in lead details before completing next automation steps |
Decisions
Decisions branch out an automation, allowing a campaign to perform different activities on differently qualified leads.
A decision must specify an action for all applicable leads (yes) and/or all inapplicable leads (no).
System-based
These decisions branch a campaign based on variables based in PUBLITRAC itself.
Added to list {x} | Splits automation based on lead membership of a specified list |
Alert {x} sent | Splits automation based on whether a specific alert was sent out |
Lead synch | Splits automation based on whether a lead was synched to the CRM |
Removed from list {x} | Splits automation based on whether a lead was removed from a specified list |
Split 50% | Splits automation for A/B testing |
Email-based
These decisions branch a campaign based on how a lead has interacted with emails you have sent through PUBLITRAC.
Email sent in last {x} days | Splits automation based on whether leads have received an email from PUBLITRAC in the specified date range |
Email {x} bounced | Splits automation on leads based on whether a specified email bounced |
Email {x} delivered | Splits automation on leads based on whether a specified email was delivered |
Email {x} opened | Splits automation on leads based on whether a specified email was opened |
In email {x} link {y} clicked | Splits automation on leads based on whether a specific link was clicked in a specified email |
Link clicked in email {x} | Splits automation on leads based on whether any link was clicked in a specified email |
Unsubscribed in email {x} | Splits automation on leads based on whether a lead unsubscribed from a specified email |
Lead-based
These decisions branch a campaign based on specific lead details.
Lead field {x} equals {y} | Splits automation based on the value of a specific lead detail |
Lead field {x} contains {y} | Splits automation based on the presence of a defined value in a lead field |
Lead field {x} is empty | Splits automation based on the absence of value in a lead field |
Lead member of list {x} | Splits automation based on whether leads are members of a specific list |
Lead score above {x} | Splits automation based on whether leads are above a specific score |
Lead score below {x} | Splits automation based on whether leads are below a specific score |
Lead score between {x} and {y} | Splits automation based on whether leads have a score within a specific range |
Touched by campaign {x} | Splits automation based on whether a lead has interacted with a specific campaign |
Website-based
These decisions branch a campaign based on how a lead has interacted with your website.
Average pageviews {x} {y} | Splits automation based on whether leads meet a specified threshold for the number of pageviews they have made on your site |
Filled out any form | Splits automation based on whether leads filled out any form on your website |
Filled out form {x} | Splits automation based on whether leads filled out a specific form on your website |
Last visit length {x} {y} | Splits automation based on whether leads have stayed for a specified amount of time on your website during their last visit |
Last visit {x} {y} | Splits automation based on whether leads have visited your website in a specified date interval |
Link {x} clicked | Splits automation based on whether leads have clicked a specific link your website |
Visited website category {x} | Splits automation based on whether leads have visited a category of your website |
Number of pageviews last 7 days {x} {y} | Splits automation based on whether leads have logged a specified number of pageviews on your website in the last week |
Number of pageviews last visit {x} {y} | Splits automation based on whether leads have logged a specified number of pageviews on your website during their last visit |
Number of pageviews {x} {y} | Splits automation based on how many total pageviews a lead has logged on your website |
Number of visits {x} {y} | Splits automation based on number of total visits a lead has logged on your website |
Visited webpage {x} | Splits automation based on whether a lead has visited a specific page on our website |
Website visited | Splits automation based on whether a lead has visited your website |
Related articles