The Alerts tab on your Experience OS dashboard displays all app alerts in one centralized place, making it easier to implement and monitor your Experience OS apps.
You can also choose to receive email notifications for alerts by clicking Manage Email Alerts.
Each alert includes the affected area or app, a severity level (indicated by color and icon), a description of the issue, suggested actions, and links to detailed logs. This article provides an overview of the most common alert types, including common causes and how to resolve them.
Understanding your alerts
Dynamic Yield continuously monitors your implementation to help you catch and resolve issues early. The following are different types of implementation alerts you might receive—what they mean, their common causes, and how to fix the issues.
No pageviews reported
What it means:
No pageviews have been detected for your site in recent traffic logs.
Common causes:
This usually results from one of the following:
- Page context or pageview tracking wasn't implemented on your site.
- Context or pageview tracking was implemented, but stopped working because of code changes or network issues.
To resolve:
- Script-based implementations: Ensure all page context requirements are met. See the Page Context developer documentation for details.
- API-based implementations: Verify that both page context and API request requirements are properly implemented. See the pageview reporting documentation for details.
Page context errors detected
What it means:
Your site is reporting page context, but some required parameters are invalid or missing.
Common causes:
Each page context type has different required parameters, so you'll need to determine the cause per context. For example, on a product page, the issue might be that:
- The viewed product SKU is missing.
- The price value is not in a valid numeric format.
To resolve:
- Click Download Log to inspect specific errors.
- Ensure that all required parameters are included in your code. See the page context documentation for details.
Errors in reported events
What it means:
One or more events (Purchase, Add to Cart) were reported without all the required parameters.
Common causes:
For example, a Purchase event might be missing the SKU or price of the purchased item in the data object.
To resolve:
- Click Download Log to identify which events failed and why.
- Review the required event schema and examples in the events implementation documentation.
- Update your code to include all mandatory fields.
Experience API errors
What it means:
One or more of your Experience API requests (such as choose or track engagement) returned errors due to invalid or missing values.
Common causes:
An API request might send a parameter in the wrong format. For example, passing a sessionId as an integer instead of a string.
To resolve:
- Click View Issues or View API Logs to see which API requests failed.
- Review payload requirements in the API reference.
- Update your integration accordingly. Learn more about working with Experience APIs.
Product feed sync failed
What it means:
Dynamic Yield was unable to successfully sync your product feed file. This can result in missing or outdated product data on your site.
Common causes:
- Missing mandatory columns: The feed is missing required fields such as sku, categories, image_url, in_stock, price, name, or group_id.
- Too many warnings: The feed includes too many entries with missing or invalid values in required fields, making the data unreliable.
- Unsupported or invalid file format: The source file format (CSV, JSON, XML) may be incorrectly structured or improperly formatted.
- Invalid source or access issues: The feed is hosted on a private or restricted server, preventing Dynamic Yield from accessing it.
To resolve:
- Open the alert in the Alerts Dashboard.
- Click Download Log to identify the specific issues.
User Data feed hasn't synced recently
What it means:
The User Data feed hasn’t been updated in a while and is likely outdated, which could lead to inaccurate audience data.
Common causes:
- No recent file uploads to your dedicated AWS S3 bucket
- Changes or interruptions in your automatic upload process
To resolve:
See our Developer Docs for instructions on uploading a valid User Data file with the correct access credentials, and validating the upload.
User Data feed not synced since last failed attempt
What it means:
The last sync of the User Data feed failed and the feed hasn’t been successfully updated since the failed attempt.
Common causes:
- The last User Data file contained too many errors for a successful sync
- You haven’t uploaded a valid file to your dedicated AWS S3 bucket in a while
To resolve:
See our Developer Docs for instructions on uploading a valid User Data file with the correct access credentials, and validating the upload.
Subscribing to email notifications about alerts
Click Manage Email Alerts to get email notifications about issues that are important to you.
You’ll receive email notifications at the following intervals:
- First Notification: Sent within 24 hours of when the issue is first detected.
-
Reminder Notifications: Sent every 7 days while the issue remains unresolved.
Exception: Product feed alerts are sent every morning until the issue is resolved.