MiaProva provides the tools to effectively manage optimization programs. Our kanban board is just one of the several ways we help organizations manage concurrent testing roadmaps.
Author: MiaProva Product Page 2 of 3
This video shows how organizations that use MiaProva can update their connection to Adobe I/O to make use of their optimization data in Adobe Target as well as Adobe Analytics by way of A4T.
* How A4T can provide the mechanisms to align organizationally, scale your optimization program, monitor the program in aggregate, and leverage metric-driven AI
* Automation with Target and putting the metrics and audiences from Analytics to work for you
* Incorporating Automation to advance the journeys of your digital consumers
At the earlier stage of optimization programs, MiaProva provides a standard test ticket in-take form that is based on industry best practice. Our hope is to guide users to carefully consider all factors that can impact their tests downstream.
As most of our clients reach a level of maturity and sophistication in their testing program, the need to allow flexibility has become clearly pressing. MiaProva is pleased to share that we just released a new capability, where different teams in one organization can setup different test intake forms that is most relevant to their individual needs.
Let’s walk through in some details!
To create a new test ticket form, the test manager with admin access can go to the new TEAMS tab under admin console. Here you can setup team specific work streams, as well as customizable ticket intake form.
You can set default form for the ‘submit ticket’ page to load, as well as create and customize any team-specific new form.
MiaProva’s ticket goes through different states in its life cycle. Here are the key states and in which order they occur:
Intake > Submitted > Under Development > Awaiting Summary > Finalized
You can decide if a specific field is required on each state, or if it’s visible on a given state. Please note however since these states are sequential in nature, MiaProva would require you to enter the data in a prior state IF that field is required in the subsequent state.
In addition to add/remove fields from a default form, you can also add additional MiaProva suggested fields or customize your own fields.
To add a MiaProva pre-configured, most frequently used field:
To add a new custom field, first click the ‘add field’ button, then:
Once you finished configuring an existing form or create a new one, find it as the first item on any ticket submission form. Here is an example under the ‘submit ticket’ section:
On this form, choose the form that you wish to use, and all your custom fields will show up accordingly. Note that this form will govern the remainder of the ticket life cycle! So consider carefully please when you set the ‘required’ and ‘visibility’ options when customizing the form. For instance, if you wish to have a simple form to encourage ease of submission, but want to provide very rich test information in the test summary stage, you might want to consider setting ‘test hypothesis’ as NOT required on the input form state, but add it as ‘required’ on the ‘Awaiting Summary’ and ‘Finalized’ stage.
A note about filters:
Note that with these changes, we added custom filters by team as well – since filters are defined by the fields specified for an individual team. Here is an example:
A note about Jira users’ integration with MiaProva
If your organization uses Jira and has an integration with MiaProva, please note that the form that you set as ‘DEFAULT’ will be the one used to integrate with Jira. This is because Jira does not support the concept of different intake forms by different teams.
Adobe Target offers the ability to upload your offline visitor data into Adobe Target for rules-based personalization or for solutions like Automated Personalization to make model-based content decisions.
These simple steps walk you through how to set up MiaProva/Slack integration. Please note, you will need to be a Slack Admin as well as a MiaProva Test manager from your organization to perform this integration.
Step 1. Log into your company’s Slack account, take note of your Slack team name. Then, create a new channel for MiaProva Notification. You can name it anyway you wish. We recommend ‘miaprova’.
Step 2. Log in MiaProva as Test Manager, and click the Gear icon on top right menu to open the Admin page. Navigate to ‘Tests Setup’ panel, scroll to find the ‘Slack Integration’ section:
Step 3. Ater you clicked on ‘Install Application’ button, a browser will open with the following permission request, please click on ‘ALLOW’ to proceed. **NOTE** please verify that the upper right corner on this screen shows the Slack team name that you actually want to integration with. This impacts users who belong to multiple Slack teams.
Step 4. To test the integration, in your Slack App, find the MiaProva notification channel that you setup, and type in hint command ‘/mia’ – you should see a list of available pull commands showing up. To test, choose /mia-new-idea command, and type a sample test idea text after the command. For instance: /mia-new-idea We should geo-target our homepage banner. After you submit this, go into your MiaProva web app, on the left nav find ‘my idea lab’. scroll down the ‘VOTED’ column and you should see the new idea that you submitted via Slack showing up here.
In addition to getting reports for a live test, we are working on additional pull requests that will allow you to see the status of test tickets (e.g. ticket is under development).
Step 5. This step shows how the test manager/admin in your company can control what Slack ‘PUSH’ notifications your business end users can receive. To do this, go to the Gear Icon, select the Notifications tab. Check all items that you think might be beneficial to be PUSHED into Slack. (Please note this is not a pull request by individual users – the push notification will be sent to Slack and show to all users who have access to that channel):
If only I have a dollar for every email, call, text from business stakeholders to ask ‘how’s my test doing?’!
The new MiaProva/Slack integration serves as your new ‘Alexa’ or ‘Siri’ (but no, we don’t listen in your conversation!). Simply ask in the MiaProva Channel inside your company’s Slack account to provide you with a real time test report. You can also submit any test ideas to your testing team, or check on test development status.
Get live test reports from Slack:
On the MiaProva Slack Channel, simply type /mia and click the prompt /mia-1-report. This will provide you with a full list of test ID and names that are currently live.
To get information on any specific test, simply add test name or Adobe Target’s campaign ID after the command (e.g. /mia-1-report 240503).
Anyone in your company can submit their test ideas, and everyone can vote on it in Slack
On the MiaProva Slack Channel, simply type /mia and click the prompt /mia-new-idea, then start to type your test idea.
Once the idea is submitted, it’ll show up in the Slack channel automatically, where anyone can ‘like’ the idea. It also provides the link for users to go into MiaProva to vote on level of effort and estimated return for quick prioritization!
Check test ticket status
You can ask the MiaProva Slack channel to show you status of all submitted tickets, or any single one to see if it’s being prioritized, already under development, or launched. In addition, you can also ask for the details of an individual ticket to see what the test is all about!
List of tests under development now:
see ticket details directly in Slack:
With this integration, your business stakeholders will NOT need to be extensively trained in using Adobe Analytics/Target, nor MiaProva – they just need to remember ‘/mia’ as key words to start asking key questions to get tests update inside Slack!
*Please note that users do need to have an miaprova account to see these protected information in slack.
Throughout years of consulting, MiaProva founders understand key challenges facing companies from gaining the credibility to build a testing program from ground-up to scaling a mature program to even higher level. In this blog, let’s see how MiaProva offers unparalleled solutions to address these common challenges:
- Traffic control of large volume of tests
- Lack of visibility into test prioritization & status
- Business is unable to access real time reports of test performance
- Labor intensive to create knowledge base of past test learnings
- Quantify testing impact to organizational KPIs
- Difficult to promote testing best practices in a large organization
MiaProva shows test experience & report in the context of your own web page
MiaProva’s Chrome extension has 650+ active enterprise users!
- Show all tests running on a specific page with offer details
- One-click to turn off tests on the page and see default experience
- See user real time profile to understand personalization
- Research on any industry websites to see what tests they are running!
- See real time test performance report
- Allow anyone in your company to submit test ideas within the page context
- *2020 roadmap: render different test experiences on the page by a single click
Miaprova provides Automated Reports via Adobe I/O
No time to pull Target reports for everyone asking you how their test is doing, day in and day out? No problem! MiaProva pulls all Target and A4T reports automatically for you! In addition, any business users can self help by:
- Slice & dice the reports by Audience Segment
- Create any custom metrics from Target or Analytics
- Show alerts when sample size are met & test version reached significance
- Search or filter to find tests for a certain work stream or custom labels
- Test managers can control who sees which reports
Integrated with Slack & Jira to super-charge existing program management tools
Love MiaProva’s powerful ideation and reporting capability, but don’t want to change your existing test management process in Jira? Our ‘Fast Track’ Workflow offers full integration with Jira so any update made there will automatically show up in MiaProva, and vice versa. You can get the best of both tools with no re-training or extra work!
In addition, MiaProva provides both push an pull integration with Slack. You can:
- Subscribe to receive push notification on any test updates!
- User can pull real time test report or see test ideas via a single command in Slack!
- Anyone in your company can submit test ideas via Slack without MiaProva access
Documentation of past test learning – Done for you!
No one likes documentation.
Other tools might offer test library for learnings – but how much manual work would it take for you to create those documentation? Frequently, without dedicated resources, those pretty interfaces go unused and test results still scatter around email, powerpoint, etc.
MiaProva automatically creates 90% of the test summary content based on test requests and adobe report; Add your summary observation and any deep dive analysis as attachment and be done!
Test Managers are in the drivers seat, not us
MiaProva prides itself in enabling test managers to configure almost every part of the tool, so that you have full control over how report looks, what metrics/audience to import from Adobe, filters / labels to use, even to choose an entire work flow to best manage your testing tickets!
In addition, we provide hands-on, 1-1 training with any test managers to get started, following our quick-start guide!
Reach out for a demo and free 30-day trial to see all these features yourself!
Feature: Allow testing managers to remove a concluded tests from public view
Testing Manager can now choose to make a test NOT visible to the larger audience in their organization (those with ‘general user’ role) on the Program Overview page. Simply switch the ‘ON’ button to ‘OFF’ on each test listed. Once the test is removed from public view, it will not be counted towards all the summary KPIs on the program overview page either. This feature provides more control for test managers to report out tests of interests. The ON/OFF switch is located by each test as shown below:
Please note that the test that is switched to OFF is NOT REMOVED from MiaProva, but simply made not visible to the users with ‘general users’ role in your organization. If the test managers decide at a later time to make the test visible again, simply click the ‘INCLUDE DISABLED’ checkbox on top of the filters panel, and that will make visible all the disabled tests.
Feature: Jira integration customization by each company
Prior to this release, any updates to a ticket inside MIaProva’s test management work flow will trigger a mirrored update in Jira if a company enabled our integration. This release introduces a company-level, MiaProva admin controlled configuration to determine at the Final Awaiting Summary stage, if a ticket deleted in MiaProva will trigger a deletion in Jira. MiaProva customers should contact email@example.com to indicate their preferences of this configuration.
Feature: Allow users to customize testing KPIs on Program Overview
Testing Manager can now choose if a specific custom metric should be shown on the Program Overview page as the organization’s global testing Key Performance Indicator. To do so, in the Admin console, go to Test Setup, Custom Metrics and find the metric of choice. Click EDIT, then check the ‘show in aggregates?’ box. The selected metric will show up on the top summary panel on the Program Overview page when the relevant Goal metric is selected (or if no goal is specified).
Related to this feature, previously MiaProva default Revenue and Conversion to show on the Program overview page as required metrics. After this release, Revenue and Conversion are treated like any other custom metrics (no longer shown as default).
Feature: Code Conflict Alerts now requires users to turn on
Code conflict alert (Admin Console > Alerts > ‘One or more specific server elements..’ alert) occurs when MiaProva detects server side elements referred to in the test offer are no longer available, resulting in broken test experience.
To generate this test, MiaProva requires test managers to specify the page URL where the test is happening. This allows MiaProva to monitor the server side code change over time on that page through the test’s duration.
In this release, MiaProva by default turned OFF code conflict alert and its associated alert that reminds test manager to set location URL. If your organization would like to enable the code conflict and location URL entry alerts, please turn it to the ON position in the Admin Console, Alerts tab.
Please note: Once enabled, if no test location URL is specified in MiaProva, a message will alert you to enter test location URL to enable the monitoring of code conflict.
Feature: Targeting conditions on Swimlane view
MiaProva leverages the latest enhancement in Adobe Target I/O’s audience API data and improved its ‘targeting condition’ details on the Swimlane page. Users now can have a comprehensive view of the specific targeting condition applied to a test: