In Settings › General Settings, you can configure and review the technical implementations and integrations of your website or app. This screen changes based on the type of platform you defined for your section – website or mobile (native app).
Edit section settings
Click the edit (pencil) icon next to your section name to edit these settings, including the section name, URL, CUID type, and localization settings.
Implementation status
This area provides an overview of the implementation of your script, page context, events, and product feed. For additional implementation status details, you can download a past 12-hour log.
Read more about the Implementation Status.
Manage languages
If you have a multi-language website, 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 is served to the user. Read more about multi-language campaigns.
Primary metrics
Select the metrics that appear at the top of the dashboard and audience reports. Learn more about customizing your dashboard and audience report metrics.
User identifier types
You must define a customer unique identifier (CUID) for every Dynamic Yield section. The CUID is used as the primary identifier type by which users are identified across their devices (see Matching Users Across Channels). The CUID is used to merge activity and data from across all devices that are associated with that CUID so that users always find themselves in the right audience and with the right affinity profile, regardless of the device they're using.
While only one CUID type can be defined for the section (the default is email address), Dynamic Yield supports assigning additional identifier types as secondary identifiers. This is especially useful when you want to target users across various channels in Reconnect, using any ID in use across your marketing stack. Soon, secondary identifiers will also serve to import user data and export audience data.
Privacy and regulation
Active Cookie Consent mode enables you not to serve personalized content or track users who did not give their consent. 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 on our Developers site.
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 Performance API
(Previously known as Product Data API)
Enable the client-side API of Product Data. Read more about the Product Performance API.
Daily activity stream
Export raw data related to events and pageviews. When turned on, a daily export of raw data is added to an S3 bucket, enabling your BI team to connect to it and use it in their analysis. Read more about the Daily Activity Stream.
URL normalization
Every page has a standard URL that's 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.