Exclude profiles who have been sent an email | Community
Skip to main content
Level 3
December 19, 2023
Solved

Exclude profiles who have been sent an email

  • December 19, 2023
  • 2 replies
  • 1845 views

We have an urgent ask, so any quick replies will be appreciated. 

 

We have a journey that starts with segment qualification and has a profile cap. Audience that are in the range of the cap receive an email and the rest exit the journey. 

 

The journey evaluates on a daily basis and we'd like to understand how to exclude the profiles from receiving an email if they've already received the same email before. 

 

Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by ShashiCh

You can use inSegment function to exclude/include at journey level using expression editor for condition checks.

2 replies

Level 2
December 19, 2023

All AJO Email tracking data stores in the schema 'AJO Email Tracking Experience Event Schema' as a time series record which gives granular data on clicks, hard/soft bounce delivered status etc. etc. and it has email address and journey details as well. 

 

So if you a create an audience using these event details, these audiences(who received email from this journey) can be excluded from the main audiences built before.

Level 3
December 19, 2023

Is there a way to exclude the audience at the journey level instead of the audience level? Our journeys will re-evaluate before the audience qualification gets updated

ShashiChAccepted solution
Level 3
December 19, 2023

You can use inSegment function to exclude/include at journey level using expression editor for condition checks.

Mohan_Dugganab
Adobe Employee
Adobe Employee
December 19, 2023

@trojan_horse 

you can create a batch segment leveraging the attributes from message feedback event schema and accordingly suppress it, within the journey.

This schema / dataset contains the message delivery logs.

Level 3
December 19, 2023

Is there a way to exclude the audience at the journey level instead of the audience level? Our journeys will re-evaluate before the audience qualification gets updated