24 results found

1. Feature Request: Show per variant visitor count in experimentation block in Optimizely Analytics

   Stakeholders viewing the dashboards struggle to instantly see the visitor counts in each variants. Please consider adding the number of visitors in each variance in the experiment tile in the dashboards.

   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  ·  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. curated content blocks on the analytics home page

   See also the community post which allows for better formatting: https://usercommunity.optimizely.com/c/analytics/feature-request-curated-content-blocks-on-the-analytics-home-page

   The problem

   What we see

   Home is a single list of every report, sorted by the date it was last edited. This suits builders, who want the work they touched most recently.

   Other audiences meet the same page and face a different task. They want to find the report that matters and trust it.

   Newest is not best. A test copy edited today sits above a reviewed report edited last month.

   Trusted and experimental reports look the same. A copy named "Dashboard_copy" sits next to an approved report.

   Structure is hidden. Folders, such as "Main Reports", appear only as a small tag.

   Guidance is hard to find. Warnings, such as "do not edit this dashboard", sit inside report descriptions.

   The page is plain. It has no pictures, no pinned items, and no starting point for new users.

   Why it matters

   Home is the first impression of the whole analytics product. Senior leaders and new users see this page first.

   We’re democratising access to data and dashboard building, so we want people to get a full exposure to the platform, this curates the first impression of the platform.

   The page works. It does not yet show how much good work sits behind it. This can affect how the product is judged and how widely it is used inside an organisation.

   The proposed feature

   The idea

   Home becomes an ordered list of blocks. Users with edit rights add, move, and remove blocks from a short menu. Nobody needs to write code.

   A curated area sits at the top of Home.

   All content is the default block. It holds today's sort row, search box, and report list. Nobody can remove it, but an editor can move it up or down.

   The header, left nav, create cards, and Filters panel stay as they are.

   With no curated blocks, the page is the same as it is now.

   Content blocks

   Header. Page title, purpose, and optional search.

   Callout. Warnings and notices.

   Featured report. The one report that matters most, with a picture.

   Card grid. Pinned reports with a name, picture, and short description.

   Link list. Dense lists with a name, one line of text, and an owner.

   Tile row. Navigation by area.

   Embedded report. A live, read-only report in a frame.

   Mock Up

   Page templates

   Templates give editors a starting point they can change.

   Team hub. Header, callout, featured report, pinned cards, embedded report, link list, and area tiles.

   Executive overview. Header, one embedded headline report, and three deep-dive cards.

   Getting started. Header, numbered steps, and template cards to copy.

   Ways to create the blocks

   We would welcome any of these, or a mix.

   A. Mark Eting. The editor describes the page in plain words. For example, "a team hub with our five main dashboards and a warning about the read-only report". Mark Eting proposes the blocks, and the editor reviews and changes them. This fits how people already use "Ask Mark".

   B. Form builder. The editor adds a block, fills in a short form, and drags blocks to reorder them.

   C. Sheet or CSV import. One row per item, with columns for name, description, link, type, owner, and image. This allows bulk edits and version history.

   D. Tag driven. Report owners tag a report, and a block fills itself from the tag. This stays current without manual work, but gives less control over order.

   See also the community post which allows for better formatting: https://usercommunity.optimizely.com/c/analytics/feature-request-curated-content-blocks-on-the-analytics-home-page

   The problem

   What we see

   Home is a single list of every report, sorted by the date it was last edited. This suits builders, who want the work they touched most recently.

   Other audiences meet the same page and face a different task. They want to find the report that matters and trust it.

   Newest is not best. A test copy edited today sits above a reviewed report edited last month.

   Trusted and experimental reports look the same. A copy named "Dashboard_copy" sits next to an approved report.

   Structure… 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  ·  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. Feature Request: Improve Label Display for Path Visuals

   When a path visual contains a long label, the text is not displayed correctly and may be truncated or difficult to read.

   It would be helpful to provide additional label formatting options, such as:

   Rotating the label text
   Automatically reducing the font size
   Wrapping the text across multiple lines

   This would allow users to view the complete label at a glance without needing to hover over it or take additional steps.

   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  ·  0 comments  ·  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. Reuse Saved Explore Visualizations Across Experiments

   Allow users to copy or reuse saved visualizations from one experiment's Explore tab in other experiments without manually recreating them.

   Currently, saved explorations are tied to individual experiments, requiring users to rebuild the same reports for each experiment.

   The requested enhancement would allow users to:

   Copy or duplicate saved explorations across experiments.

   Reuse existing visualizations without rebuilding their configurations.

   Add explorations from multiple experiments to a shared dashboard.

   This would reduce repetitive work, improve reporting consistency, and make it easier to compare experiment performance.

   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  ·  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. Feature Request: Auto-save for Dashboards

   Introduce an auto-save feature for Optimizely Analytics dashboards so that changes are saved periodically. This would prevent lost work and reduce the need for manual saving

   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  ·  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. OA Homepage Improvements

   Feature request: curated content blocks on the Analytics Home page
   Andrew Somerharju-Neale proposes a feature request for the Analytics Home page to better serve leaders and occasional users by adding a curated content area at the top.

   Problem: The current Home page is a single list of reports, sorted by last edit date, which suits report builders but not other users who need to find and trust important reports.
   Request: Introduce a curated section with simple content blocks while keeping the existing content list unchanged.
   Why it matters: The Home page is the first impression of the analytics product, impacting its perception and usage within an organization.
   Proposed Feature: Transform Home into an ordered list of blocks, allowing users with edit rights to add, move, and remove blocks without coding. The curated area would include:

   Header: Page title and purpose.
   Callout: Warnings and notices.
   Featured report: Highlighting the most important report.
   Card grid: Pinned reports with descriptions.
   Link list: Dense lists with owner information.
   Tile row: Navigation by area.
   Embedded report: A live, read-only report.
   Mock Up: Page templates like "Team hub" and "Executive overview" offer starting points for editors.

   Ways to create blocks: Options include Mark Eting, Form builder, Sheet or CSV import, and Tag driven methods.

   Andrew asks if others have found workarounds or would find this feature useful.

   https://usercommunity.optimizely.com/c/analytics/feature-request-curated-content-blocks-on-the-analytics-home-page

   Feature request: curated content blocks on the Analytics Home page
   Andrew Somerharju-Neale proposes a feature request for the Analytics Home page to better serve leaders and occasional users by adding a curated content area at the top.

   Problem: The current Home page is a single list of reports, sorted by last edit date, which suits report builders but not other users who need to find and trust important reports.
   Request: Introduce a curated section with simple content blocks while keeping the existing content list unchanged.
   Why it matters: The Home page is the first impression of the analytics product, impacting… 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

   New  ·  0 comments  ·  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

