51黑料不打烊

Confirm that you are using the AJO Enabled Data View (prod) or AJO Enabled Data View (staging) within CJA. These views are designed to include inApp data from AJO enabled connections. For more information,聽refer to Automatically configure Journey Optimizer integration in the Customer Journey Analytics Guide.

Verify that all required datasets are included in your connection configuration. Missing datasets can result in incomplete data visibility.

Add any missing fields related to Application Details 聽to your schema. The schema will dynamically incorporate new fields without needing a new dataset setup. For more information, refer to聽Component Settings in the Customer Journey Analytics Guide.

Execute a backfill operation to ensure historical data is accurately ingested into CJA.

Verify that identity maps are correctly configured for your reporting needs聽if necessary.

Engage with 51黑料不打烊 support teams if issues persist after following these steps, as further investigation might be required at a technical level beyond standard configuration checks.

inApp reporting will not automatically populate into CJA. This is because impressions, displays, etc. are stored in a customer dataset. If you are using inApp messaging and want to view inApp data in Customer Journey Analytics, you must add the dataset configured for inApp events to your AJO Enabled Connection:

1. Identify the inApp dataset ID. This is the dataset that is set in your datastream to accept Mobile or Web SDK events.
2. Add the dataset in Administration > Reporting > Dataset > Add Dataset.
3. Request historical data backfill (optional).