Merge policies in Real-Time Customer Profile define how data from different datasets is combined to create the unified profile view. If a dataset is not included in the merge policy being used to view the profile, its data will be excluded from the final unified profile, even if it has been successfully ingested. In this scenario, the most likely reason the mobile and location data are missing is that the datasets containing these fragments were not added to the specific merge policy being used for inspection.

B. Real-Time Customer Profile is designed to unify fragments that arrive at different times; simultaneous loading is not a requirement for successful merging.

C. The order of fragment ingestion does not typically cause data to be entirely missing. Merge policies use rules like timestamps to resolve conflicts, not to exclude data based on load order.

D. This is factually incorrect. Real-Time Customer Profile fully supports standard data types, including mobile phone numbers and location information.

1. Adobe Experience Platform Documentation. (2023). Merge policies overview. Adobe Experience League. The documentation states, "Merge policies are rules that Platform uses to determine how data from multiple sources will be prioritized and combined to create a unified profile."

2. Adobe Experience Platform Documentation. (2023). Real-Time Customer Profile Guide. Adobe Experience League. In the section "Working with merge policies," it explains that you can create multiple merge policies and that each policy can include a different combination of datasets.