The General Settings screen allows you to configure and review the technical implementations and integrations of your site or app. This screen changes based on the type of platform – Web or native app.
Implementation Status
An overview of the implementation of your script, page context, events, and product feed. You can also download a past 12-hours log for additional implementation status details. Page context, event and product feed status is only available for eCommerce sites.
The following table gives more details about the meanings of each status.
| Item | Status | Description / Threshold |
|---|---|---|
| Script | Not Implemented | No script detected |
| Implemented | The script is detected. This does not verify that the script is in the header. | |
| Page Context | Not detected | No page context information sent in the past 12 hours |
| Validated | There may be errors in up to: 2% of your product pages, 2% of your cart pages, or 5% of your category pages |
|
| Accepted with Warnings | There are errors in: 2-7% of your product pages, 2-7% of your cart pages, or 5-10% of your category pages |
|
| 1 error (The number of errors is the number of page context types that have passed the error threshold) | There are errors in more than: 7% of your product pages, 7% of your cart pages, or 10% of your category pages |
|
| Events | Not received | No events received in the past 12 hours |
| Validated | There may be errors in up to: 2% of your add to cart, sync cart, remove from cart, or purchase events, 20% of your login, subscribe, or signup events, or 50% of your filter, sort, change attribute, keyword, or video watch events |
|
| Accepted with Warnings | There are errors in 2-7% of your add to cart, sync cart, remove from cart, or purchase events | |
| 1 error (The number of errors is the number of event types that have passed the error threshold) | There are errors in more than: 7% of your add to cart, sync cart, remove from cart, or purchase events, 20% of your login, subscribe, or signup events, or 50% of your filter, sort, change attribute, keyword, or video watch events |
|
| Data Feeds | Not synced | You have not yet attempted to synchronize a data feed. |
| Synced | You have successfully synchronized a data feed. | |
| Synced with Warnings | The data feed synchronized, but some individual rows were not synchronized due to errors such as missing data. Download the log for more details. | |
| Failed to sync | The data feed did not synchronized due to an error. Download the log for more details. |
Note: The status of events and page context are updated once every ten minutes.
If you find the above thresholds are too sensitive, or not sensitive enough for your site, contact our Support team to configure adjustments.
Note: After resolving an issue, it may take some time until the error or warning status is changed. This is because the thresholds are calculated based on the combined data from the past 12 hours. You can verify that an issue has been successfully resolved by watching the percentage of errors in the logs gradually decreasing over time.
Logs for Events and Page Context
Overall percentages of invalid items are presented, as well as a sample of unique invalid items organized per type. It is not a fully comprehensive log with details about each event, row, and pageview.
For example, the events log below displays a section for each type of event that was triggered, what percentage of the events were invalid, and a sampling of the invalid events with their errors.
Logs for Data Feeds
Data feed logs differ depending on whether the feed was synchronized or not. If the feed was synchronized with warnings, the log contains the list of individual rows that were not synchronized and some details. If the feed was not synchronized at all due to an error, the log only contains the error details.
| Error Message | Description |
|---|---|
| Internal error | Failed to synchronize the feed due to an unexpected error. Open a support ticket. |
| Too many warnings | Failed to synchronize the feed because more than 90% of the rows in the feed were invalid. |
| Javascript error | Failed to synchronize the feed because the parser function did not return a valid feed. |
| Invalid headers | Failed to synchronize the feed because a required column was missing. |
| Timeout | Failed to synchronize the feed because there was no response from the URL for 5 minutes. |
| Invalid Format | Failed to synchronize the feed because the feed file was not a valid CSV, JSON, or XML file. |
| URL not found | Failed to synchronize the feed because the URL was not found or an error occurred when trying to download from the URL. |
| File size exceeded | Failed to synchronize the feed because it has exceeded the size limit for your account. Open a support ticket to determine if your feed size limit can be enlarged. |
Custom Domain
By default, Dynamic Links are served from link.dyo.io domain and Landing Pages, but you can serve them with your own domain. Read more about custom domain integration.
IP Filter
Filter internal IP addresses from reports. Useful if you have a lot of internal traffic you don't want to affect experience results. Read more about IP filters.
URL Normalization
Every page has a standard URL that is displayed in the user's browser (page URL), but some sites also define a canonical or open graph URL in the code of each page. The URL normalization setting determines which URL to use for audience and targeting conditions.
For example, let’s say you want to target example.com/product=123. Your CMS has 2 URLs that renders this product page: example.com/product=123 and example.com/product=blue-suede-shoes. Both pages have defined the same canonical URL: example.com/product=123.
If URL normalization is set to use the page URL - these are viewed as 2 different pages and must each be targeted individually because their page URLs are different. If you normalize the URLs by the canonical URL, you can just target them together by specifying the canonical URL.
If you select canonical or open graph URL and one is not defined for the page, Dynamic Yield uses one of the other URLs as specified in the fallback descriptions of each option.