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-hour log for additional implementation status details.
Read more about the Implementation Status.
Manage Languages
If you have a multilingual site, you can manage the translation of variations inside the variations. Meaning, you can enter different values for template variables for different languages - and the appropriate value will be served to the user. Read more about Multilingual Campaigns.
Primary Metrics
Choose the metrics that will appear at the top of the dashboard and audience reports. Learn more about customizing your dashboard and audience report metrics.
Active Cookie Consent
Active Cookie Consent mode allows you to not serve personalized content or track users that that did not give their consent for that. Read more about Active Cookie Consent.
Custom Domain
By default, Dynamic Links and Landing Pages are served from link.dyo.io domain, 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.
Product Data API
Enable the client-side API of Product Data. Read more about the Social-Proof API.
Daily Activity Stream
Export raw data of events and pageviews. Once turned on, a daily export of raw data will be added to an S3 bucket, allowing your BI team to connect to and use it in their analysys. Read more about the Daily Activity Stream.
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 the audience and targeting conditions.
For example, let’s say you want to target example.com/product=123. Your CMS has 2 URLs that render 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.