Hi @Tof_Jossic , Yes, the records for these 78 profiles were successfully ingested after 2025-11-01 via dataflow_01 (no issues reported). Since that date, we have full confidence in the data ingested through dataflow_01 into dataset_01. I mentioned previously ingested because today we are facing iss...

Screenshot attached.

Hi all, We are encountering issues when ingesting a batch file for the Individual Profile class. The error message displayed is:"Record size exceeded the limit". Out of approximately 4.8M records, 7,450 records failed (~0.15%). According to Adobe documentation, the maximum size of a record class is ...

Hi everyone, I'm facing an issue in Customer Journey Analytics (CJA) where the same anonymous user (ECID) is being associated with multiple ECIDs across sessions (multiple Person IDs) — even when using the same browser and device. Here's my configuration:"Identity Map" data element type defined by A...

Hi @Josh__Stephens , yes, the backfill had finished.  Ultimately, we resolved the issue by removing the dataset from the connection, reingesting it again, and initiating a new backfill. It turned out the solution was not as straightforward as the documentation suggested. Thanks for your help!

Hi @Josh__Stephens , We have multiple datasets in the connection. However, we only have Email as Person ID in one of them. After changing the Person ID for this dataset, we are not seeing Emails as Person IDs anymore in the new data. Nevertheless, historical data is still showing Emails as Person ID...

Hi @Josh__Stephens , No, we did not remover the existing dataset before bringing in the new backfill. Is this a requirement for this action? Thanks!

Hi there, We have a connection built in CJA with some datasets linked to it: Dataset 1 - Person ID: identityMap<primary>Dataset 2 - Person ID: identityMap<ECID> With this configuration, we found out we are breaking sessions in dataset 1 when users log in and Email is considered as Primary ID. In ord...

Hi @mmarti , Yes, event_id is a random value generated based on sha256(userId+timestamp). Hope this helps,Jose

Hi @John_Man , Let's see if I have understood it correctly: Final Output - MergeValue 1: Device Type - Rule 1 (Lookup). This assigns a Device Type value based on "Type identifier", a Lookup ID coming from device.typeid via AA source connector. Value 2: Type. This is the device.type field coming from...