Batch audience activation to Azure Event strange behaviour

[Michael_Soprano]

What I did:

1. Created batch audience. Customer fell into that audience for the first time 

2. Mapped this audience with Azure Event 

3. For the first time recalculation users were not sent to Azure Event (why ???)

4. I ingested data in Batch way and then when some attributes changed on the profiles from audience (point 1) then these records were sent to Azure Event ...

Someone can explain me this behaviour?

[arpan-garg]

Hi @Michael_Soprano  - Are you trying to say that on the initial load the profiles qualified were not sent to the Azure event? From what i understand you are trying to send batch audience data to a streaming destination which is event hub is it correct?

[Michael_Soprano]

Yes and it should work.

However as @Devyendar said there are some limitations which are not explicitly explained in the documentation. 

My processes looks as follows: 

1. Data Distiller process 1 which write data into dataset XYZ

2. Audience recalculation - even if the profile is in the audience its not automatically sent to Azure Event. Using data from dataset XYZ 

3. Data Distiller process 2 which writes the same data into the same dataset (XYZ from point 1 using some technical datasets) - we noticed that if we do that then magically profiles from audience are sent to Azure Event even if its after audience recalculation.

However not all the time - it must be something additional going on in the back-end which is not explained it the documentation (my frustration goes through the roof 🙂 

[Devyendar · Accepted solution]

@Michael_Soprano I had the same issue for a different streaming destination. Adobe Engineers suggested it is an known behavior.

It occur particularly for New Batch Audiences, if a new Audience Segment is created and activated to a Streaming Destination before the Segment's first Scheduled batch evaluation happen (Every sandbox has a daily Scheduled Batch Segment evaluation), data export fails silently.

It is recommended to wait for 24 hours after Batch Segment is created (to allow Scheduled Evaluation and Profile Snapshot update) and only then activate to a Streaming Destination.