Preventing same profile from receiving same push from batch segment | Community
Skip to main content
A
akwankl
Level 6
April 25, 2024
Question

Preventing same profile from receiving same push from batch segment

  • April 25, 2024
  • 1 reply
  • 935 views

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.

 

1 reply

SatheeskannaK
Community Advisor
SatheeskannaKCommunity Advisor
Community Advisor
April 26, 2024

@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.

Thanks, Sathees
    A
    akwanklAuthor
    Level 6
    April 26, 2024

    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
    Community Advisor
    SatheeskannaKCommunity Advisor
    Community Advisor
    April 26, 2024

    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.

    Thanks, Sathees
      Terms & ConditionsAccessibility statement

      Loading footer...