Some AEP customers had requested that Adobe enable a "penalty box" mitigation feature to prevent merged profiles from being used for activation. These were most typically profiles merged due to shared device identities. This must have been done in your IMS Org at some point, as that error message co...

Just for clarity, if your reason for wanting to delete people data isn't due to an explicit request by the end consumer, the license terms for the Privacy API prohibits its use for this. The only two allowed options purging obsolete people data are using the Data Lifecycle Record Delete feature or d...

Opinions differ of course, but I personally would never generate any kind of random identity. Instead I've always used deterministic methods, such as concatenating other fields from the SELECT row result to construct a unique identity from that. (This also means being sure to use DISTINCT or similar...

This version is superior: AND timestamp >= DATE_TRUNC('month', DATE_ADD(CURRENT_DATE, -DAY(CURRENT_DATE))) AND timestamp < DATE_TRUNC('month', CURRENT_DATE) as it allows the queries to run more efficiently using the physical partitioning inherent in how timeseries-based datasets are stored on dis...

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

Generally speaking, it's better to ensure that all of your files have the same format, and only source a dataset from one folder in your cloud storage location.Different datasets should be sourced from different folders, but each folder should be homogenous in terms of its contents.Then whenever you...

Identities must be unique to a single profile. When you have Field1 and Field2, together do they always uniquely identity a single profile? (I assume that they do. If so then you should concatenate them into a single field marked as an identity either upstream of AEP or during the Data Prep phase of...

How will you prevent your arrays and the resulting profile records from growing too large? There are multiple limits applicable here: https://experienceleague.adobe.com/en/docs/experience-platform/profile/guardrails#data-model-limits Would you be better served with custom aggregates instead, e.g. fi...

Looking at the original image, it appears that your processing throughput increased on September 13th and since then has been nearly matching your actual ingestion rate? If true and that's still not sufficient bandwidth then I'd explore this method of reducing ingestion into Profile Service:https://...

I typically combine into one dataset when:the data is of the same class: profile, event, or customthe data will have the same primary identitythe data is sourced from the same systemthe data will be sourced the same way: streaming vs batch If you combine profile-class data into one dataset when all ...