Preventing same profile from receiving same push from batch segment

[akwankl]

Hi there,

We have a Journey starting with a Read Audience node reading off a batch segment. The concern from our marketing team is that the size of the batch is huge (1M profiles) and would like to send out in small batches. We are planning to use Condition, and impose a profile cap of around 10K first to test. 

The question then is, how do we prevent/remove the same profile from receiving the same push notification when we go to full production after the test? I can't seem to use events with a journey starting with a Read Audience. How can we approach this?

Thanks.

[SatheeskannaK]

@akwankl, You can setup a separate batch audience to pull profiles that received specific push message and exclude them in the journey. The audience can use the messageExecutionID and feedbackstatus data fields.

[akwankl]

Hi @SatheeskannaK , is there a more real-time way?

It just doesn't make sense that we need to create a segment every time, we send hundreds of push campaigns per month. And also, creating a batch segment would mean we need to wait 24 hours before the segment can be used.

Thanks.

[SatheeskannaK]

If it needs to be near real-time then either use a unitary event type journey allow to the use of experience event data in the conditions or setup an audience criteria that meets the streaming segmentation criteria.

[akwankl]

Hi @SatheeskannaK,

Is there no other way? We need to start a journey with a segment because there are multiple criteria involved. It's really painful having to create another segment each time to remove those who removed the push already for the campaign.

Thanks.

[Sukrity_Wadhwa]

Hi @akwankl,

Were you able to resolve this query with the given solution or on your own? Do let us know.

Thanks!