I got the case like this:
1. I got some processes using DQ based on dataset XY1 - not enabled for profile
2. It writes data to Dataset XY2- hourly. Enabled for profile
It would be max 100-1000 records every time
3. Streaming audiences would use data based on data from XY2
Would it work?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
If you were to create nested audience for the streaming qualification it may work, but the query service results will be evaluated in batch.
When you use Query Service to create a dataset (for example, with a CREATE TABLE AS SELECT or similar operation) and that dataset is profile-enabled, the resulting data is still written and processed as a batch ingestion job in Adobe Experience Platform
If you were to create nested audience for the streaming qualification it may work, but the query service results will be evaluated in batch.
It's not going to work for much longer Michael.
There are changes coming to streaming segmentation where intra-day batch data loaded into profile won't be read by streaming segmentation. So I wouldn't plan on using hourly queries as there's nothing that's going to use that data. Plus those 24 batches per day count against the 90 batches per sandbox per day profile ingestion limit.
Views
Replies
Total Likes
Views
Likes
Replies