Targetting Engaged Audiances in Campaign Workflow

[UmaV]

Hi Team,

Based on email openings, we were attempting to launch a campaign that was divided into Engaged Audiences and Non Engaged Audiences. The audiences who opened the prior campaigns' emails are identified as engaged, whereas the other audiences are identified as non-engaged. I used the intersection activity and the query activity to extract the Email openings from the prior campaign and deduplicate them using their Email ids. However, following the implementatiom of the Intersection activity, the overall data counts of the engaged audiences do not match.

So wanted to know if there were any other strategies we might employ to separate the workflow audiences who are engaged from those who are not, or to fix this intersection activity.

Adding the workflow screenshots for reference.

Here if you could see the total number of engaged audiences from previous campaign is 63,541 and the remaining sets of audiences were 266,101. However after intersection actity the audiences were splitted as 241,936 for Engaed and 24,165 for Non engaged. Which is actually not matching with the total count of 329,642 (63,541+266,101).

Appreciating the quick support!

Thanks in advance!
Uma V

[ParthaSarathy · Accepted solution]

Hi @UmaV ,

To target Engaged audience, you can try this below condition

You can select URL Type as Open or email click depends upon your use case.

To Target Non-Engaged .Audience,

And instead of delivery code, you can use any attribute to identify the required delivery of previous campaign.

[ParthaSarathy]

[UmaV]

Hello @ParthaSarathy 

Thank you for the response.

Could you kindly confirm where we can fetch the Delivery Logs, because I couldn't able to locate them in my Recipient Delivery Logs.

[ParthaSarathy]

Hi, 

Please select nms:recipient schema as Targeting Dimension

[UmaV]

Thanks Much @ParthaSarathy this helps!

[UmaV]

So I've tried the same with the following queries. However, we need to club this engaged audiences with another workflow, so I've utilized the intersecting activity to do so. As you can see in the picture below, I currently have 266,101 fresh audiances and 63,738 engaged audiances.

When I used the intersection activity, I saw that just 25,261 comes out as engaged, when it should have been 63,738. Is there a clear explanation for the decreased counts, or can we find a different activity to replace the intersection?

[ParthaSarathy]

This might be because, there are only 25261 common records between two sets.

By default if you had configured 'keys only' in reconciliation of intersection activity, It will check common records between both sets based on Primary key (Recipient's primary key if both targeting dimension is on Recipient table)

Additionally, If you want to check common records between both tables based on Email Id, In each Query activity's additional data > add @email 

And in intersection activity, Configure as below

The Result of this activity will have common records of both sets based on Email address.

[UmaV]

Thanks a lot for the insights @ParthaSarathy  much helpful!