7. Feature Request: Pagination within Dashboards

   Add a pagination feature within dashboards, allowing users to divide long dashboards into multiple pages rather than displaying all visuals and subsections on a single scrollable page. Users could create new pages and move visuals across as needed.

   The main two benefits I see are:

   • Easier Navigation

   • Reduced Query Costs (Queries appear to run as each respective visual enters the viewport. Pagination provides a direct path to desired content, reducing unnecessary query execution and costs)

   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  ·  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

8. Allow Opti ID authentication for customer-managed non-DXP environments (self-hosted)

   Related: EPTS-4294

   Problem:

   Opti ID is currently only available for environments hosted within DXP. Many DXP customers run one or more additional environments outside DXP, in our case a self-hosted Test environment in our own Azure subscription, used for QA before code reaches the DXP Integration environment.

   Because Opti ID cannot be enabled there, we cannot authenticate CMS editors and administrators in that environment using the same mechanism we use everywhere else. This creates a permanent configuration divergence between our QA environment and every environment downstream of it.

   Why this matters:

   Authentication and authorization are exactly the kind of thing QA exists to catch. With Opti ID unavailable in our Test environment, we would have to:

   maintain a second, parallel authentication configuration purely for QA;
   test Opti ID-dependent behaviour (role mapping, access rights, session handling, product switching) for the first time in a DXP environment rather than before it; and accept that any Opti ID-related defect surfaces later in the pipeline, where it is more expensive to fix.

   For CMS 13 this becomes sharper, since Opti ID gates Opal, the Embedded DAM, and Optimizely Connect Platform. Any feature depending on those cannot be meaningfully QA'd outside DXP at all.

   Requested capability:

   The ability for a DXP customer to register one or more additional, customer-controlled hostnames and redirect URIs against their existing Opti ID configuration, for example, permitting a nominated non-production hostname to authenticate against the Integration environment's Opti ID instance.

   This is conceptually the same allowance already made for local development, where a non-DXP host (localhost on specified ports) is permitted to use the Integration environment's Opti ID credentials. We are asking for that same principle to extend to a customer-managed non-production environment with a stable hostname, which is arguably a lower-risk case than localhost, since the host is fixed, TLS-terminated, and under our control.

   Suggested constraints:

   Restricted to non-production environments only
   Limited to a small number of additional hostnames per customer
   Requires HTTPS and a verified domain
   Provisioned by Optimizely on request rather than fully self-service
   Tied to the Integration environment's credentials rather than issuing a new Opti ID instance

   Relationship to the planned self-service redirect URI portal

   The CMS 13 FAQ notes that a self-service portal for managing redirect URIs is planned. We would ask that its scope explicitly include hostnames outside DXP, not only DXP-hosted environments and localhost. If that portal covers this case, it resolves our request entirely.

   Current workaround and its cost:

   Our only current option is to run our Test environment on a different authentication scheme from all other environments, which means the authentication path is untested until it reaches DXP. If that is unworkable for us, the alternative is deferring Opti ID adoption entirely, which in CMS 13 also defers Opal, DAM and OCP.

   Related: EPTS-4294

   Problem:

   Opti ID is currently only available for environments hosted within DXP. Many DXP customers run one or more additional environments outside DXP, in our case a self-hosted Test environment in our own Azure subscription, used for QA before code reaches the DXP Integration environment.

   Because Opti ID cannot be enabled there, we cannot authenticate CMS editors and administrators in that environment using the same mechanism we use everywhere else. This creates a permanent configuration divergence between our QA environment and every environment downstream of it.

   Why this matters:

   Authentication and authorization are exactly the kind of thing… more

   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  ·  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

