The only relevant merge policies when defining audiences are the ones for "_xdm.context.profile". Of those, only one can be marked as the default.

If you look on the Datasets page for your dataset at the bottom you'll see Dataset Run IDs and their corresponding Batch IDs. For batch source connectors these are 1:1.

With additional enhancements to AEP and related apps there are fewer and fewer reasons to have multiple merge policies. From what I've seen, most combinations of use cases function perfectly fine with a single merge policy that is used for all segmentation and all integrations. Having unnecessary ad...

As mentioned above, streaming data is batched before it's written to the data lake. But it is ingested immediately into Profile and Identity Services, so there's not much reason to worry about the intervals between batches in the data lake. Nothing should be trying to read from those datasets in the...

My preference is to avoid zero length strings at all times. Otherwise this complications the logic required when testing in an audience. This is why best practice is to set a min=1 length on string fields even when optional. If you need to nullify one or fields then I'd recommend sending a complete ...

To send to event data to external storage, then look at Event Forwarding? https://experienceleague.adobe.com/en/docs/experience-platform/tags/event-forwarding/overview 

The data lake is considered part of AEP, and when you configure Data Collection for web SDK and mobile SDK datasources, that event data will flow into the data lake: https://experienceleague.adobe.com/en/docs/experience-platform/collection/home -Kevin

Ah, I might have missed something in my reply. For delimited source files, you should not have any special characters in the header line.  No dots, no spaces, no hyphens, ... nothing except alphanumeric and underscores. Plus that first character in the column name can't be an underscore, must be alp...

I've never needed to use any sort of json to object mapping functions when ingesting JSON formatted data into AEP. Instead I've been able to map individual source JSON fields to my destination schema fields, and also to map source JSON objects to my destination schema objects (when the structure is ...

Data Lifecyce Record Delete is the recommended way to remove unwanted data from AEP based on specific identity values: https://experienceleague.adobe.com/en/docs/experience-platform/data-lifecycle/home I've been using it for nearly 18 months so far... works great! (It used to be informally called "D...