Create a New Target Group from Contact policy allow list

This is a tenant-specific feature; it is useful for those clients:

• who use both Webex Campaign and Webex Connect for their various marketing and non-marketing use cases and
• who use the optional module within Webex Connect called ‘Contact Policy’ to store and manage their customers’ opt-in and opt-out preferences for receiving communications via specific channels.

Pre-requisites for using this feature:

• You must have an active licensed tenant on Webex Connect.
• You must enable the usage of the optional ‘Contact Policy’ module within your Webex Connect tenant.
• You must create at least one ‘Consent Group’ with a Group Category of ‘Allow List’. This ‘Allow List’ will have the email addresses of your customers who have opted in to receive communications from you via the email channel.
• You may request the Webex CPaaS Tech Support team to associate your Webex Campaign tenant with the corresponding Webex Connect tenant.
• As this is a tenant-specific feature, you will need to request the Webex CPaaS Tech Support team to enable the ‘Contact Policy Integration’ feature on the Webex Campaign Admin Console.

Please refer to Contact Policy Groupsfor information on how a Contact policy allow list is created.

To create a New Target Group from Contact policy allow list for an email promotion deployment

1. When creating an email promotion deployment on the deployment canvas, drag and drop the Contact policy group node onto the Target Group placeholder.

2. Click the Add link on the right-side node properties panel to select one of the Contact policy groups (allow lists).

3. After selecting the policy group, click Save Changes. Continue to configure the Schedule and Email content nodes, save the deployment, and activate it.

When you activate the above deployment, messages will be sent only to those email addresses which were present in the allow list (opted-in) as of ~5:15 am. Any new email addresses opted-in (and added to the ‘Allow list’) after 5:15 am, will not be part of this deployment’s target group today.

Any email addresses which have opted-out of the ‘Allow list’ after ~5:15 am, will still be part of this deployment’s initial target group. However, before every message is pushed to email gateway, Webex Campaign will check against the specified ‘Contact Policy Allow List’ that CONSENT value for each email address is still ‘true’ and the value of the ‘EXPIRES’ field is still in the future. Thus, Webex Campaign will automatically suppress the messages to those email addresses which have opted out since ~5:15 am.

Usage notes:

1. You cannot use more than one ‘Contact Policy allow list’ as a Target group source within a deployment; nor can you mix this TG source with any other type of TG source.
2. Webex Campaign will retrieve only ‘allow lists’ from your Webex Connect Contact Policy; i.e. You cannot use a ‘deny list’ as a Target group source.
3. You can use ‘Contact policy allow lists’ only within ‘Simple Promotion’ deployments, i.e. 'Instant Deployments', ‘Follow-up Promotions’ and ‘A/B Promotion’ deployments are out of scope for this feature.
4. If, due to some unforeseen reason, the specified ‘Contact Policy Allow List’ could not be retrieved into Webex Campaign in the early morning, then:
   1. For one-time (non-recurring) deployments which are using that ‘allow list’ as a Target group source, the status of those deployments will be changed to ‘Paused’. The deployment creator will receive the notification alert that the status of their deployment has been changed to ‘Paused’.
   2. For recurring deployments which are using that ‘allow list’ as a Target group source, the status of those deployments will be changed to ‘Pending’. This scenario is conceptually similar to a ‘file missing from SFTP’ scenario when the TG source for a recurring deployment is SFTP. The deployment creator will receive the usual email notification alert that the status of their deployment has been changed to ‘Pending’.
5. If, due to some unforeseen reason, the specified ‘Contact Policy Allow List’ was only partially retrieved into Webex Campaign in the early morning, then, the deployments which are using that ‘allow list’ a Target group source, will run with the available (retrieved subset) of records.

A Target Group created using a Customer Profile Data for SMS and Email channels can be used as a target group for the Facebook channel.

To create a New Target Group for Facebook channel

1. On the Target Group List screen, click +Add New.
2. On the Target Group Creation screen, enter details for the following fields:

• Target group name: Enter a name for the Target Group.
• Source: Select the source as Customer Profile Data from the drop-down list box.

📘

Currently, you have to select the source as Customer Profile Data for Facebook Channel. Other source types are not supported.

• Supported channels: Select the channel as Email or Mobile.
• Description: Enter a description for the target group.
• Target Group Type: By default, Static is selected.

3. Click Target Group Content bar. In this screen, you can select the data source and define the headers for the data.

4. Click Data Sources pane and select the source. If you select multiple sources, then select the relationship between the data sources.

5. Click Output Headers pane and select the desired source and output attributes. You can also add static headers and static values while generating the output using the Static Headers tab.

6. (Optional) To add a static header and value, click on Static Headers and enter Header Name, Header Type and Value in the respective fields.

7. Click Query pane and click Define Filter Conditions. You can also reuse an already saved filter. To filter the output records, click Add a Filter and define the conditions.

8. Enter a name for the Filter, select the Data source, Profile Name and define conditions on profile data.

9. Click Save and Proceed. To reuse the filter in future, click Save As Filter Template.

10. (Optional) Select the checkbox Remove the records from the query result set which have the same value for this attribute to omit duplicate records from the result set based on the selected attribute.

11. Click Additional Information pane and select the appropriate option in case of an issue with a record.

• Skip particular record: Select this option to skip the record that has an issue.
• Skip the file once the threshold is reached: Select this option and enter a threshold to skip the file if the threshold is reached. You can enter the threshold value in absolute records or in the percentage of the records in the file.

12. Click Headers Encryption. When the source is selected, the headers from the target group are displayed. You can enable or disable the encryption of the headers as required. The PII data headers like EMAIL, MSISDN, and CUSTOMERID are encrypted by default. This option is not available when the source is selected as Condition on Campaign Data and Remote Store.

📘

If a contact record within the TG file(s) has values unspecified for these mandatory TG headers, then that contact record will be rejected. Contact records which fail the mandatory header validation will be available to be downloaded as ‘Errors’ for further investigation from the WHO tab after the TG-processing is complete (as shown in the below example screenshot).

13. Click Add.

The Target Group will be saved on the Target Group List screen.