@shamir_duran Let us know if the solution above worked for you! If it helped, marking the response as correct can guide others with the same question. And if you found a differentsolution, please share it — your experience could be valuable to the community.  

I will recommend to check below steps to troubleshoot offline and online data issues in CJA:Check identity stitching – use a common ID (e.g., ECID or CRM ID).Validate schema and mapping – ensure correct XDM structure and field mapping.Review timestamps – make sure they’re accurate and in ISO format....

You cannot create a single CJA connection across multiple AEP sandboxes — each connection is limited to one sandbox.If you have a unified, merged view in CJA, your best option is to:- Design a unified schema, including sandbox/geography identifiers.- Automate data movement from each sandbox to a thi...

You can send the enriched data to an AEP dataset by using the Streaming Ingestion API from Event Forwarding.- Combine arc.event.xdm and apiResponse into one payload.- POST to AEP with required headers (x-api-key, x-dataset-id, etc.).- Ensure payload matches the dataset's schema.Once in the dataset, ...

Best Practices for Ensuring Data Consistency Compare key summary metrics (Visits, Unique Visitors, Page Views, Revenue, etc.) for the same time range and segments. This helps identify broader issues before diving into specifics. Ensure both AA and CJA are using the same time zone and date ranges. Th...

Identity type limited to 20" means you can have at most 20 distinct identity namespaces/types. You can have many records/values per type, but only 20 different types/namespaces. Yes, the methods I suggested (identity cleanup, ECID validation, etc.) are all pre-ingestion solutions — meaning they need...

Both MaxIdentities and InvalidXdm errors are common in batch ingestion pipelines in AEP.To fix MaxIdentities Error:Limit identity types to 20 or fewer per record.Remove unused or duplicate identity namespaces.Add pre-ingestion validation to filter or truncate excess identities.To fix InvalidXdm (Inv...

@Gav_R  Add a Separate Processing Rule for iOSIF platform (context data) equals "ios"THEN set eVarX to "ios"Processing rules are case-sensitive — make sure the value from the iOS app is exactly "ios" (not "iOS" or "IOS").Let me know if this works.

You can Update the rule to include a second condition:If platform equals "ios" → set eVarX = "ios"Debugging Tips:Use Adobe Experience Platform Debugger to verify if the platform context data is being sent correctly.Use Charles Proxy to inspect the beacon data on mobile.Temporarily map platform direc...

Helpfull, Thank you for sharing.