About AmpIQ

AmpIQ enables customer-centric marketing campaigns. Use segment insights to build high-value segments. Use those segments to add audiences to campaigns. Build campaigns that send those audiences to any combination of downstream marketing workflows.

AmpIQ promotes customer-centric marketing by enabling new insights on every customer, smart segmentation, and seamless campaign integration from an intuitive interface that makes it easy to apply the right segments, test and optimize, and then grow loyalty and lifetime value.

  • AmpIQ generates customer- and segment-level insights, including for brand and channel behaviors, product preferences, revenue sizing, and recommended actions.

  • AmpIQ enables out-of-the-box predictive models, segments, and personas designed to improve customer lifetime value with a visual interface that allows you to explore and create segments on your own.

  • Campaigns can be activated cross-channel to optimize channel mix, drive improved experiences, and improve return on investment.

  • Apply closed-loop measurements, multivariate testing, and control groups to transactions, revenue gains, and key performance indicators for customers.

  • Send these results to any 100+ integrations and any of your downstream workflows, including to marketing, customer experience, advertising, and attribution tools.

Common workflows

The most common workflows for AmpIQ involve segment insights, predictive attributes, and campaigns. Use AmpIQ to:

  • Discover customer segments with product affinities, and then identify the right products for that segment

  • Review customer insights from the Segments page to identify growth opportunities

  • Perform opportunity sizing on a per-segment basis

  • Build segments by customer value, i.e. “top 1%”, “top 5%”, “top 10%”, etc.

  • Review data by predictive model, including predicted customer lifetime value (pCLV), churn propensity, next best product, and discount sensitivity

  • Build segments that leverage customer attributes, behavioral data, and predictive attributes

  • Build detailed campaigns with A/B groupings, and then send them to any customer channel

Requirements

AmpIQ has specific data requirements for data source quality, columns and tables, fields, and additional data sources.

Segments

A segment defines a specific attribute profile that can be used to initiate marketing campaigns using the list of customers that match that profile.

Use the visual editor in the Segments tab to easily build a segment from a series of drop-downs and picklists. As you build the attribute profile refresh segment insights to see how many customers match and to see how much value they bring to your business. When the segment is ready, activate it, and then use it to initiate marketing campaigns.

The Segments page.

The Segments page contains a list of active segments along with recommended segments highlighted across the top of the page.

How segments work

The Segment Editor is the user interface for building segments in AmpIQ. This editor uses a series of drop-downs, picklists, conditions, and values to define an attribute profile. Refresh segment insights to see how many customers match the profile, and then active it as a segment.

The Segment Editor is located within the Segments page in Amperity.

The Segment Editor is available from the Segments page. Click Create from the Segments page to open the editor, and then start building your segment.

Segment names

A good segment name is clear and concise, is not longer than necessary, uses patterns to help lists of segments stay organized, and considers how it might be represented in downstream workflows, such as lists of segments in the Campaigns page in Amperity, but also external systems such as Braze, Campaign Monitor, Facebook Ads, Google Ads, Klaviyo, and Mailchimp.

Database tables

You can use any database table that is available to the Segments page to build attribute groups. All of the tables in the currently-selected database are available from the drop-down menu in each attribute group and are shown in the bottom right corner of the Segment Editor.

Important

Tables must be configured to be available to the Segments page. This must be done by a member of your team who manages databases and tables from the Customer 360 page.

Select a database to use tables in that database to build an attribute profile.
  1. You may change the selected database by choosing another one from the drop-down menu.

  2. The list of tables is refreshed to show the tables in that database.

AND vs. OR (between attribute groups)

The Segment Editor builds segments using a series of WHERE clauses. Each clause defines a single attribute group. There are two locations in the Segment Editor where you must specify the use of AND and/or OR operators within a WHERE statement.

  1. Within every attribute group

  2. Across all attribute groups

Use AND to set multiple conditions, where each condition is evaluated separately and only records that satisfy each condition can be included in the results. Attribute groups that use the AND operator will typically become smaller as the number of attributes used in the attribute group gets larger.

