Goals are very similar to Triggers, in that your Automation will wait until something happens and won't continue down the path immediately, like when using a Condition.

Your contact won't be assessed as Meeting Goal or Not Meeting Goal, until they reach the Goal Step in your Automation

At that point, an Automation will only progress past the Goal Step if and when a) the goal "happens," or b) the goal doesn't happen in the timeframe specified by the Didn't Meet Goal setting. 

Your contact can only go down one path. If the Automation proceeds down the Didn't Meet Goal path, then your contact does in fact meet that Goal, as in they won't go down the Met Goal path. You can set up a second Goal on the Didn't Meet Goal path to assess if they've met the Goal after the Actions on the Didn't Meet Goal path.

This will give you valuable information as to where on the customer journey your contact is likely to meet the Goal

To set up a Goal, select Goal to choose your goal, then decide if or when someone might continue down the Didn't Meet Goal path. 

You can use the following Goals within your Automations:

New contact created: Continue an automation when a contact is added to your Kizen account, regardless of how.

Field updated: Continue an automation whenever a specific field is updated within a contact record. You can choose between First Name, Last Name, Email Address, Company, or any of the custom fields you've set. 

Tag added to contact: Continue an automation when a specific tag is added to a contact.

On or around date: Continue an automation based on date field types. You can choose to continue the automation on the exact date within that contact record or a specific number of days before or after.

Activity logged: Continue an automation whenever a specific Activity is logged in relation to a specific contact.

Form submitted: Continue an automation whenever a specific Form is submitted by a contact.

Survey submitted: Continue an automation whenever a specific Survey is submitted by a contact.

Purchase success: Continue an automation whenever a purchase goes through. You have the option to select specific products as the goal, or any purchase.
 
Purchase declined: Continue an automation whenever a purchase is declined.

Website visited: Continue an automation when a contact in your account visits a specified website.

Interaction occurred: Continue an automation when a contact in your account makes a specific interaction. 

Email delivered: Continue an automation when a specific email is delivered or any email created from a specific template is delivered. Learn more about how to use the Message Library to trigger Automations here

Email opened: Continue an automation when a specific email is opened or any email created from a specific template is opened. Learn more about how to use the Message Library to trigger Automations here.

Email link clicked: Continue an automation whenever a specific link is clicked across any sent emails.

Email attachment opened: Continue an automation whenever a specific attachment is clicked across any sent emails. 

Text message received from contact: Continue an automation whenever a text message is received from a contact. You can include an optional case-insensitive qualifier (i.e. when they text "Yes").

Using Goals to Remove Contacts from an Automation

A common use of Goals is to use a Goal qualifier as a way to remove someone from an Automation.

When you have a dynamic Automation with multiple steps and you want to assess if the Goal is met at any point during the Automation, you'll want your Automation to look like the following.

Set up your Goal as it's own path, and both sides of the Automation will run at the same time. In this case, your Didn't Meet Goal path is set to Never run, but the left side of the Automation will run until the Goal is met. Since the Goal Step is at the beginning, your Automation will take the Action of canceling the Automation as soon as the Goal is met, whenever the Goal is met.

Did this answer your question?