Skip to content

Web Experimentation

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

68 results found

  1. I am a UX Developer. I am trying to create a template within Google Tag Manager to make it easier for team members to push custom events to Optimizely Web Experimentation. Unfortunately due to GTM sandbox restricts, direct execution of methods on global objects like optimizely.push is not possible. There are a few possible ways to resolve this, which could include:

    1. Expose a queue-style global object
    2. Provide a GTM-friendly wrapper
    3. Publish an official GTM Custom Template
    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)
  2. Role: Onboarding Solution Architect

    Issue:
    For the Audience Condition Ad Campaign "When selecting Visitor does not come from, it is a common interpretation that anyone who comes to a page, except those from an ad campaign would be selected. But this is not true. Instead, the user must come from an ad campaign, just not the one you specify to be targeted. "

    Request:
    Change this audience condition to match the intuitive and common interpretation "common interpretation that anyone who comes to a page", essentially to evaluate anyone and not just those visitor coming from an ad campaign.

    This would…

    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)
  3. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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)
  5. 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)
  6. 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)
  7. 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)
  8. 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)
1 2 4 Next →
  • Don't see your idea?