Use OR to combine conditions, where at least one of the conditions must be satisfied to be included in the results. Attribute groups that use the OR operator will typically become larger (or at least stay the same) as the number of attributes used in the attribute group gets larger.

Important

All conditions within an attribute group must use the same operator. In addition, the same operator must be used across all attribute groups. In both situations you have a single choice: AND or OR.

Example segments

The following segments will produce very different outcomes.

Tip

These examples were run against test data used by the Amperity training and documentation teams. Try running a similar segment against your own data (without activating it) so that you can compare and contrast these result patterns against real data in your own tenant.

This segment returns a very small number of customers (fewer than 100), most of whom are active and most of whom are reachable. The 1-year revenue is ~$2500.

This segment returns a large number of customers (more than 5000), some of whom are active and most of whom are reachable. The 1-year revenue is ~$425k.

If you add another condition–surname is like "Smi"–to both examples, the attribute group built using the AND operator gets smaller, but the attribute group using the OR operator gets larger.

Consider the differences in how each operator returns data when you are choosing which attributes to add to attribute groups. You can define multiple attribute groups that use the same database table, such as one that pulls first and last names and another that groups by location using the Customer_360 table in both attribute groups.

You can get the same results as the example that uses the OR operator by creating three attribute groups with a single attribute in each group:

Segment insights

Segment insights within the Segment Editor include the following categories:

  • The number of unique customers.

  • The number of customers who have been active within the last year.

  • The amount of revenue generated from these customers within the last year.

  • The number of customers who are reachable.

When you start building a segment, the values for segment insights represent 100% of your customers and revenue across all categories. As you apply attributes to your segment refresh segment insights and review the the updated values.

Segment insights are available when using the Segment Editor.
  1. Segment insights are shown when you start using the Segment Editor.

  2. As you apply attributes segment insights are reset. Click the Refresh button to update segment insights based on the attributes you have selected. The values for each category are updated.

Segment overview

A segment overview highlights the most important information about a segment, including:

  • How much opportunity does this segment have?

  • Which channels should I engage on?

  • What is the predicted revenue for this segment?

Use the information on the segment overview to help determine the best way to initiate a marketing campaign.

A segment overview available after a segment is activated.

Each segment overview contains the following details:

  1. The number of unique customers in this segment.

    Note

    In order display unique customers in this segment, the Unique Customers insights card queries Amperity IDs to match them up with each unique customers.

  2. The sum of order revenue in this segment over the previous 12 months.

    Note

    In order to display the total revenue for this segment over the past 12 months, the 1-Year Active Customers insights card queries data from transaction attributes, total revenue, and Amperity IDs.

  3. The total order revenue for all unique customers in this segment who have ordered in the previous 12 months.

    Note

    In order to display the total revenue for this segment over the past 12 months, the 1-Year Segment Revenue insights card queries data about transaction attributes and total revenue.

  4. The number of reachable customers in this segment.

    Note

    In order to display reachable customers in this segment, the Reachable Customers insights card customer queries customer contact information, including at least one phone number, email address, and/or physical mailing address.

  5. Revenue statistics, including historical revenue and predicted revenue trends.

  6. The channels through which this segment has customer opportunity.

  7. Segment insight charts for customer behaviors and customer attributes. These charts have a configurable date range and up to six may be selected. Click the Actions menu, and then select Customize charts to choose up to six charts for customer behaviors and for customer attributes.

  8. The list of customers who belong to this segment.

SQL editor

The SQL Segment Editor is an optional interface that allows you to build an attribute profile using Presto SQL. Start with a SELECT statement that returns the Amperity ID, and then apply a series of WHERE statements to define one (or more) attribute groups that match specific conditions and values.

There SQL Segment Editor has the following requirements:

  1. The only field that can be returned by the SELECT statement is amperity_id.

  2. All conditions and values must be contained within a WHERE clause.

  3. A WHERE clause must use one of the following operators: AND or OR.

For example, a segment that uses the OR operator to return customers whose first name begins with “Mi”, last name begins with “Smi”, and who reside in California:

SELECT
  "amperity_id"
