Summary data in Segment Builder varies in Production and Development in AEP
Summary data in Segment Builder displays different behaviors in production and development environments in Adobe Experience Platform. This article explains the issue in detail and provides steps to resolve it.
Description
Environment
Adobe Experience Platform (AEP)
Issue/Symptoms
In Adobe Experience Platform, Segment Builder may display an error when retrieving information about specific attributes.
- Typical error: Summary data is not available for this field due to behaviors.
- When testing, you may see different behavior depending on the sandbox you are using.
- In a production environment, the Audience Builder UI will likely display a list of values in the summary data, whereas in a development sandbox, no list appears under similar conditions.
Resolution
-
The observed behavior is attributed to a backend process known as the Summaries job. This job analyzes previously ingested data to determine statistically relevant values for display.
-
Key points regarding this behavior include:
- The Summaries job functions effectively when there are enough unique values or frequent clusters within datasets.
- In production, due to a significantly larger dataset size compared to development, distinct clusters may be easily identifiable by the Summaries job. Hence, a dropdown list appears.
- In contrast, with smaller datasets in development, the lack of values may affect dropdown (summary data) visibility.
-
If, however, you have the same data in both production and development, please engage the support teams via a support ticket so the sample job is refreshed on the sandbox where you experience the issue.
-
This adjustment ensures that summary data displays consistently across both environments for the same attributes.
Additional Information
-
By opening the browser’s Developer Tools and refreshing the page, you may be able to retrieve the
lastSampledTimestampfor the sandbox. Simply look for apreviewsamplestatuscall to get this information, as illustrated in the attached screenshot.
-
The sample job should run at least once every 7 days. If that is not the case, please contact support for a refresh.