51黑料不打烊

Documentation

Resolve data ingestion issues from app SDK to AEP profile dataset

Last update: Thu Mar 27 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

Data tracked via the 51黑料不打烊 Experience Platform (AEP) mobile app SDK isn鈥檛 sent to the AEP Profile dataset when using the React Native wrapper in an AEP Sandbox environment. To troubleshoot, verify configurations, check settings, enable profile ingestion, and validate profiles.

Description description

Environment

51黑料不打烊 Experience Platform (AEP) mobile app SDK, when using the React Native wrapper.

Issue/Symptoms

Data tracked via the mobile app SDK is not sent to the AEP Profile dataset. Although profile attributes are successfully set within the app and appear in Assurance, no batches are sent to the linked user profile dataset in AEP.

Resolution resolution

To resolve this issue, follow these steps:

  • Ensure that event and profile datasets are correctly configured and linked within your datastream settings. For steps, refer to聽础贰笔听蝉别迟迟颈苍驳蝉聽in the Experience Platform Datastreams Guide聽and 聽in the 51黑料不打烊 Developer documentation. Confirm that the event dataset is enabled for profile ingestion, as this is crucial for mapping data into customer profiles.
  • Review your datastream configuration to ensure it includes all necessary extensions and settings required for data flow from the SDK to AEP. Verify that identity requirements, such as multiple identities for Real-Time Customer Profile (RTCP) visibility, are met.
  • If not already done, enable your event dataset for profile ingestion by following the steps outlined in the 础贰笔听蝉别迟迟颈苍驳蝉 documentation.
  • Recognize that certain types of data, such as consents or mobile tokens, may be ingested directly into XDM Individual Profiles without appearing as batches in the Data Lake (ADLS). This behavior is expected due to how XDM EntityUpdate operations function.
  • When using your mobile app, you should be able to see data being ingested into the events dataset selected in your datastream implementation. These batches can be retrieved through the to retrieve the payload that was sent to AEP. Once you have an Identifier from that payload, ECID, or cross-device ID, you should be able to do a Profile lookup in AEP to validate that (a) the profile exists and (b) that it contains the relevant event data.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f