FROM
   "Customer_360"
WHERE
  (
    (LOWER("given_name") like '%mi%')
     OR LOWER("state") = 'ca'
     OR (LOWER("surname") like '%smi%')
  )

The following example is identical to the previous example, but shows each condition in its own WHERE clause, using UNION ALL between each clause to group the results together:

SELECT
  "amperity_id"
FROM
   "Customer_360"
WHERE
  (
    (
      "amperity_id" IN (
        SELECT
          "t0"."amperity_id"
        FROM
          "Customer_360" "t0"
        WHERE
          ((LOWER("t0"."given_name") like '%mi%'))
        UNION ALL
        SELECT
          "t1"."amperity_id"
        FROM
          "Customer_360" "t1"
        WHERE
          (LOWER("t1"."state") = 'ca')
        UNION ALL
        SELECT
          "t2"."amperity_id"
        FROM
          "Customer_360" "t2"
        WHERE
          ((LOWER("t2"."surname") like '%smi%'))
      )
    )
  )

Campaigns

A campaign is a message or offer that is sent to a specific group of customers or recipients.

The Campaigns page.

Use the Campaigns page to activate a variety of use cases across your marketing stack. For example:

  • Messaging a group of high customer lifetime value (CLV) customers on Facebook for a VIP event

  • Emailing customers with an affinity toward blue button down shirts for a product liquidation

  • Targeting a segment of customers who are more likely to add a visit to the hotel spa

  • Messaging a group of customers likely to churn with a special offer

  • Showing an ad to re-engage customers who have unsubscribed from email

  • Reaching out to customers that have enrolled in your loyalty program

  • Identifying customers within existing lists, and then pushing targeted subsets for downstream messaging to any channel.

  • Using a control group, along with any number of recipient groups, to measure the quality of a campaign.

How campaigns work

A campaign is a message or offer that is sent to a specific group of customers or recipients.

How campaigns work.

A campaign is defined in the Campaigns page, from which you configure the segments that will be associated with the campaign, the downstream locations to which the campaign will be sent, and the time at which the campaign is to begin.

Segments are associated with a campaign. For example:

  • A segment that includes the list of customers for this campaign.

  • A segment that defines a list of customers who, if also present in the segment that includes the list of customers, will be excluded. This segment is optional, but will take priority over the list of customers in the included segment.

A campaign must be associated with at least one destination, such as Klaviyo, Sailthru, Facebook Ads, Google Ads, HubSpot, etc. A recipient group may be configured to send data to more than one destination. Each recipient group configured for a campaign defines its own list of destinations.

At the scheduled date and time, Amperity will run the segments and build the customer list, after which Amperity will send the results to each configured destination.

When this process is complete, your campaign is ready to be scheduled.

Important

A segment is associated to a campaign using the segment ID, which is durable and unchanging. The name of a segment can be changed, which means if the name of a segment changes, the name of that segment in a campaign will also change. However, the ID (and the association of that segment to the campaign) will not change.

Campaign workflow

Amperity supports the following types of campaign workflows:

Multi-channel

A multi-channel marketing campaign blends marketing strategies across channels (i.e. email, SMS, paid media, etc.) to provide customers a personalized experience, but with consistent messages, offers, and products across all channels.

A multi-channel campaign defines combinations of sub-audiences and channels to define unique sets strategies, with each applied to a sub-audience.

A multi-channel campaign has the following components:

  1. A state change that initiates a campaign message.

  2. A segment that defines the audience to which the multi-channel campaign messages will be applied. This segment can be configured to limit the list to certain types of users, such as only business travellers, high-value customers, and so on.

  3. The use of sub-audiences to partition the audience into a variety of campaign channels. Each sub-audience may be configured to have its own control group.

  4. A launch cadence that defines the frequency–daily, weekly, monthly, quarterly–at which the campaign messages are run.

One-time campaigns

A one-time campaign represents a specific campaign message that is configured to be sent only once.

A one-time campaign can be configured to run in a similar manner as a recurring campaign, but with the purpose being to communicate messages to customers they should see only once. For example:

  • A welcome message to a customer who has joined a loyalty program.

  • A message to a customer who has signed up for a credit card.