9. Opti Analytics - Cart Abandonment Rate

   eCommerce Specialist, I maintain our B2B website.

   We are looking for an Abandonment Cart % rate and from what I am explained from your techs is the following:

   I reached out to our Analytics Engineering team to verify whether there is an out-of-the-box feature or configuration that can provide this data. Unfortunately, we don't currently have that capability.

   At this time, the best workaround would be to either:
   Download a copy of the database and extract the required information directly.
   Create a custom integration job to export the dataset.

   You guys have the data, just formulate it for us, please make this easier on your customers. Thanks

   eCommerce Specialist, I maintain our B2B website.

   We are looking for an Abandonment Cart % rate and from what I am explained from your techs is the following:

   I reached out to our Analytics Engineering team to verify whether there is an out-of-the-box feature or configuration that can provide this data. Unfortunately, we don't currently have that capability.

   At this time, the best workaround would be to either:
   Download a copy of the database and extract the required information directly.
   Create a custom integration job to export the dataset.

   You guys have the data, just formulate it for us, please… more

   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  ·  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. Allow customers to add an additional OpenTelemetry exporter for DXP application telemetry

    Once Optimizely DXP migrates the .NET stack from Classic SDK 2.x to OpenTelemetry (required by 2027-03-31 when Microsoft retires Classic 2.x support), please add a per-environment config that lets DXP customers register an additional telemetry exporter pointing at their own Application Insights resource (or OTLP endpoint). DXP's existing exporter stays untouched.

    Why customers need this

    DXP application telemetry currently goes only to a DXP-managed Application Insights resource. Customers can be granted read-only API-key access, but that's insufficient for:

    • End-to-end distributed traces spanning customer-owned frontend/API services and the CMS backend. W3C traceparent already propagates correctly through DXP's Classic SDK 2.21.0 — the trace data exists, we just can't get it into our own resource.
    • Unified SIEM / log-aggregation feeds (Splunk, Datadog, Elastic, etc.) that expect one ingestion path.
    • Customer-controlled retention, sampling, and access policies.

    API-key access doesn't enable Azure cross-resource KQL (which would help) because that's gated on Azure AD RBAC, and DXP support cannot grant RBAC per policy. The only current workaround is for every customer to build their own pull-and-forward integration — duplicated engineering effort across the customer base.

    Why this is now feasible and low-risk

    OpenTelemetry is designed to support multiple exporters per signal — adding a second is a one-line SDK registration with zero impact on the first. The double-counting / Activity.Current conflict concerns that apply to mixing Classic SDK 2.x with the OTel Distro don't apply once the whole stack is OpenTelemetry-based. DXP's existing pipeline, dashboards, alerts, and SLA stay exactly as today.

    Proposed implementation

    A per-customer-per-environment config in the DXP portal:

    • CUSTOMER_APPLICATIONINSIGHTS_CONNECTION_STRING → DXP registers a second AzureMonitorExporter.
    • Or more generally, OTEL_EXPORTER_OTLP_ENDPOINT for any OTLP destination (Datadog, New Relic, Splunk OTLP, Grafana Tempo, self-hosted collectors, etc.).

    Customer-supplied Azure Monitor endpoints are in the same domain family as DXP's own (already allowlisted in egress). Per-customer opt-in; zero impact on customers who don't enable it.

    Once Optimizely DXP migrates the .NET stack from Classic SDK 2.x to OpenTelemetry (required by 2027-03-31 when Microsoft retires Classic 2.x support), please add a per-environment config that lets DXP customers register an additional telemetry exporter pointing at their own Application Insights resource (or OTLP endpoint). DXP's existing exporter stays untouched.

    Why customers need this

    DXP application telemetry currently goes only to a DXP-managed Application Insights resource. Customers can be granted read-only API-key access, but that's insufficient for:

    • End-to-end distributed traces spanning customer-owned frontend/API services and the CMS backend. W3C traceparent already propagates correctly through DXP's Classic SDK 2.21.0 —… more
    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  ·  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. Variance Reduction for Experiments in Low-Frequency E-Commerce Context

    I'm a UX researcher and have been reading up on CUPED for an upcoming experiment. I understand that CUPED is currently set up in Optimizely Analytics to work on the past two weeks of data for the metric of interest, which must be numeric (e.g., Revenue). As is the case for many low-frequency e-commerce products, many of our customers won't have revenue events in the two weeks leading up to an experiment.

    As I dove deeper down the rabbit hole, I came across CUPAC, developed by DoorDash in 2020. CUPAC solves the above problem by using a model-based predicted outcome as the covariate, computed from features observable at exposure time. DoorDash's own benchmark shows 10-20% sample size reduction, which compounds the value Optimizely already delivers. I'd love to have CUPAC as part of Optimizely Analytics.

    I'm a UX researcher and have been reading up on CUPED for an upcoming experiment. I understand that CUPED is currently set up in Optimizely Analytics to work on the past two weeks of data for the metric of interest, which must be numeric (e.g., Revenue). As is the case for many low-frequency e-commerce products, many of our customers won't have revenue events in the two weeks leading up to an experiment.

    As I dove deeper down the rabbit hole, I came across CUPAC, developed by DoorDash in 2020. CUPAC solves the above problem by using a model-based predicted outcome… 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

    New  ·  0 comments  ·  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

