Use Case maturity:

Basic

What to expect:

Increase in Revenue

Use Case goal:

Performance

Use case description

Social Media Ad Audiences provides comprehensive instructions for leveraging Bloomreach's audience segmentation to retarget your paid ads more effectively to specific customer groups. The successful implementation of this use case can enhance your ad reach by focusing on particular customer segments, thus driving your overall marketing efficiency and the overall performance of your e-commerce business.

Use Case Items

With this use case, you’ll get an:

• Ad audiences scenario - add to the audience
• Ad audiences scenario - remove from the audience

How to deploy the use case

After downloading the use case, follow these steps.

Meet the requirements

Check if the data in your project meets the requirements. The Use Case Center lists requirements for each use case during the deployment process.

Understand the use case logic

It leverages customer segmentation to create audience groups for your paid account. It's advisable to build unique customer segments. For example, you can divide the customers into three segments: customers who've made 5+ purchases (loyal), 3+ purchases (potential loyal), and 0 purchases (Lost). This segmentation allows ads to be retargeted effectively.

Scenario 1 - ADS add/remove retargeting based on segmentation

This is a template/example of best practices for handling Ad Audiences retargeting with email engagement segmentation. The segments NEEDS TO be replaced by your own segmentation.

The scenario should be triggered daily. In order to comply with GDPR rules, we should check if a customer has given us Paid Media consent. If they did, we check if a customer has a valid email or phone number as an identifier. After, we check if the customer belongs to any of the segments that we want to push OR went through this scenario in the last 90 days. The later is to include customers that are no longer part of the segments but might be still in your ads audiences and thus they need to be removed from them.

In this example, according to the mockup segmentation, three situations may occur:

• If customer is in Loyals segment, we ensure he is added into corresponding audience. If he is NO longer part of the segment, we make sure he is removed from the audience.
• If customer is in Possible loyals segment, we ensure he is added into corresponding Possible loyals audience. If he is NO longer part of the segment, we make sure he is removed from the audience.
• If customer is in Lost segment, we ensure he is added into corresponding Lost audience. If he is NO longer part of the segment, we make sure he is removed from the audience.

BE AWARE THAT YOU SHOULD SETUP THE SEGMENTATION AND NAMING OF THE SEGMENTS AND AUDIENCES BASED ON YOUR NEEDS. IT IS HIGHLY IMPORTANT TO ADJUST THE NAMES IN APPROPRIATE CONDITIONS.

BE AWARE THAT THE ACTION OF ADDING AD AUDIENCES WEBHOOKS IS REQUIRED.

Scenario 2 - ADS Remove customers from audiences [servicing scenario]

This is a template/example of best practices for removing customers from all audiences.

The scenario should be triggered when a customer rejects Paid Media consent. After rejection, the best practice is to wait 2 minutes, in case of unintended rejection, and check if the customer hasn't re-subscribed in the meantime. if not, it has to be checked if a customer has a valid email or phone number as an identifier for removal. Finally, it makes sense to try to remove the customer only if he was added to any audience in the past.

BE AWARE THAT THE ACTION OF ADDING AD AUDIENCES WEBHOOKS IS REQUIRED.