A one-time campaign.

Recurring campaigns

A recurring campaign is sent automatically based on an updated/refreshed audience that a customer wants to receive in their outbound destination or a state change, such as an accepted return, a change to a loyalty program, or an alert based on credit card status, with a predefined campaign message and cadence to a list of recipients.

A recurring campaign has the following components:

  1. A state change that initiates a campaign message.

  2. A segment that defines a list of customers to which the campaign message applies. This segment can be configured to limit the list to certain types of users, such as only business travelers, high-value customers, and so on.

  3. A launch cadence that defines the frequency–daily, weekly, monthly, quarterly–at which the campaign messages are run.

A recurring campaign.

Campaign elements

Campaigns are built using the following elements:

Audiences

An audience is a list of customers who match the attributes, filters, and conditions that are applied to a segment.

Use a segment to define a list of customers that represent an audience, and then attach that audience to a campaign.

Exclusion lists

An exclusion list identifies a list of customers who should not receive communications related to a marketing campaign.

Use a segment to define a list of customers that represent an exclusion list, and then attach that exclusion list to a campaign.

Control groups

A control group is the percentage of an audience who will not receive communications related to a marketing campaign. Use control groups to establish a baseline against which you can measure the success of a campaign over time.

A campaign typically has a single control group, unless sub-audiences are defined within the campaign. Each sub-audience may contain a control group.

Recipient groups

A recipient group is the percentage of an audience who will receive communications related to a marketing campaign. A campaign may have more than one recipient group.

You may configure more than one recipient group for each audience and sub-audience within a campaign.

Sub-audiences

A sub-audience is a list of customers who will receive a specific type of communication related to a marketing campaign.

A sub-audience may define users by brand, most commonly purchased sub-brand, product affinity, product category, product type, demographics, etc.

A sub-audience typically represents a set of users for which you have a better understanding of marketing preferences and will receive more specific messaging as part of the campaign. For example, you might split a spring sale email campaign by product affinity so you can send out an email showcasing shorts to customers with a high affinity for shorts and another email advertising t-shirts to customers with a high affinity for t-shirts.

A sub-audience enables you to measure the performance of individual communications in a campaign. For example, you can see how the shorts sub-audience email performed as compared to the t-shirts sub-audience email within the same campaign. Each sub-audience can be configured to use its own control and recipient groups, providing even greater control and flexibility.

Campaign use cases

Use the Campaigns page to activate a variety of use cases across your marketing stack. For example:

  • Use Facebook Ads to message a group of high customer lifetime value (CLV) customers about a VIP event

  • Use Klaviyo or Sailthru to email customers with an affinity toward blue button down shirts for a product liquidation

  • Using Facebook Ads and Klaviyo to target a cross-channel segment that contains customers who are more likely to add a visit to the hotel spa

  • Use Campaign Monitor or Mailchimp to email a group of customers who are likely to churn with a special offer

  • Using Facebook Ads and Google Ads to show ads to customers who have unsubscribed from email, but you want to re-engage

  • Use Shopify data to identify your loyal customers, and then send them additional offers

  • Identifying customers within existing lists, and then pushing targeted subsets and/or apply exclusions for downstream messaging to any channel

  • Using a control group, along with any number of recipient groups, to apply A/B tests that help measure the quality of a campaign

Churn prevention

A churn prevention campaign seeks to engage customers as their likelihood of making a transaction diminishes. This type of campaign uses a series of messages based on thresholds to apply deeper discounts and different messages as probability declines. This approach also allows different strategies to be applied at each stage in the process or based on the likelihood of that customer completing a transaction.

Use a query to identify users based on predicted customer lifetime value (pCLV), specifically to identify the probability of a user from making another transaction. The probabilities could be broken down into the following thresholds:

  • Cooldown: 50-60% probability of future transactions.

  • At risk: 35-50% probability of future transactions.

  • Highly at risk, 20-35% probability of future transactions.

  • Lost, 0-20% probability of future transactions.

