Historically, MiaProva would only provide Adobe Target usage reports from when they started using MiaProva. We have since changed that and now provide reporting on their usage of Adobe Target since they started using it. Many of our customers have been using Target since 2010 or even earlier!
The video is about a new feature in MiaProva’s last release which allows customers to view year-over-year reports on how they are using Adobe Target, including activity throughput. The report filters can be applied to exclude QA activities. The feature has been updated to go back to the beginning of the company’s relationship with Adobe Target. MiaProva’s tools for efficiencies and scale have helped many customers to run lots of activities year over year. The speaker encourages MiaProva customers to check out this new feature.
Transcript: (00:00) here’s a quick video on a small little feature that we incorporated with our last release that a couple customers that provided a few that I saw that was super cool so I thought I’d do a video to show so um what you’re seeing here is um just a report in terms of how you’re using Adobe Target and year over year um reporting in terms of activity throughput and historically what we’ve done is only started the year of the graph when Mia Provo when the company first started using miaprova but we’ve (00:33) since updated to go back all the way in time since the Adobe Target relationship at the organization started and so I thought it’d be interesting to kind of show you know some of this so here’s here’s an organization using Adobe Target since 2010 you can see the kind of the progression year over year so MIA purple customers give this a look um your report filters that you apply within here so when you want to filter out activities like QA that’ll apply on the data set as well so you can you kind (01:02) of see your company’s growth and the companies that are doing like lots of testing as you see here Mia Prova obviously helps with this you know with our standardization our tools for efficiencies and scale and so you’ll see a lot of companies out here that’ll have lots of companies or lots of activities run year over year and me and Prova is playing a big role in in helping scale that out here you can see some of these customers you know a thousand activities year over year um you know some years less but then you (01:37) know so far this year 223 different activities 1809 activities last year so exciting stuff Mia program customers go ahead take that a look um thank you
Here is a nice primer on how the Adobe Developer Console provides credentials to Projects within Adobe I/O. MiaProva was built using JWT, and is thrilled Adobe is moving to OAUTH and deprecating JWT.
This video also demonstrates how easy it is for current MiaProva customers to update their Adobe credentials from JWT to OAUTH.
All future MiaProva customers will immediately be able to leverage OAUTH as their default method to connect to the Adobe Developer Console.
* 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
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…
Adobe’s Model Context Protocol (MCP) tooling represents a meaningful shift in how practitioners can interact with Adobe Experience Cloud products, enabling them to query data, surface insights, and drive workflows through natural language and AI-native interfaces. At MiaProva, we’ve been tracking this closely, and we’re excited to share that we’ve now built native support for…
Optimization teams have never had more data, more tools, or more pressure to drive meaningful business impact. But as the ecosystem has grown more powerful, it has also grown more fragmented. Teams are now expected to connect experimentation, analytics, audience management, activation, and governance across multiple platforms — all while keeping programs scalable, observable, and…