Campaign Studio
Campaigns
Most marketers think of campaigns as being ways to communicate with their contact list. Campaigns can also be useful for lead management, marketing operations, and sales enablement. Campaign Studio’s visual campaign builder can help with both goals, even within a single campaign.
Allow contacts to restart the campaign: One contact usually cannot repeat the same campaign. Enable this option if you build a campaign for a recurring message such as birthdays or subscriptions, or transactional operations such as activity notifications, adding to a lead score, or updating data. Contacts can go through the same campaign multiple times without you having to clone the campaign.
Contacts cannot restart the campaign until they are removed from the campaign. This does not have to be manual for every contact. You can use an action option in the campaign builder to remove contacts once they have gone through a campaign. Alternatively; Contacts can restart a campaign by leveraging Change campaigns action and pointing to the same campaign (recommended approach).
Published: Set the Yes/No toggle bar to publish or unpublish a campaign. An unpublished campaign is inactive. Only publish a campaign when it is ready to go live.
If a campaign already contains contacts, changes to the published campaign do not always apply to those contacts.
However, the changes apply to contacts for events beyond any already scheduled, including pending events.
Changes to already scheduled events do not apply to the contacts.
Changes do not apply if the contact has already passed the stage in the campaign you are modifying.
New events added directly from the contact source do not apply to contacts already in the campaign.
When you attempt to unpublish a published campaign, Campaign Studio displays the following confirmation page:
Campaign Republish Behavior: Control how delays for scheduled campaign events are handled when a campaign is unpublished and republished. Users can set the default option globally, or override the global setting for an individual campaign in the edit form.
Select one of the following options for managing scheduled campaign event delays:
These settings remove the need to manually publish or unpublish campaigns at the required times and helps to control relevance.
To schedule a campaign to publish at a specified date and time:
Click the Publish at (date/time) box.
Click the preferred date and time from the Date and Time picker.
Set Published to Yes.
Campaign Studio marks the campaign as Pending and publishes it at the scheduled date and time.
To schedule a published campaign to unpublish at a specified date and time:
Click the Unpublish at (date/time) box.
Click the preferred date and time from the Date and Time picker.
Campaign Studio unpublishes the campaign at the scheduled date and time.
Acquia recommends you to internally test all campaigns and components that you build in Campaign Studio.
Instruct the testers about the actions, such as open an email sent to them or click a link, that they must or must not perform.
This ensures that every campaign event and associated components are tested thoroughly.
While testing, use mock time periods to shorten the testing intervals. For example, use minutes instead of days, weeks, months, or years. Then, adjust these times to the appropriately intended time periods before publishing the campaign.
For more information, see Testing basics.
Push contact to another Campaign Studio instance: Maps a contact to a different Campaign Studio instance that is configured through the action. Companies associated with the contact will also be created in the destination instance.
Custom fields are not automatically pushed along with contacts and companies. To map the associated custom fields, users must first create custom fields in the destination instance using the same alias and datatype as in the source instance, and then push contacts (with companies) with custom fields to the destination instance.
Send email: Sends an email to the contact.
Campaigns are triggered to either segments or contacts who submit forms. Once you have selected either segments or forms, you will select the actual segments or forms to use. To use both, use the gray selector button on either the left or right side of the contact source box to add whichever source type you did not originally select.
After selecting a contact source, click the gray semi-circle at the bottom of the source box to select an event type.
After you choose an event type and add an event, you either see decisions and conditions connectors or the actions connector.
Decisions and Conditions have yes and no paths.
Campaign Studioyes path. To add events on the yes path, click the green connector on the left of the event box.no path. To add events on the no path, click the red connector on the right of the event box.The lines connecting the decision or condition and the next event match the connector color to help follow the contact’s journey. Campaign Studio’s campaign builder is non-linear and multi-channel. It is possible to have several actions happening at the same time, or mix decisions, actions, and conditions at one time in a campaign.
To change a path, grab the bottom from one event and drag it to the top connector for the event you want to follow.
Having paths from multiple decisions, actions, or conditions that point to the same campaign event, causes an error. To avoid this, use the Jump to Event actions to follow the same path in a campaign.
When editing a campaign, if you encounter the You do not have access to the requested area/action error, update view in the address bar to edit. For example, update marketing.acquia.com/s/campaigns/view/1 to marketing.acquia.com/s/campaigns/edit/1, launch the builder, and ensure that no campaign events have multiple paths leading to the same event.
Decisions are behaviors from your contacts or the actions that your contacts take. The options for decisions change based on the campaign actions before the email. If a contact does something, Campaign Studio sends them down the green path on the left side of the bottom of the condition box, which indicates yes. If not, the contact goes down the red path on the right.
Request dynamic content: If you have a webpage or landing page where you want to add dynamic content, you can push campaign-based dynamic content within the campaign builder. The slot name is what you name the slot in the code on your webpage:
<div data-slot="dwc" data-param-slot-name="dwc">
<h1>Dynamic web content for myslot</h1>
</div>
When a contact *requests* a slot, it means they are a member of that campaign
and they visit the page that the dynamic content is on. When building the
campaign, follow this decision with an action type of **Push dynamic content**.Campaign Studio to a specific phone number, you can look for text messages which include Campaign Studio. To look in your SMS inbox for any message, leave the Pattern the reply should match field empty.Actions are events which require Campaign Studio to do something to the contact or contact record. These can represent sending communications to the contact, or automated operational tasks to keep your marketing running. A single campaign, and even a single stage in a campaign, can include many actions and types of actions.
-10.-10.Jump to Event: Enables users to move contacts from one point in a campaign to another, without having to rebuild certain events. If your contact does not hit your goal at one point in the campaign but does at a later stage, you can send the contact to a different path in the campaign by using a Jump to Event.
For example, you may have a decision for Submits form with several events following the form submission. If the goal is to have a contact submit the form and you have the decision several times in the campaign, using the Jump to Event avoids building all the following events many times.
Once the Jump to Event action is executed, the remaining events on that flow of campaign are not executed. The flow of campaign execution then begins from the event it jumped to.
The Jump to Event action respects an event’s scheduled waiting period configured in the Execute this event field.
When an email is selected, the status of Send to unsubscribed contacts is displayed based on the setting on the Advanced tab on the Emails page. Repeatable emails can be sent to a contact multiple times across all campaigns and non-repeatable emails can be sent to a contact only once. For more information, see Transactional and marketing emails.
Send email to user: Sends a template email to a person or people other than the contact. This may be a specific user or users, the contact’s owner (dynamically sent), or non-users using the To: field. Tokens in the email will display the data from the contact record, not Campaign Studio user data. Emails sent using this action are not counted in statistics for the email.
When an email is selected, the status of Send to unsubscribed contacts is displayed based on the setting on the Advanced tab on the Emails page. For more information, see Transactional and marketing emails.
Send marketing message: Sends content using the contact’s preferred channel if the selected marketing message uses the same channel. For more information, see Marketing Messages.
The New Campaign or Edit Campaign page displays a notification when a user attempts to publish a campaign containing an unpublished email.
Conditions use customer and company data as the criteria for condition-based logic to create highly customizable filters.
[email protected], without spaces or other invalid characters or formats). This does not check if the email address is a live mailbox.Operators apply when using the following campaign conditions:
For detailed information about operators, visit Operators in Campaign Studio.
There are no scheduling options on decisions. As soon as the criteria for the decision is met, the contact is sent down the green/yes path. Any actions or conditions after the decision are scheduled separately. Any actions on the red/no path will “wait” a specified time period before triggering.
No path for decisions, so that a contact has time to actually do something. If an action were immediately triggered on a No path, every contact would go down the No path because they would not have an opportunity to meet the decision criteria. For example, click a link.At a relative time period: Triggers the action after the specified number of minutes, hours, days, months, or years. This option also enables users to schedule actions to trigger at a specified time of day or between specified hours. If a particular time is specified and a contact reaches the event later in the day, the action triggers the next day at that time. Similarly, if a user sets a time range, such as business hours, 09:00 to 17:00/5:00 PM, and the contact reaches the event outside of those hours, the action triggers when the time period begins again. Either one or the other of a specified time or a range of time may be used. When data is entered in one field, others in this section gray out.
The following are the example scenarios for a campaign event that is configured to execute only during weekdays from 3:00 AM to 9:00 AM:
If the campaign event falls on a Tuesday and is configured to execute at 11:00 AM, Campaign Studio reschedules the event to execute on Wednesday at 3:00 AM because the configured time does not match the range of 3:00 AM to 9:00 AM.
If the campaign event falls on a Saturday and is configured to execute at 11:00 AM, Campaign Studio reschedules the event to execute on Monday at 3:00 AM.
If the campaign event falls on Sunday and is configured to execute at 6:00 AM, Campaign Studio reschedules the event to execute on Monday at 6:00 AM.
The following is an example scenario for a campaign event that is configured to execute only on particular weekdays from 3:00 AM to 9:00 AM:
If the campaign event falls on a different weekday and is configured to execute at 6:00 AM, Campaign Studio reschedules the event to execute on the next suitable weekday at 6:00 AM.
If the campaign event falls on a Tuesday and is set to execute on 11 AM , due to it not matching because of the hours, then it would be rescheduled to execute on Wednesday at 3 AM.
For events scheduled with a specific time, an event triggers at the specified time in a contact record’s timezone if the Preferred Timezone field is populated. For example, if a send email action is scheduled for 10:00 am Eastern Standard Time (EST) and a specific contact’s preferred timezone is set as Europe/Paris, the email is sent at 10:00 am Central European Time (CET), which is 4:00 am EST.
At a relative time period: Use this option to wait for a specified amount of time before verifying that the condition is met. If you set up a campaign where a contact must meet a condition before an action, such as email sent, triggers, schedule the condition for when you want the email to be sent.
Once the condition is checked and met, schedule the action to send immediately, at a relative time period, or at a specific date and time. For details, see Action: At a relative time period.
This condition prevents an action from triggering if the contact enters the campaign after the time configured in the condition, and is used to prevent time-sensitive or outdated content from reaching the wrong audience. After the time configured in the condition, Campaign Studio directs the contact to the negative path and does not apply the action to the contact.
Time Stamp: Campaign Start Date refers to the Publish Up date displayed on the DETAILS tab on the campaign details page.
Example scenario 1: When a user saves a campaign for the first time with the Published field set to Yes, but with no date added to the Publish at (date/time) field, the system saves the time of publication as the Publish Up date.
Example scenario:
An unpublished campaign without a Publish at (date/time) is created at 3:10 PM UTC. The user creates a condition in Prevent action after date of less than 5 minutes. When the user publishes the campaign at 3:19 pm UTC, Campaign Start Date sets to 3:19 PM UTC, which is the same as Publish Up displayed on the DETAILS tab. Contacts that are added to the campaign between 3:19 PM UTC and 3:24 PM UTC move to the positive path. Contacts that are added to the campaign after 3:24 PM UTC move to the negative path.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Campaigns are triggered to either segments or contacts who submit forms. Once you have selected either segments or forms, you will select the actual segments or forms to use. To use both, use the gray selector button on either the left or right side of the contact source box to add whichever source type you did not originally select.
After selecting a contact source, click the gray semi-circle at the bottom of the source box to select an event type.
After you choose an event type and add an event, you either see decisions and conditions connectors or the actions connector.
Decisions and Conditions have yes and no paths.
yes path. To add events on the yes path, click the green connector on the left of the event box.no path. To add events on the no path, click the red connector on the right of the event box.The lines connecting the decision or condition and the next event match the connector color to help follow the contact’s journey. Campaign Studio’s campaign builder is non-linear and multi-channel. It is possible to have several actions happening at the same time, or mix decisions, actions, and conditions at one time in a campaign.
To change a path, grab the bottom from one event and drag it to the top connector for the event you want to follow.
Having paths from multiple decisions, actions, or conditions that point to the same campaign event, causes an error. To avoid this, use the Jump to Event actions to follow the same path in a campaign.
When editing a campaign, if you encounter the You do not have access to the requested area/action error, update view in the address bar to edit. For example, update marketing.acquia.com/s/campaigns/view/1 to marketing.acquia.com/s/campaigns/edit/1, launch the builder, and ensure that no campaign events have multiple paths leading to the same event.
Decisions are behaviors from your contacts or the actions that your contacts take. The options for decisions change based on the campaign actions before the email. If a contact does something, Campaign Studio sends them down the green path on the left side of the bottom of the condition box, which indicates yes. If not, the contact goes down the red path on the right.
Request dynamic content: If you have a webpage or landing page where you want to add dynamic content, you can push campaign-based dynamic content within the campaign builder. The slot name is what you name the slot in the code on your webpage:
<div data-slot="dwc" data-param-slot-name="dwc">
<h1>Dynamic web content for myslot</h1>
</div>
When a contact *requests* a slot, it means they are a member of that campaign
and they visit the page that the dynamic content is on. When building the
campaign, follow this decision with an action type of **Push dynamic content**.Campaign Studio to a specific phone number, you can look for text messages which include Campaign Studio. To look in your SMS inbox for any message, leave the Pattern the reply should match field empty.Actions are events which require Campaign Studio to do something to the contact or contact record. These can represent sending communications to the contact, or automated operational tasks to keep your marketing running. A single campaign, and even a single stage in a campaign, can include many actions and types of actions.
-10.-10.Jump to Event: Enables users to move contacts from one point in a campaign to another, without having to rebuild certain events. If your contact does not hit your goal at one point in the campaign but does at a later stage, you can send the contact to a different path in the campaign by using a Jump to Event.
For example, you may have a decision for Submits form with several events following the form submission. If the goal is to have a contact submit the form and you have the decision several times in the campaign, using the Jump to Event avoids building all the following events many times.
Once the Jump to Event action is executed, the remaining events on that flow of campaign are not executed. The flow of campaign execution then begins from the event it jumped to.
The Jump to Event action respects an event’s scheduled waiting period configured in the Execute this event field.
When an email is selected, the status of Send to unsubscribed contacts is displayed based on the setting on the Advanced tab on the Emails page. Repeatable emails can be sent to a contact multiple times across all campaigns and non-repeatable emails can be sent to a contact only once. For more information, see Transactional and marketing emails.
Send email to user: Sends a template email to a person or people other than the contact. This may be a specific user or users, the contact’s owner (dynamically sent), or non-users using the To: field. Tokens in the email will display the data from the contact record, not Campaign Studio user data. Emails sent using this action are not counted in statistics for the email.
When an email is selected, the status of Send to unsubscribed contacts is displayed based on the setting on the Advanced tab on the Emails page. For more information, see Transactional and marketing emails.
Send marketing message: Sends content using the contact’s preferred channel if the selected marketing message uses the same channel. For more information, see Marketing Messages.
The New Campaign or Edit Campaign page displays a notification when a user attempts to publish a campaign containing an unpublished email.
Conditions use customer and company data as the criteria for condition-based logic to create highly customizable filters.
[email protected], without spaces or other invalid characters or formats). This does not check if the email address is a live mailbox.Operators apply when using the following campaign conditions:
For detailed information about operators, visit Operators in Campaign Studio.
There are no scheduling options on decisions. As soon as the criteria for the decision is met, the contact is sent down the green/yes path. Any actions or conditions after the decision are scheduled separately. Any actions on the red/no path will “wait” a specified time period before triggering.
No path for decisions, so that a contact has time to actually do something. If an action were immediately triggered on a No path, every contact would go down the No path because they would not have an opportunity to meet the decision criteria. For example, click a link.At a relative time period: Triggers the action after the specified number of minutes, hours, days, months, or years. This option also enables users to schedule actions to trigger at a specified time of day or between specified hours. If a particular time is specified and a contact reaches the event later in the day, the action triggers the next day at that time. Similarly, if a user sets a time range, such as business hours, 09:00 to 17:00/5:00 PM, and the contact reaches the event outside of those hours, the action triggers when the time period begins again. Either one or the other of a specified time or a range of time may be used. When data is entered in one field, others in this section gray out.
The following are the example scenarios for a campaign event that is configured to execute only during weekdays from 3:00 AM to 9:00 AM:
If the campaign event falls on a Tuesday and is configured to execute at 11:00 AM, Campaign Studio reschedules the event to execute on Wednesday at 3:00 AM because the configured time does not match the range of 3:00 AM to 9:00 AM.
If the campaign event falls on a Saturday and is configured to execute at 11:00 AM, Campaign Studio reschedules the event to execute on Monday at 3:00 AM.
If the campaign event falls on Sunday and is configured to execute at 6:00 AM, Campaign Studio reschedules the event to execute on Monday at 6:00 AM.
The following is an example scenario for a campaign event that is configured to execute only on particular weekdays from 3:00 AM to 9:00 AM:
If the campaign event falls on a different weekday and is configured to execute at 6:00 AM, Campaign Studio reschedules the event to execute on the next suitable weekday at 6:00 AM.
If the campaign event falls on a Tuesday and is set to execute on 11 AM , due to it not matching because of the hours, then it would be rescheduled to execute on Wednesday at 3 AM.
For events scheduled with a specific time, an event triggers at the specified time in a contact record’s timezone if the Preferred Timezone field is populated. For example, if a send email action is scheduled for 10:00 am Eastern Standard Time (EST) and a specific contact’s preferred timezone is set as Europe/Paris, the email is sent at 10:00 am Central European Time (CET), which is 4:00 am EST.
At a relative time period: Use this option to wait for a specified amount of time before verifying that the condition is met. If you set up a campaign where a contact must meet a condition before an action, such as email sent, triggers, schedule the condition for when you want the email to be sent.
Once the condition is checked and met, schedule the action to send immediately, at a relative time period, or at a specific date and time. For details, see Action: At a relative time period.
This condition prevents an action from triggering if the contact enters the campaign after the time configured in the condition, and is used to prevent time-sensitive or outdated content from reaching the wrong audience. After the time configured in the condition, Campaign Studio directs the contact to the negative path and does not apply the action to the contact.
Time Stamp: Campaign Start Date refers to the Publish Up date displayed on the DETAILS tab on the campaign details page.
Example scenario 1: When a user saves a campaign for the first time with the Published field set to Yes, but with no date added to the Publish at (date/time) field, the system saves the time of publication as the Publish Up date.
Example scenario:
An unpublished campaign without a Publish at (date/time) is created at 3:10 PM UTC. The user creates a condition in Prevent action after date of less than 5 minutes. When the user publishes the campaign at 3:19 pm UTC, Campaign Start Date sets to 3:19 PM UTC, which is the same as Publish Up displayed on the DETAILS tab. Contacts that are added to the campaign between 3:19 PM UTC and 3:24 PM UTC move to the positive path. Contacts that are added to the campaign after 3:24 PM UTC move to the negative path.
If this content did not answer your questions, try searching or contacting our support team for further assistance.