and then define a message that is specific to each threshold with custom discount levels, offers, and calls to action.

Important

Part of a churn prevention campaign includes being careful about which messages are sent, and when they are sent. For example, use a frequency safeguard to set a threshold to ensure each user receives an email once per month, once per quarter, once per X days, and so on. Use another frequency safeguard to ensure that a user is eligible to receive a message targeted at the correct probability threshold.

Member activation

A member activation campaign seeks to welcome customers as members to loyalty programs, credit cards, and other opt-in activities. This type of campaign uses a series of messages to help pull the customer closer to additional activities and benefits based on what they had just opted into.

For example, use a query to select all users who have signed up for a loyalty program within the previous 24 hours. Send the results of this query to a downstream email campaign manager, and then send a welcome message to those users.

Predictive models

A predictive model is a feature of AmpIQ that predict customer behavior, such as predicted customer lifetime value (predicted CLV), churn propensity, product affinity, and lifecycle events.

Note

Predictive models require at least four years of historical data (five years or more is recommended), along with the following tables already configured in your customer 360 database:

  1. Customer_360

  2. Merged_Customers

  3. Transaction_Attributes

  4. Transaction_Attributes_Extended

  5. Unified_Itemized_Transactions (updated to include product catalogs)

  6. Unified_Transactions

Common inputs to models

Columns from the Merged_Customers, Unified_Transactions, and Unified_Itemized_Transactions (including product catalogs) are used as inputs to predictive modeling. For multi-brand tenants, the amperity_id column from the Customer_360 table is also used as an input to predictive modeling.

The following columns are common inputs to predictive models:

Source table

Input columms

Customer_360

The amperity_id columns is used as an input to predictive modeling for multi-brand tenants.

Merged_Customers

The following columns are common inputs:

  • amperity_id

  • birthdate

  • city

  • email

  • gender

  • given_name

  • phone

  • postal

  • state

  • surname

Unified_Itemized_Transactions

The following columns are common inputs:

  • amperity_id

  • is_return

  • item_discount_amount

  • item_quantity

  • item_revenue

  • order_datetime

  • order_id

  • product_category

  • product_description

  • product_id

  • product_subcategory

Important

The product_category, product_description, and product_subcategory columns must be joined to the Unified_Itemized_Transactions table.

Unified_Transactions

The following columns are common inputs:

  • amperity_id

  • order_cancelled_quantity

  • order_cancelled_revenue

  • order_datetime

  • order_discount_amount

  • order_id

  • order_quantity

  • order_returned_quantity

  • order_returned_revenue

  • order_revenue

  • purchase_brand

  • purchase_channel

  • store_id

AmpIQ models

AmpIQ provides models for the following behaviors:

  • Churn propensity is a predictive model that determines the likelihood that a customer will be active at any point in time, based on their purchase history. The churn propensity model outputs a score between 0 and 1 that represents a customer’s probability of return.

  • Predicted customer lifetime value represents the total value of all orders a customer is predicted to make if they return to make another purchase during the next 365 days.

  • Product affinity is a predictive model that identifies which customers are likely to purchase by using a combination of historical purchase data and lookalike audiences. The predicted affinity model outputs a ranked list of customers with three recommended audience sizes.

How-tos

This section describes tasks related to AmpIQ:

Add attribute

You can add attributes to your segment by selecting individual attributes from tables or by selecting from a series of pre-configured transactional behavior attributes.

A segment

Add attribute from table

You can add an attribute from a table on the Segments page.

To add an attribute from a table to a segment

  1. From the Segment Editor, click Add Attribute.

  2. From the Source menu, either select a table source or search for the a table source from the search field.

  3. From the Attribute menu, either select an attribute or search for an attribute in the search field.

  4. From the Condition menu, select a condition.

  5. From the value menu, either select a value or search for a value in the search field.

  6. Add another attribute or section.

  7. When done, click Save.

The data appears on the Segments page.

Add attribute from query

You can add an attribute from a query on the Segments page.

To add an attribute from a query to a segment

  1. From the Segment Editor, click Add Attribute.

  2. From the Source menu, either select a query source or search for a query source in the search field.

  3. From the Attribute menu, either select an attribute or search for an attribute in the search field.

  4. From the Condition menu, select a condition.

  5. From the value menu, either select a value or search for a value in the search field.

  6. Add another attribute or section.

  7. When done, click Save.

The data appears on the Segments page.

Add transactional behaviors

You can add transactional behaviors on the Segments page.

To add transactional behaviors to a segment

  1. From the Segment Editor, click Add criteria.

  2. Select one an attribute, from the Transactional Activity menu.

  3. Select a source from the Sources menu.

    Tip

    You can also use the Search field to find a source.

  4. In the menu, select a segment attribute.

  5. In the Operators menu, select an operator.

    Note

    You can delete an attribute by clicking on the ‘x’ to the right of the criteria.

  6. Enter information into the required fields.

  7. Click Add filter.

  8. From the Filters window, select the appropriate conditions and values.

  9. Click Save. The filters appear on the Segment Editor window beneath the associated attributes.

  10. When done adding criteria and sections, click Save to update the segment.

Add condition

You can add conditions on the Segments page.

To add conditions to a segment

  1. From the Segment Editor, click Add Attribute.

  2. From the Source menu, either select a source or search for a source in the search field.

  3. From the Attribute menu, either select an attribute or search for an attribute in the search field.

  4. From the Condition menu, select a condition.

  5. From the value menu, either select a value or search for a value in the search field.

  6. Add another attribute or section.

  7. When done, click Save.

The data appears on the Segments page.

Add section

You can add sections on the Segments page.

To add sections to a segment

  1. From the Segment Editor, click Add Section.

  2. Click Add Attribute.

  3. From the Source menu, either select a source or search for a source in the search field.

  4. From the Attribute menu, either select an attribute or search for an attribute in the search field.

  5. From the Condition menu, select a condition.

  6. From the value menu, either select a value or search for a value in the search field.

  7. Add another attribute or section.

  8. When done, click Save.

The data appears on the Segments page.

Add segment

You can add a segment on the Segments page.

To add a segment

  1. From the Segments page, either click Create Segment or select a segment, click Actions, and then, in the menu, click Edit segment.

  2. On the Segment Editor window, click Add Attribute.

  3. From the Source menu, either select a source or search for a source in the search field.

  4. From the Attribute menu, either select an attribute or search for an attribute in the search field.

  5. From the Condition menu, select a condition.

  6. From the value menu, either select a value or search for a value in the search field.

  7. Add another attribute or section.

  8. When done, click Save.

The segment data appears on the Segments page.

Edit segment

You can edit a segment fron Segments Editor.

To edit a segment

  1. From the Segment Editor, click Actions (upper-right corner).

  2. Click Edit.

  3. Make your changes and then click Save.

    The updated segment data appears on the Segments page.

Configure a multi-channel campaign

You you can configure a multi-channel campaign on the Edit Campaign page.

How to configure a multi-channel campaign

  1. Give your campaign a name.

  2. Choose the segment that represents the audience to use for this campaign.

    Optional. Choose a segment that contains a list of customers to exclude from this campaign.

  3. Configure at least one control group/recipient group set for this campaign. Rename these groups as necessary.

    A control group should be set to 10%, with the initial recipient group set to 90%. Click Add recipient group to add more recipient groups. Rename them as necessary and adjust the percentages as appropriate.

  4. For each recipient group (including the control group, if configured for this campaign), assign multiple destinations.

    Note

    A recipient group with multiple destinations will send data to all of the configured destinations.

  5. Optional. Add one (or more) sub-audiences. Click Add Sub-audience to add more sets to this campaign, and then use the Audience Builder to define the criteria for each sub-audience.

  6. Optional. Give each sub-audience a name.

  7. Optional. Assign multiple destinations to each recipient group in a sub-audience.

  8. Configure recipient list delivery. One-time campaigns you have two options: at a scheduled date and time in the future or as soon as possible.

    Provide the campaign launch date. Amperity uses the campaign launch date to improve results tracking for campaigns.

  9. Click Schedule to put this campaign into the queue.

    Amperity will process the segments, and then send the results to the configured destinations. Please allow for enough time for Amperity to complete this process before kicking off the campaign in the downstream system.

