Skip to content

Web Experimentation

Categories

JUMP TO ANOTHER FORUM

65 results found

  1. Dear Team,

    We would like to request the extension of the recently released properties functionality for custom events to include page-level implementation. This enhancement would significantly improve both targeting capabilities and metric definition for page-based analytics.

    Currently, when managing numerous product detail pages (PDPs) with varying attributes such as product categories, we face limitations in creating meaningful metrics. Whilst page attributes exist, they cannot be utilised within metric definitions.

    The ability to define page properties would enable us to create metrics such as "product category PDP visits" without requiring dedicated category pages or specific experimental targeting for each variant.

    This…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. As an experimenter, I should see a warning/alert when changing an Audience in either Web or FX that is being used in an active experiment to prevent unwanted impacts on live experiments.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Feedback from client: I want to be able to search for an old test on the results dashabord just once, rather than have to search for it within each status category.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. I create experiments for a major retailer, and current URL substring match capabilities force me to use JS conditions or callbacks for all campaigns on my PDPs and category pages. This is tedious and makes it difficult for non-technical teammates to run experiments.

    For example, many retailers use structures like retailer.com/p/ to indicate PDPs and retailer.com/c/ for category pages. However, using those in the substring match fields will include all substrings with a "p" or "c" since the backslashes are not accounted for, opening up the test for many, many more visitors than we would anticipate. For example, the visitor…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. I am working as analytics engineer in western union , we are having trouble to export the campaigns for our audit activity.

    We have 100s of running campaigns in our prod project and its not feasible for all our teams to use the API end points to list more than 200 campaigns and filter Running campaigns manually from the JSON.

    And our non tech team cannot do this activity and we don't have bandwidth to build application using the Optimizely api end point to get a UI for this.

    We used other AB & Personalization tool and has this basic…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. The ability to split tests based on geographical region so that we can test the effectiveness of region-specific marketing campaigns, two-sided marketplaces, or faciliate other testing use cases when we cannot guarantee a user will be in solely the control or test variant.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Currently Web Experimentation Audience Attributes only support values as string types. Adding support for number values (floats, integers) would allow for more complex and granular audience membership.

    Customer provided example: An audience for visitors who have less than 100 subscriptions. The Audience Attribute numSubscriptions would be a number value of the total number of subscriptions the visitor has. This attribute could be used to build an audience for all visitors with less than X (ex. 100) subscriptions.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. I am the Product Manager at Hearst Magazines.
    Our current Web Experimentation implementation is set up with the snippet in the <body> tag, which causes significant flicker for experiments involving changes above the fold.
    Your new Edge on CDN feature could be a game changer for us. However, the blocker is that we currently use Fastly CDN, which is not supported by your Edge product.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. State exactly why it was flagged; would likely require customer to input some data

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Its inconvenient navigating back and forth

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. The changes work when you are in the tool , but do not actually work in the wild. Something overwrites the code from the customer's website.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Customers try to load their website in the Visual Editor and it never finishes loading

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Customers attempt to use the visual editor to make persistent changes, but the changes do not persist throughout the entire user journey as the selector changes either on reload or if new DOM elements are present on different pages.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Once a test is concluded, export the changes as a set of code in HTML+CSS+JS, or React, etc. Has come up several times in the past month. Suggest investigating whether competitors do this.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Prospects that have had tests "break" their site want an automated solution for monitoring the quality of their test variations in production, and to be alerted immediately when there are issues that negatively impact UX.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. There are common WYSIWYG editor problems, based on site architecture or test type. Create self-service solutioning guides for customers to diagnose and solve problem.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Customers use the Chrome Plug-in often for debugging, QA and forcing themselves into variations. It does not always work, and is pretty limited.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    New  ·  2 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Give customers the ability to create own labels to attach to experiments, and make these columns you can add in the overview, as well as making it filterable and sortable. This feature would help create ownership of experiments

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Had a customer respond that it did not make sense that there were so many checkboxes for the GA4 Integration in the Experiment > Integrations tab. The GTM check should be checked by default or be part of a global/project setting instead of Experiment level.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. When building an optimization variation, Change HTML content is no longer a primary option within the Create Change menu. This is the primary template I use and I now have to do a lot of extra clicking as each time I have to select it from Browse Templates. If the ability to add favourite templates was added it would allow me to be a lot more time efficient with my builds.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?