12. fabric

    We see that the use of Microsoft Fabric as a data warehouse is increasing. My suggestion is therefore to build a pre-built connector for Analytics to MS Fabric like there is for Snowflake, Databricks, etc.

    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  ·  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. Apache Iceberg Analytics Connector

    Apache Iceberg connector for Analytics to like there is for Snowflake, Databricks, etc.

    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  ·  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

14. Multi-Select Metrics using Checkboxes

    To shorten the set-up time, rather than clicking each metric separately, Michael proposes an option to multi-select metrics in the dropdown with checkboxes.

    5 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

    Future Consideration  ·  2 comments  ·  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. Sequential Metrics for User Journey Analysis

    Dear Team,

    We would like to propose an extension to the recently released ratio metrics functionality through the introduction of sequential metrics capability.

    This feature would enable the combination of two metrics based on their occurrence sequence for individual users. The system should accommodate both flexible ordering (where metrics may occur in any sequence) and prescribed ordering (where a specific sequence is required).

    One might aptly term this functionality "sequential metrics."

    This capability would prove invaluable for analysing the impact of experimental changes on subsequent user actions. For instance, when testing a new button design, we could examine users who both clicked the modified button and subsequently initiated checkout processes.

    This type of sequential analysis would provide crucial insights into how interface changes influence downstream user behaviour.

    Currently, conducting such sequential analysis requires extraordinarily complex workarounds, which significantly hampers our analytical capabilities. The introduction of sequential metrics would substantially enhance our experiment analytics, enabling us to better understand user journey progression and the cascading effects of interface modifications.

    This functionality would allow experimenters to measure not merely individual actions, but the relationships and dependencies between user behaviours, providing a more comprehensive view of experimental impact on user experience pathways.

    We believe this enhancement would greatly advance our analytical sophistication and experimental insight capabilities.

    Yours sincerely,

    Michael

    Dear Team,

    We would like to propose an extension to the recently released ratio metrics functionality through the introduction of sequential metrics capability.

    This feature would enable the combination of two metrics based on their occurrence sequence for individual users. The system should accommodate both flexible ordering (where metrics may occur in any sequence) and prescribed ordering (where a specific sequence is required).

    One might aptly term this functionality "sequential metrics."

    This capability would prove invaluable for analysing the impact of experimental changes on subsequent user actions. For instance, when testing a new button design, we could examine users who… 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

    Future Consideration  ·  0 comments  ·  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. Metric filtering on revenue or value properties

    I'm a big fan of the new filter feature for metrics but would like to see this feature extended to cover standard value and revenue properties, not just custom additional properties.

    A simple use case: a business wants to increase high value transactions so they set up a metric that counts transactions over a certain threshold (e.g. revenue > £200).

    The workaround at the moment is to copy the values and/or revenue metrics into an additional custom property. This seems like unnecessary duplication though..

    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  ·  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. Ratio Metrics for Experiment-Specific Metrics

    Dear Team,

    We would like to request the extension of ratio metric functionality to include experiment-specific metrics, rather than limiting this capability to project-wide metrics alone.

    Currently, ratio metrics are only available when combining project-wide metrics, which restricts our analytical capabilities at the experiment level. This limitation becomes particularly evident when examining conversion funnels and user behaviour patterns within individual experiments.

    To illustrate this requirement: consider a microcopy test conducted on a button element. We can readily track the click-through rate using an experiment-specific metric, whilst simultaneously monitoring checkout initiations through a separate project-wide metric. From an experimenter's perspective, understanding how changes to the button copy affect the ratio between click-throughs and checkout completions would provide valuable insights into user behaviour and conversion efficiency.

    The ability to create ratio metrics combining experiment-specific and project-wide metrics would significantly enhance our analytical depth and enable more sophisticated performance evaluation. This functionality would allow us to better assess the holistic impact of experimental changes on user journeys and conversion pathways.

    We believe this enhancement would prove essential for comprehensive experiment analysis and informed decision-making.

    Kind regards,

    Dear Team,

    We would like to request the extension of ratio metric functionality to include experiment-specific metrics, rather than limiting this capability to project-wide metrics alone.

    Currently, ratio metrics are only available when combining project-wide metrics, which restricts our analytical capabilities at the experiment level. This limitation becomes particularly evident when examining conversion funnels and user behaviour patterns within individual experiments.

    To illustrate this requirement: consider a microcopy test conducted on a button element. We can readily track the click-through rate using an experiment-specific metric, whilst simultaneously monitoring checkout initiations through a separate project-wide metric. From an experimenter's perspective, understanding… 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

    Gathering Feedback  ·  0 comments  ·  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. Event selector Needs to be better.

    Test

    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  ·  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. Event Property Breakdown in Web Experimentation Reporting

    Add ability to view and filter by event property values directly in the Reporting interface.

    Current gap: Cannot break down metrics by event properties

    Desired functionality: Similar to existing Segment feature - display available property values and enable filtering (see attached screenshot).

    •  

    •  

    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

    Committed  ·  0 comments  ·  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

20. Add a filter option for New/Returning users

    I am the Product owner for our Web Experimentation tool. Our current reporting is very robust but it will also be ideal to add visitor segmentation for new/returning visitors. I have a feeling we had this before but no longer able to segment by that. We are always trying to figure out if new/returning users convert different with our variations. Is this only available via audiences? It will be nice to have them on the filters section of the tool when you are looking at the results report.

    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  ·  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