Configure a one-time campaign

You you can configure a one-time campaign on the Edit Campaign page.

How to configure a one-time campaign

  1. Give your campaign a name.

  2. Choose the segment that represents the audience to use for this campaign.

    Optional. Choose a segment that contains a list of customers to exclude from this campaign.

  3. Configure at least one control group/recipient group set for this campaign. Rename these groups as necessary.

    A control group should be set to 10%, with the initial recipient group set to 90%. Click Add recipient group to add more recipient groups. Rename them as necessary and adjust the percentages as appropriate.

  4. For each recipient group (including the control group, if configured for this campaign), assign at least one destination. You may assign more than one.

    Note

    A recipient group with more than one configuration destination will send data to all of the configured destinations.

  5. Optional. Add one (or more) sub-audiences. Click Add Sub-audience to add more sets to this campaign, and then use the Audience Builder to define the criteria for each sub-audience.

  6. Optional. Give each sub-audience a name.

  7. Optional. Assign at least one destination to each recipient group in a sub-audience.

  8. Configure recipient list delivery. One-time campaigns you have two options: at a scheduled date and time in the future or as soon as possible.

    Provide the campaign launch date. Amperity uses the campaign launch date to improve results tracking for campaigns.

  9. Click Schedule to put this campaign into the queue.

    Amperity will process the segments, and then send the results to the configured destinations. Please allow for enough time for Amperity to complete this process before kicking off the campaign in the downstream system.

Configure a recurring campaign

You you can configure a recurring campaign on the Edit Campaign page.

How to configure a recurring campaign

  1. Give your campaign a name.

  2. Choose the segment that represents the audience to use for this campaign.

    Optional. Choose a segment that contains a list of customers to exclude from this campaign.

  3. Configure at least one control group/recipient group set for this campaign. Rename these groups as necessary.

    A control group should be set to 10%, with the initial recipient group set to 90%. Click Add recipient group to add more recipient groups. Rename them as necessary and adjust the percentages as appropriate.

  4. For each recipient group (including the control group, if configured for this campaign), assign at least one destination. You may assign more than one.

    Note

    A recipient group with more than one configuration destination will send data to all of the configured destinations.

  5. Optional. Add one (or more) sub-audiences. Click Add Sub-audience to add more sets to this campaign, and then use the Audience Builder to define the criteria for each sub-audience.

  6. Optional. Give each sub-audience a name.

  7. Optional. Assign at least one destination to each recipient group in a sub-audience.

  8. Configure recipient list delivery. Recurring campaigns require a cadence (daily or weekly), a start date and time, and then an end date. The end date has three options: never, on a specific date, or after a specified number of occurrences.

    Provide the campaign launch date. Amperity uses the campaign launch date to improve results tracking for campaigns.

  9. Click Schedule to put this campaign into the queue.

    Amperity will process the segments, and then send the results to the configured destinations. Please allow for enough time for Amperity to complete this process before kicking off the campaign in the downstream system.

Edit campaign

You can edit a draft, scheduled, or delivered campaign on the Campaigns page.

To edit a draft campaign

  1. On the Campaigns page, on a campaign, click the more options button.

  2. In the menu that appears, click Edit.

  3. On the Edit Campaigns page, make your changes.

  4. When done, click Schedule.

To edit a scheduled campaign

  1. On the Campaigns page, on a campaign, click the more options button.

  2. In the menu that appears, click Unschedule and Edit.

  3. On the Unschedule and Edit dialog box, click Confirm.

  4. On the Edit Campaigns page, make your changes.

  5. When done, click Schedule.

To edit a delivered campaign

  1. On the Campaigns page, click on a campaign.

  2. On the View Campaign page, click Edit.

  3. On the Edit Campaign page, make your changes.

  4. When done, click Schedule.

    Tip

    After a campaign has been delivered, you can edit and reschedule the campaign for a future delivery.