254 results found

1. IQI Report - App Insights as the Source of Truth

   There are multiple similar functions happening that are similar within Optimizely. They all need to be utilizing the same data a the singular source of truth. They are:

   1. Incident Management, primary data is App Insights.

   2. Deep diagnostics done by Problem Management, primary data is App Insights

   3. App Insights Dashboard

   4. IQI Health Check reporting, primary information (aside from pingdom's availability info which for legal reasons) is Cloud Flare for health information.

   The inconsistency of source data causes issues because we cannot make a consistent presentation of the information when the source being utilized is entirely different.

   It also adds possibility of deviation of information because CloudFlare adds network hops and the possibility of transforming HTTP Status Codes, etc. So, the information can be altered in an unproductive way.

   If we want to add CloudFlare reporting, we should add targeted CloudFlare specific reports to the IQI report. These should identify discrepancies within the CloudFlare environment that are frequently done as differentials between App Insights and CloudFlare - such as delays in response from CloudFlare that are not caused by backend systems.

   There are multiple similar functions happening that are similar within Optimizely. They all need to be utilizing the same data a the singular source of truth. They are:

   1. Incident Management, primary data is App Insights.

   2. Deep diagnostics done by Problem Management, primary data is App Insights

   3. App Insights Dashboard

   4. IQI Health Check reporting, primary information (aside from pingdom's availability info which for legal reasons) is Cloud Flare for health information.

   The inconsistency of source data causes issues because we cannot make a consistent presentation of the information when the source being utilized is entirely different.

   It also adds possibility of… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  1 comment  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Fix NuGet Search UI on world.optimizely.com

   Many deficits exist within the NuGet portion of world.optimizely.com.

   An effort should be made to rectify the UX experience within the site to:

   1. Make it more user friendly.

   2.) Make it so that our NuGet search functionality works appropriately within production.

   For example, you should be able to filter the UI not just by the package name, but the DLL. See - https://docs.developers.optimizely.com/content-management-system/docs/nuget-package-families-in-cms

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Identify and Aid Customers with Production Live-Locks

   There's the concept of a "dead" lock and a "live" lock. A live-lock is essentially a race condition within a production environment. It causes stair stepping of CPU usually until the server crashes.

   This often happens when a developer accidentally uses a non-thread safe object in a multi-threaded manner.

   The object (for example a HashSet) being used needs to be identified and a thread safe type needs to be replaced so that the live-lock goes away and the CPU goes back to normal.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Down-Sampling Service Bus App Insights

   Much of the log analytics costs come from voluminous amounts of service bus activity that is largely useless for analytics purposes. We could generally use a fraction of the analytics and we would be just fine.

   For diagnostic purposes, we generally need to inspect the contents of the service bus itself to identify problems.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Consider shifting from Adaptive Sampling to Fixed Sampling

   There's a known bug in Adaptive Sampling that prevents us from getting accurate analytics from App Insights. It largely calls the values of App Insights largely into question because we cannot tell when the metrics within App Insights are accurate or not.

   Moving from Adaptive Sampling to Fixed Rate Sampling resolves this issue, but it also can cause an increase in log analytics and the possibility of exceeding the log quota.

   If we can come up with a weekly way to determine the appropriate sampling rate for a given type of log data for a customer and tweak the analytics fixed sampling rate on a weekly basis, that would be preferable. That combines the best of both worlds.

   https://www.google.com/search?q=known+microsoft+issue+in+app+insights+adaptive+sampling+values&rlz=1C1CHBF_enUS1003US1003&oq=known+microsoft+issue+in+app+insights+adaptive+sampling+values&gs_lcrp=EgZjaHJvbWUyBggAEEUYOdIBCTEyMDM5ajBqN6gCALACAA&sourceid=chrome&ie=UTF-8

   There's a known bug in Adaptive Sampling that prevents us from getting accurate analytics from App Insights. It largely calls the values of App Insights largely into question because we cannot tell when the metrics within App Insights are accurate or not.

   Moving from Adaptive Sampling to Fixed Rate Sampling resolves this issue, but it also can cause an increase in log analytics and the possibility of exceeding the log quota.

   If we can come up with a weekly way to determine the appropriate sampling rate for a given type of log data for a customer and tweak the analytics… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Identify and Communicate Crashing Instance Causes by Exception/Log Inspection

   Due to my elevated level of access nobody on the team gets these errors emails from Microsoft except Erik.

   We need an easy way to address these with customers through the ticketing system.

   These are causing instances crashes for the sites. Here's an example of what's happening on moco.

   Here are the email threads I'm receiving from Microsoft that shows they're having outages.

   •  

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Visible in menu should be available in Graph

   In CMS 13 the VisibleInMenu PageData property is not indexed.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Graph  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminCiara Bergin (Principal Product Manager, Optimizely) responded

   We’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!

8. Expose categories in Graph

   Categories are part of CMS 13 but they're not supported by Graph yet. We use them for filtering content.

   8 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Graph  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminCiara Bergin (Principal Product Manager, Optimizely) responded

   We’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!

9. Editor Content Health Dashboard : A personalized, self-service governance view for every content editor in the CMS

   As a content editor, I want to see a personalized dashboard when I log in to the CMS that shows me only the content I own that needs attention, so that I can find and fix issues myself, without waiting for someone else to tell me about them.

   This dashboard replaces the generic default view in the CMS for all content editors. It does not replace any existing admin tools or reports. The intent is to move content governance from a reactive, admin-led activity into a proactive, editor-led habit. The dashboard is the trigger for that behavioural shift. This is a single story that covers the concept and requirements. If the team needs to break it into smaller stories per dashboard section for sprint planning, that is a valid approach, but the sections should be built as one coherent interface, not as separate standalone tools.

   The problem we are solving
   Today, the CMS shows every editor the same generic dashboard. It is not personalized, it does not show issues specific to that editor's content, and it gives no signal about whether the content they own is healthy or broken. The result is that content problems, broken links, outdated pages, unused media, unpublished drafts, go unnoticed for months or even years, until an admin, a customer complaint, or a site audit surfaces them. By that point the damage is already done.
   With over 100 editors across our sites, we cannot rely on a central team or a CMS administrator to track and chase every editor about their content. That model does not scale. Governance needs to become a personal responsibility and for that to happen, editors need to be able to see their own issues at a glance the moment they log in.

   Who this is for
   This dashboard is for every person who creates, edits, or publishes content in the CMS. That includes marketing editors, regional content managers, product page owners, and campaign managers. It is not a tool for administrators - it is a tool that makes every individual editor their own first line of quality control.

   What the editor needs to see
   When an editor logs in, their dashboard should surface the content they personally created or own. (as per editor access rights applicable)

   Broken and 404 pages
   1. Pages I created that are currently returning a 404 error or are broken
   2. Pages that have an incorrect redirect set up
   3. Any pages I own that have no live URL and no redirect in place
   4. Direct links to each page so I can go in and fix it immediately

   Outdated content
   1. Pages I own that have not been reviewed or updated in a defined period of time
   2. A clear signal of how long it has been since the last update
   3. The ability to mark a page as reviewed without making edits, if the content is still current

   Unused images and media
   1. Images and files I uploaded that are not currently used on any page
   2. The file name, upload date, and file size so I can make an informed decision
   3. A way to archive or delete unused files directly from the dashboard

   Unpublished drafts
   1. Pages I have started but never published
   2. The last date I saved the draft, so I can identify ones that have been forgotten
   3. A direct link to open the draft and either publish it or discard it

   Expiring and review-due content
   1. Pages where a review date or expiry date is approaching in the next 30 days
   2. Pages where no review date has been set at all, flagged as a governance gap
   3. The ability to extend a review date or set one if it is missing

   Rule-Based Automation Layer (if possible)
   Defined rules such as:
   1. Draft older than 90 days → archive or notify owner
   2. Redirect chains > 2 hops → auto-flag for cleanup
   3. 404 URLs with traffic → auto-suggest redirect
   4. Orphan pages (no inbound links) → flag or archive

   What the editor does not need to see
   The dashboard should not show content owned by other editors (exception for admins, site managers & super users). It should not show global site statistics. It should not require the editor to filter, search, or configure anything to get to their personal view. When they log in, their issues are the first thing they see.

   Why this is a single solution, not multiple tools
   We considered building separate reports for each of these issues. We decided against it. Separate reports mean editors have to remember to check multiple places. Most will not. A single dashboard that loads at login means the information finds the editor, the editor does not have to go looking for it. This also means one build, one place to maintain, and one consistent experience for all 100+ editors regardless of which site or market they work in.

   Attached are vizualisation ideas- not anything we have as of today.

   As a content editor, I want to see a personalized dashboard when I log in to the CMS that shows me only the content I own that needs attention, so that I can find and fix issues myself, without waiting for someone else to tell me about them.

   This dashboard replaces the generic default view in the CMS for all content editors. It does not replace any existing admin tools or reports. The intent is to move content governance from a reactive, admin-led activity into a proactive, editor-led habit. The dashboard is the trigger for that behavioural shift. This is… more

   •  

   •  

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Reports  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. select content

    As a content editor,
    I want to search for existing blocks within the “Select Content” shortcut window, so that I can quickly find and reuse the required content without manually browsing through multiple options.

    Background / Problem Statement:

    Currently, when creating a new block in Optimizely CMS, users are presented with two options:
    Create a new block
    Select content

    When selecting “Select Content”, a shortcut window opens displaying available blocks. However, this window lacks a search functionality, making it difficult and time-consuming to locate specific content, especially when the number of blocks is large.

    Navigation Path:

    Main Content → Select Content button →Select content → Shortcut window opens displaying available blocks

    Reason for change

    The current “Select Content” shortcut window in Optimizely CMS does not provide a search capability, which creates significant usability and efficiency challenges for content editors.

    Inefficient Content Discovery:
    Editors must manually scroll through a long list of blocks, which is time-consuming and error-prone, especially as the content repository grows.

    Poor User Experience:
    Lack of search increases friction in the content creation workflow, leading to frustration and reduced productivity.

    Reduced Content Reusability:
    Difficulty in locating existing blocks discourages reuse, resulting in duplicate content creation and inconsistency across pages.

    Scalability Limitation:
    As more blocks are added over time, the current approach does not scale and will further degrade usability.

    Business value
    Reduces time spent searching for reusable blocks
    Improves content editor efficiency and workflow
    Encourages reuse of existing content (supports consistency and governance)
    Enhances overall CMS usability

    As a content editor,
    I want to search for existing blocks within the “Select Content” shortcut window, so that I can quickly find and reuse the required content without manually browsing through multiple options.

    Background / Problem Statement:

    Currently, when creating a new block in Optimizely CMS, users are presented with two options:
    Create a new block
    Select content

    When selecting “Select Content”, a shortcut window opens displaying available blocks. However, this window lacks a search functionality, making it difficult and time-consuming to locate specific content, especially when the number of blocks is large.

    Navigation Path:

    Main Content → Select… more

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  1 comment  ·  Editing (Content)  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. IP Address restriction in Cloudflare

    It would be great if we could configure an IP Address whitelist in Cloudflare so that we only allow a specific set of source IP Addresses to be allowed to access our DXP instances. This will allow us to block public access to non-production environments

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. When there are errors on the servicebus we don't log it. It would help if we logged errors for troubleshooting purposes.

    When there are issues with the servicebus it is not possible to see what went wrong many times. You can go to the servicebus and look at the graph and see that there are "server errors" and "user errors" and "throttled messages"but there is no way to see the details of the server errors or the user errors.
    Some times we can see a log entry in the CMS logs but not always and I guess it depends on the type of error.
    If we had more information it would help when troubleshooting customers having problems with the servicebus.

    22 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Gathering Feedback  ·  2 comments  ·  DXP, Hosting & Infrastructure  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Configure Salesforce MA Connector to Omit Certain Object Types

    The Salesforce Marketing Connector tries to fetch fields for Account, Campaign, Contact, Lead and Case.
    When one or more of these are not enabled in SF, this leads to a flood of logs/errors from the 'Fetch Data From Marketing Connectors' job.
    Can you please expose a configuration that allows us to specify which object types should be fetched?

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Integration / APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Difficulty locating the "Automatic published media on upload" setting in CMS 12

    Location of Settings in CMS 12: Difficulty locating the "Automatic published media on upload" setting in CMS 12, which affects workflow and publishing behavior.

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Editing (Content)  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Media Publishing Confusion

    Media Publishing Confusion: Contributors often forget to publish or submit new/updated media (e.g., PDFs, images) for review, as the system does not prompt them, resulting in drafts being left unapproved. 

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Editing (Content)  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Versioning Limitations: Updates to blocks (even within a page) do not trigger version updates or review requirements for the parent pgge, ma

    Page‑level updates are not reflected in version history:
    When a block on a page is updated, the page‑level version history does not show the recent change. Instead, version history is tracked only at the block level, not for the page as a whole. As a result, it can appear that a page has not been updated even when changes have been made.

    For example the Child Health Policy Accelerator | SickKids page was updated couple of days ago, but the last update details are showing of October 2025.

    •  

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Editing (Content)  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Reviewers lack visibility into where blocks and media objects are used across the site, leading to time-consuming searc

    Reviewers lack visibility into where blocks and media objects are used across the site, unless someone published the landing page/parent block where the block is supposed to be placed. This lead to time-consuming searches and uncertainty during approval.

    •  

    •  

    8 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Editing (Content)  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. add button ID property

    Analytics requires us to differentiate between different CTA buttons on a page that may go to the same destination (e.g. event "register today"). Please ad a button-ID property in the standard link interface (page, external link, media, remaining URL, etc.) We cannot use UTM-like properties as that breaks tracking within a current session. This is very standard in other CMSs.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Gathering Feedback  ·  0 comments  ·  Editing (Content)  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. send alerts when sync jobs fail

    We want alerts to be sent via email and or our incident io pager system when sync jobs fail. Now, we have to look in every job's history to see if any sync jobs fail.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Graph  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminCiara Bergin (Principal Product Manager, Optimizely) responded

    We’re currently gathering additional feedback on this idea. If you have any more context, examples, or specific use cases, please share them - it really helps us understand how this would best support your workflow. Thanks for contributing to the conversation!

20. Real-Time Audiences from ODP to CMS: respecting cookie consent for personalization

    Real-time audiences can be synced from ODP to CMS via a NuGet package (https://docs.developers.optimizely.com/optimizely-data-platform/docs/odp-cms). This enables audiences created in ODP to become selectable in the CMS's Audiences setting.

    The CMS's Audiences setting doesn't take account of cookie consent configurations at all, however. This creates a problem for configuring personalization in the CMS with synced ODP audiences.

    ODP audiences may opt out of personalization in their cookie consent preferences. But if personalization is configured in the CMS, the personalized view will still display for those who have opted out.

    (This is not an issue with Web Experimentation, as Web Experimentation does respect cookie consent preferences. ODP audiences synced to Web Experimentation will have their preferences honored.)

    It would be great if the CMS can also respect cookie consent preferences for real-time audiences synced from ODP.

    Real-time audiences can be synced from ODP to CMS via a NuGet package (https://docs.developers.optimizely.com/optimizely-data-platform/docs/odp-cms). This enables audiences created in ODP to become selectable in the CMS's Audiences setting.

    The CMS's Audiences setting doesn't take account of cookie consent configurations at all, however. This creates a problem for configuring personalization in the CMS with synced ODP audiences.

    ODP audiences may opt out of personalization in their cookie consent preferences. But if personalization is configured in the CMS, the personalized view will still display for those who have opted out.

    (This is not an issue with Web Experimentation, as Web… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Gathering Feedback  ·  0 comments  ·  Personalization  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating