Announcements
Go to Conductrics.com →
Back to All
Improved

3.7.14 Update

almost 2 years ago by Nate Weiss

Greetings from Conductrics!

We're happy to announce our 3.7.14 update, aka Taco Truck.

Those of you who are using dedicated Conductrics environments can opt-in to this update at your convenience. Just get in touch with us to schedule the update!

New Dashboard 📈

The most obvious part of this update is a new Dashboard page, which is an improved version of the current "Agent List" page. We hope you'll enjoy:

  • More information per agent, such as mini-charts for each agent that show the number of visitors daily, and each agent's "progress" in terms of expected calendar days and visitor count.
  • "Pods" at the top of the Dashboard that show the number of agents running over the past few days or weeks.
  • Ability to easily organize your Conductrics agents and dashboard by Area of your site/app, by overall business Objective, and by Outcome.
  • Ability to group agents by Stage, Team, Deploy Target, Area, Objective, and more.
  • Thumbnail images for your agents and variations, to make it easier to keep track of which experiment / survey is which.

You can switch between this new Dashboard and the existing "Agent List" page, so you can ease into it on your own schedule. See Your Conductrics Dashboard for screenshots and more details.

New Agent Stages 🚦

Related to the new Dashboard, Agent Stages should better clarify the process of moving an experiment/survey through Staging/QA and then into Production. These "Stages" are basically a combination of the existing agent "Status" (such as Stopped or Running) plus the state of the existing "QA-Only" mode:

  • Draft - When an agent is first created. This is functionally equivalent to existing Status Stopped.
  • In QA - When the agent is ready for previewing and QA. This is equivalent to turning on the "QA Only" flag and then changing its existing Status to Running.
  • Live - When the agent is ready for real visitors ("in Prod"). This is equivalent to setting the existing Status to Running with the "QA Only" flag turned OFF.
  • Done - When the agent is finished, hopefully after a successful and helpful run in production. This is equivalent to existing status Archived. We also prompt you for an optional Outcome at this point, so you can keep track of which tests were "Wins" versus "Inconclusive" and so on.

These new Agent Stages are mainly for the Conductrics Admin. The original Statuses (Stopped, Running, etc) and QA-Only flag are still used behind the scenes, so the actual runtime behavior of your Conductrics agents hasn't changed in this respect.

General Improvements 💝

  • Agent Scheduling - Ability to specify start and stop dates for your tests/surveys. Set this up in the same window where you change the agent's "Stage" such as "In QA" or "Live". #936
  • Low Traffic Notifications, such when an agent stops working due to a "breaking" change in the page/site. Set this up in the same window where you change the agent's "Stage" such as "In QA" or "Live". #930, #895
  • Shareable Report Links - You can now create Shareable Links to allow stakeholders direct access to selected reporting pages, without requiring them to log into Conductrics. The links can allow access to just the agent(s) and report pages you want, and can be revoked later. #959
  • REST API - Somewhat faster performance in many scenarios. #995

Survey-Related Additions 📋

  • Conductrics Surveys now include multi-lingual support. See the Survey Languages tab (under Survey Details) for an existing survey to get started. #934
  • Surveys are now compatible with sites/pages that have a Content Security Policy that disallows unsafe-inline and/or unsafe-eval. #923
  • For Surveys with "Feedback" (open text) questions, the Survey Responses report page now has additional options to help you sort through the survey responses where the visitor actually provided comments/feedback text. #1015
  • Our Survey Reporting API is now generally available for retrieving survey responses programatically. #996

Client-Side Enhancements 📄

These improvements are for Conductrics usage in the browser, via Express or our Local JS API:

  • View-States now have an option to indicate that the view-state represents a "Full Page Change". Use this option together with an "Eligibility Selector" at the agent level. #979
  • Reduced cookie (or local storage) size when using Conductrics client-side. #780
  • The size of the JavaScript file served by the CDN is somewhat smaller (the extent depends on your actual agents). The file size is also now visible in the admin for each Express / JS Deploy Target. #963
  • We now support a way to send Goal events to Conductrics "server-side" for agents that otherwise run in the browser. See Sending Goals via REST API for Express/JS Agents for details. #976
  • For Express "Custom JS" agents, you can access the agent code and selected variation from within your variation-level JS code. #1021

Little Things That Count 🐭

  • Goals are now assignable to Teams for organizational purposes in the Conductrics Admin. This should make it easier to choose the Goals you want for a given experiment or survey. #965
  • Conditions - Added Visitor Goal Count condition type, for example to target an Experiment to only include visitors based on "number of video plays" or some other "proxy" conversion metric. #597
  • Conditions - Added Minutes Past Midnight condition type, for example to "target" a Survey to only activate during certain times of day. #978
  • Conditions - Added In Range and Not In Range comparisons for numeric values, which can simplify certain "and/or" condition requirements. #980
  • Flowlets - You can now easily copy the contents of one Flowlet to another, for instance from a "Staging" Flowlet to a corresponding "Production" Flowlet. #1004
  • Mutually-Exclusive Agents - You can now provide a custom API Code for the "parent" agent that controls the mutually-exclusive relationship (aka "Bundle"). #1008
  • Testing Report - Added an option to hide the "policy comparison" report rows for "Fixed" and/or "Predictive" (if applicable to the agent). #1009
  • Archived Agents - The "Duplicate" and "Delete Agent" buttons are now enabled for Archived (aka "Done") agents. #1013
  • Agent Management API - Added a with_agent_conds parameter for cases where you need to get agent-level "visitor conditions" for each returned agent. #1018
  • List Agents - You can again create List Agents if you you need to assign multiple variations per visitor, such as mini-recommendations style scenarios. List Agents also now support variation-level meta-data. #1019 #1040
  • WYSIWYG - More context about the currently-selected element while using the visual "pointing" tool, including the immediate parent / child / sibling elements. #1025
  • GA4 Integration - The Google Analytics 4 Connector now supports "Custom Event Templates" which allow you to customize the event and parameter names sent to GA4. #1046

Bug Fixes 🪲

  • Surveys: Fixed a UI bug where a Survey set specifically to a 50% response rate would appear to "lose" the setting in the Admin, even though the 50% was honored correctly for actual visitors. #984
  • Goals: Fixed a UI bug where it wasn't possible to remove the Currency Conversion option for an existing Goal Type.
  • WYSIWYG: Fixed a UI bug where it wasn't possible to remove a "Watch and Reapply" selector for your WYS changes (from the "Gear" menu in WYS mode). #991
  • Testing Report: If a Goal was set to accept numeric values in the past, but was later changed back to non-numeric, the report could continue to show counts/stats based on the past "valued" goal events. #1012, #1006
  • Admin: It wasn't possible to change the weights for a Mutually Exclusive agent relationship. #1030

Delayed until next update 💔

  • GA4 Audiences - We had intended to include targeting via GA4 Audiences in this update. However, we decided to hold this back until our next update, as Google made some relevant additions to the Audience Lists APIs while we were implementing our solution. Please be in touch if you would like early access to this feature as it becomes available. #796
  • Interaction Detection - We're disabling our "Test Interaction" notifications for now, as we revamp the detection logic. They'll be back soon. #814

As always, many of these items were feature requests from our trusted customers. Thank you and keep them coming! 🙌