Category: Adobe Target Page 1 of 3

MiaProva and Adobe Workfront

On March 2, 2023

MiaProva is thrilled to announce our custom and highly advanced integration of Adobe Workfront to MiaProva.

The video features a discussion about the integration between MiaProva and Adobe Workfront, and how this integration benefits customers who use both solutions for their optimization and personalization management. In this blog post, we will provide an overview of MiaProva and Adobe Workfront, explain the value of their integration, and discuss the benefits that customers can expect.

MiaProva is an Enterprise test management platform that sits on top of Adobe I/O. This platform enables organizations to define journeys within MiaProva using the rich data within Adobe Analytics and Adobe Target. MiaProva automates the management of default data sets that get applied based on the journeys. The platform has over 84,000 activities in its ecosystem from organizations around the world and over 2200 active unique users. The robust test and personalization management platform offers single sign-on capabilities and extensive integrations with the Adobe world, including Adobe Analytics, Adobe Target, and Adobe Journey Optimizer.

Adobe Workfront, on the other hand, is an Enterprise project management tool that spans organizations across different departments, from IT to marketing. The tool incorporates management of creatives and all the business workflows that go with them, making it an impressive tool. Workfront offers various stages or status levels of different projects within the organization, similar to the Jira world.

The integration of MiaProva and Adobe Workfront automates the import of business-end activities, test request documents, issues, and projects. The integration is fully automated, which is very exciting for customers who are taking advantage of this integration. Customers who use both solutions can expect to realize the ROI against some of the projects that they manage within Adobe Workfront, with MiaProva serving as the catalyst to stitch these two together based on the concept of journeys.

The integration offers several benefits for customers. First, it enables customers to fully automate activities coming in from Adobe Target. Second, it allows customers to manage metrics, calculated metrics, segments, and data that’s in Adobe Analytics. Third, it provides industry best practices, such as sample sizes, sample ratio mismatch, and custom alerts based on lift and confidence thresholds. Fourth, it offers a robust test and personalization management platform. Finally, the integration offers extensive integrations with the Adobe world and single sign-on capabilities.

In conclusion, the integration between MiaProva and Adobe Workfront provides an exciting opportunity for customers who use both solutions. The integration allows customers to automate activities, manage metrics, and offers a robust test and personalization management platform. Customers can expect to realize ROI against some of the projects that they manage within Adobe Workfront. With extensive integrations with the Adobe world and single sign-on capabilities, the integration offers a seamless experience for customers who use both solutions.

This integration is of enormous value to Adobe Target and Abobe Workfront users. MiaProva serves as the bridge connecting Projects in Workfront to Optimization and Personalization efforts via Adobe Target Activities. This automation is further advanced by MiaProva’s Journey concept, which buckets default metrics, segments, events, and calculated metrics from Adobe Analytics based on Journey.

Not only will this integration serve the creation of an automated knowledge library combining the two datasets, but it will also automate the ROI of each Project from Workfront, giving the organization an accurate view of the metrics each Project is making.

The video is an announcement of the integration between MiaProva and Adobe Workfront, which automates activities and optimizes personalization management for Adobe Target users. MiaProva is an Enterprise test management platform that automates the management of data sets and enables organizations to define journeys within MiaProva. The integration with Adobe Workfront automates the import of business end test request documents, issues, and projects. Adobe Workfront is an Enterprise project management tool that manages creatives, workflows, and resourcing. MiaProva focuses on optimization and personalization efforts within programs associated with Adobe Target.

Video Transcript

MiaProva and Adobe Workfront – YouTube

Transcript:
(00:00) we are very very excited to be putting together this video this video represents our formal announcement of our big and custom integration between Mia Prova and Adobe workfront this video is going to dive into quickly at a high level what MIA Prova is what Adobe work front is and the value our customers are realizing by having these two solutions working together as part of their optimization and personalization management we’ll also dive into miaprova dive into Adobe workfront and show you how the integration works and how it’s fully
(00:36) automated very very cool stuff so at a high level what MIA Prova is Mia Provo is an Enterprise test management platform it sits on top of adobe IO which allows us to do a lot of incredible things like fully automate activities that are coming in from Adobe Target we’re able to manage metrics and calculated metrics and segments and data that’s in Adobe Analytics we enable organizations to Define Journeys within Mia Prova using all the rich data within Adobe analytics as well as Adobe Target Mia Provo automates the
(01:10) management of the default data sets that get applied based off of the journeys we’ve got over 84 000 activities in our ecosystem from organizations around the world over 2200 active unique users and because of the standardizations that we bear and the the framework that supports a customer Journey approach which allows organizations to you know have a set of tests targeted to some goals and then another set of tests to another goals just to really extract more value out of their use of adobe Target we’re saying
(01:45) increases on average about 30 percent uh with Adobe Target customers data centers in the US and the EU we’ve got industry best practices Galore everything from sample sizes to sample ratio mismatch custom alerts based off of lift and confidence thresholds really all the good stuff you need in a robust test and personalization management platform we have single sign-on capabilities and extensive Integrations with the Adobe world like I said Adobe analytics Adobe Target or customer Journey analytics Adobe Journey Optimizer we we we’re
(02:24) fully integrated with the Adobe i o ecosystem Adobe workfront which was acquired by Adobe in in late 2020 for 1.5 billion has its own Rich set of apis including a new version that Mia Prova is integrating with but if it if it goes to Adobe IO we’re fully we’re fully there and ready to take advantage of it within that system here I’m going to be jumping into the plaque both Platforms in just a second but this is what the ROI looks like and this is the story behind Adobe Target and Adobe or I should say Mia Prova and Adobe work
(03:01) front so Mia Provo was originally architected to support the Adobe Target Community the vast majority of our customers are Adobe Target users we do have the ability to support other testing platforms but given the rich set of apis that are available from the Adobe ecosystem from like an administrative standpoint we really are able to really fully automate things um with the Adobe stack and so what we do today is we automatically bring in any activities that are being used in Adobe Target as well as some older
(03:36) activities for as as part of an audit process we provide and we tie that data to Adobe Target Adobe analytics based off of these customized Journeys and what this Adobe workfront integration now does is it takes the the business end of it the the test request documents the issues the projects you know what whatever you call them um and it automates the import of that very very exciting stuff and and our Enterprise customers that are taking advantage of this integration are realizing like the ROI against some of
(04:15) the projects that they’re managed within Adobe work front and Mia Pro is the Catalyst to stitch these two together based off of this concept of Journeys um that that I’ll be happy to dive into if people are interested so let me jump into the uh what workfront is uh I I think the the people watching this video are probably familiar with Mia probe and Adobe Target so let me show you what what Adobe work front is so it’s it’s an Enterprise project management tool that typically spans organizations across
(04:48) different departments everything from like I.T to marketing and the the opportunity for Adobe was to incorporate that as part of the experience Cloud you know managing creatives and and all of the business workflows that go with all of that so it is really an impressive tool and and myself and my team we learned a lot about it uh when we built this integration we had to kind of dive deep um and it’s it’s really really extensive all the all the different components within there and and this is uh this is
(05:20) a workfront account you can see there’s lots of things in here that everything from timesheets to kind of analytics around the workflow resourcing budget stuff teams all that good stuff but what MIA Prova is focused on Mia Prova is focused on getting the projects the programs that are associated to optimization efforts or personalization efforts so at a high level there’s this concept of programs programs you can have one for let’s say the optimization department or the paid search Department or email marketing or creative
(05:56) management you know things along those lines so the organizations will typically have multiple different types of programs and so I’m just going to jump into this program here optimization and so each one of these different projects typically represents an effort within um Adobe Target you’ve got all the different details around the ticket and the fields that are customizable workfront does something really cool in terms of how they manage their fields it won’t get into that but it is very impressive how they’ve constructed this
(06:32) and so organizations there’s there’s various stages or status levels of these different projects within workfront so this is very very similar to the jira world where there’s issues and whether it’s an epic or a story uh the equivalent here is the work front project where you can see all of this coming together within here and so what MIA Prova did is they wanted we wanted the ability to allow organizations to Define whatever projects they want to show up in Mia Prova and will automatically create a program or a
(07:09) project that that has all of these fields as well we also dimensionalize this where you can use this data and construct different reports on on the program itself so lots of different features and functionality here we also wanted to apply a condition when to have it come into Mia Prova Mia Prova has rules and logic in place for when we get activities from Adobe targets we want to give organizations that use workfront the ability to Define when the data gets into Mia Prova as well so this is workfront a lot to it I’ll
(07:45) jump over to Mia Prova here so this is Mia Prova it’s connected to both uh Adobe and workfront as well as jira within this particular account so this column here this column live activities this is automatically fed from Adobe Target and Adobe analytics we can bring in data from any of the variables that collect data within Adobe analytics so this is data that’s coming in based off of optimization efforts within Adobe Target so jumping over here to the Integrations we got the integration with Adobe the
(08:19) integration with jira slack soon to announce an integration with teams but this is our workfront integration this we provide a certificate make it very easy to connect to Adobe to word fronts integration and what happens then the integration takes literally just like five minutes to do we just set up a big Enterprise company a few weeks ago it worked wonderfully download the certificate we’re up and running within probably 20 minutes and so once the connection’s made all of the programs show up within here because
(08:55) like I said workfront is typically in Enterprise wide uh you know product that’s used across the broader organization and so you could select whatever program that you’d like and you can see kind of like this is where all of the different programs are available you can see all the programs within uh jump back here go to programs this is the uh where is program programs right there so these are the different programs so obviously you don’t need them all you just need the one that’s focused on the optimization
(09:26) so you would select optimization this one’s already in use here but you can see the different status levels uh to have it brought in what’s made the most sense is when the activity has gone live so we typically do that and then where you want this project from work front to go into Mia Prova because we have various stages that align to a typical you know testing life cycle and what we’ll do then is we’ll automatically create a program within the Mia Prova ecosystem and in a program this is a very very popular feature that
(10:03) we have within here even well before the jira and and workfront Integrations programs represent the different intakes you know what are the fields that we want to require and what states do we want them visible all that sort of thing and so what we’ve done here for the workfront integration you can see here is we automatically create this we we have default fields that we use like Adobe Target the offers the activities audiences and we tie that in to data that is uh was already constructed within Adobe word front so it’s really
(10:39) really fully automated and so we can even come let me go back to the workfront integration here the mapping and so you can see these are the different programs that we have implemented into Mia Prova and so what will happen is automatically when these tickets or these projects within this program appear at different various States or they’re updated uh with the diff additional text immediately that’ll transcend down into Mia Provo so that’ll show up here you’ll see there’s part of our queue within here
(11:18) so you can see here the some of the different feeds that have come in based off of activities that have come in from work front so now these workfront related uh programs I’ll just jump over to this so we can filter on this so all of these different uh tickets within here came from work front and so where the where the integration comes together between Adobe Target and Adobe analytics I’m just going to jump to this particular ticket here this is a ticket that came in from work front and as different things happen and
(11:53) come in as part of that the the values will get updated within here so you can see there’s lots of different fields within here uh let me get the Adobe Target activity here here’s a list of all the activities that are live that are not associated uh with tickets so this is just this is our kind of like Play account that we deal with uh so it’s not really too exciting updated here but it is real data coming from Adobe Target and Adobe analytics based off of metrics that are being collected from based off of the journey definition
(12:24) and so we construct a day over day view of it as well as any default metrics based off of Journeys within miaprova you can see here automatic segments they come in from from Adobe analytics and so what we just did right there by simply selecting that activity is we stitched the Adobe Target data with the a for T that has the A4 T data to Adobe work front so we’re constructing the knowledge library in a very very efficient manner let’s say this test was a significant win and I wanted to let’s say the the conversion
(13:00) weight lift was 3.56 I’ll incorporate another metric here average order value we see 156.23 so we automatically have the Adobe data by default based off of Journey but we have this section here called impact to business which allows the metrics to be presented in various dashboards that we have on our program overview and so with here we could simply archive this oh I’ve got to say save the start date and at least one metric okay so I’ve actually done that already by saving the activity and so now I can archive this activity
(13:36) so now this activity I can even send out this summary email this summer email is the program that came from workfront tied to the data from Adobe Target Adobe analytics so really an efficient way to kind of bring everything together and then those tickets ended up on our program overview within here so as these workfront projects get archived with the connection to Adobe analytics and Adobe Target data you can kind of start realizing the ROI of some of these different uh programs within here you can also construct charts and goals and
(14:12) all that good stuff around there so there it is um you know if there’s any questions please let us know very very excited for this integration and uh yeah happy testing

Report Groups for Adobe Target’s Automated Personalization

By MiaProva

On February 21, 2023

In Adobe Target, YouTube

I have long been a big fan of Automated Personalization (AP) in Adobe Target. One of the critical features to extract as much value from it as possible is Report Groups for offers used in AP.

Report Groups allow you to folder or bucket similar offer themes. One client of mine recently took my advice to do this exercise and, since doing so, has realized a 28% lift with the targeted group vs. control by raising the conversion lift to 9% from 7%

The video is about automated personalization in Adobe Target, and the speaker suggests grouping offers in report groups to extract more value out of it. Report groups help automated personalization associate learnings from other similar offers that are from that particular group, and it is a best practice to associate report groups within similar offers. The speaker mentions an example of a client who saw a conversion rate lift from 7% to 9% by creating report groups. Using report groups also helps in getting reporting by different report concepts.

Video Transcript

Transcript:
(00:00) okay so hopefully this is really quick this video is about automated personalization and a big tip to extract more value out of it um one of my customers I was working with today we’re looking at some of the automated personalization activities that they’re that they run and I noticed that they weren’t grouping the offers in in uh and what that means so I’m going to jump through some examples so this is automated personalization uh one of the activity types in Adobe targets form the former product touch Clarity and you
(00:33) know I I have a video coming up where it Dives deep into in terms of what it does but as you add more content to each one of the different um within automated personalization all of the experiences get here depending on if you’re using one location or two locations but this example is using two locations so all the possible combinations of the different pieces of content are within there and you can actually kind of see I’m using this area on our home page and I think another area down here um let’s do it for demo purposes oh it’s
(01:03) right there the about button um so all those experiences go within here but then all the possible offers you can put them into different groups so I was qaing something here but you’ll notice here the report group is unassigned so within here you have different options you can you can edit the audience for it but you can create a report group and what this does is it helps automated personalization associate learnings from other similar offers that are from that particular group so let’s use United Airlines as an
(01:38) example uh I’m a United guy so I’m familiar with um their site and all the different things going on within there so here you can see they’ve got a credit card offer and let’s say for automated personalization they had four or five different credit card offers or they’re adding a new credit card offer uh to automated personalization by putting it into a new group using that example credit card offer and apply that what happens is as you add more content to this folder the the random Forest models within automated
(02:11) personalization associate those learnings and so it helps that new offer um or offers within that particular group share those particular insights and so it was fascinating it’s kind of like a best practice with automated personalization to associate report groups uh within um you know similar offers but this particular client um put the report groups in place organized everything and then saw like it went from a conversion rate lift of of seven percent was you know full confidence uh to nine percent so just in
(02:49) a couple weeks time the the models were able to kind of take advantage of the shared learnings and so um they’re going to continue watching and I’m fascinated by it I could be continued to watch it but it was a nice reminder for me to just put this together quick video that if you use automated personalization one of the best things you can do is uh is is kind of create a report group for all the different types of offers and then the other thing you get with part of this let me just assign this to the report
(03:20) group as well credit card offer apply that within here done next next save and close so you can also get your reporting by these different report Concepts so let’s wait for this to quit to finish syncing there we go I’ll come back reports okay there we go I wish they would do this I know two years is kind of ridiculous but let me just do last 30 days save so here you can see in this automated personalization you’ve got your control versus targeted but it does it by report group or offer group so you can kind of
(03:55) see uh the reporting stuff in context with that so there you have it quick tip on automated personalization

Custom Code in Automated Personalization within Adobe Target

By MiaProva

On February 15, 2023

In Adobe Target, YouTube

Automated Personalization is one of my favorite tools in Adobe Target. There is one nuance, though, when you wish to use custom code to define the experiences used by the models or for random distribution. This video outlines a quick workaround.

In this video, the speaker talks about using custom code in automated personalization activities within Adobe Target. They explain that while the visual editor in Adobe Target allows for modifications, adding custom code is not an option in creating an automated personalization activity. The workaround suggested is to grab something static on the page and add custom code to it, while ensuring that the source code of the image is maintained. The speaker emphasizes the usefulness of custom code in automated personalization and suggests this workaround for situations where it is needed.

Video Transcript

Transcript:
(00:00) okay so this is a pretty quick video I’m putting together because uh it’s come up a lot recently uh regarding using custom code in automated personalization activities so um I’ll just kind of show in the details here so a little bit of background uh at analytics demystified I help a lot of companies with the use of automated personalization uh Mia Prova there’s tons of companies using automated personalization where we do different things well anyways um I had a interesting situation come up like I said quite a few times where you
(00:34) wanted to inject custom code and I’ll show you where this comes in so using the visual editor in Adobe Target you have the ability to modify things as you wish really powerful to do different things I use it as often as I can to do what I need to do to set up tasks but there are situations especially being a little bit more technical where I need to add in inject custom code which I do over here very very helpful to do for all sorts of different things if you’re doing kind of like a blended server-side
(01:04) client-side thing setting a cookie you know setting something to the data layer really really cool stuff uh and helpful but that option is not available in um creating an automated personalization activity I’ll show you what I’ve been here and the reason why is because the visual editor or automated personalization needs to know and coordinate when you’re used when you’re making modifications in more than one area of real estate so if you’re modifying something here you know you would just you know modify make the
(01:41) modification uh hello world and let’s say you wanted to add in another offer you would edit the content added another one you would say hello world two and it works it’s really good and effective and especially if you want to control content across different zones or different areas of real estate um but if you’re not or if you can manage that offline on your own there’s no ability to inject custom code so in this particular client they’re introducing new overlays to the site and so they just want a nice easy way to inject
(02:28) custom code and so the workaround is this grab something on the page so basically get rid of this location and so you’re going to come in grab something that is static that won’t change that is available on the site and we’ll be there every every time and so here you got the home page reference to our image and then you would add in your JavaScript here to do you know whatever you’re doing and then just keep adding text HTML offers but always maintain the source code of the imagery otherwise what will
(03:09) happen is if you replace it with let’s say just JavaScript here to do your thing um oh the log to do you will end up overriding your image and so if that variant were to come up so you always want to maintain that image anyways quick video I thought that’d be helpful especially when using custom coded automated personalization which is very very helpful take care

Adobe Target Link Tracking

By MiaProva

On December 9, 2022

In Adobe Target

The video is about link tracking in Adobe Target and how to track links not just on one page but down a funnel. The approach works for XT, AB, and any type of activity type within Adobe Target. The speaker suggests updating the URL with a unique identifier, like s equals one, on each page and then tracking links on those pages by modifying the URL with s equals two, s equals three, etc. The changes can be applied with a visual editor or form-based editor. The conversion can be configured to be viewed as a page and URL contains s equals one, s equals two, etc. The speaker recommends using Adobe Analytics to get better selective reporting and suggests using conversion as an Adobe Target-related metric. The tracking information will not be ported into Adobe Analytics automatically and needs to be manually chosen.

Video Transcript

Transcript:
(00:00) an interesting question came in on measure slack related to Adobe Target I thought it’d be quicker to do a video uh versus typing something out so the question relates to link tracking uh and to track links not just on one page but uh down a funnel um related to an XT activity so I’m an outline an approach that will work for XT a b and really any type of activity type within Adobe Target that’s really helpful it’s something that I use a lot a lot of my clients use it but it’s also something that automatically flows into
(00:33) Adobe analytics which is good for those that use a for T and something really really helpful so it looks like someone just replied as I’m doing a video so I’ve got uh Adobe Target up here A B activity but again it doesn’t really matter if it’s XT or a B so let’s assume the home page of our blog is page one so what I like to do is since um I’m assuming we’re we’re changing the links or doing content on these different pages but whether we’re doing that or not what I like to do is
(01:05) update the URL put something a little bit unique like s equals one um so that we know that okay on this particular page s equals one because people can get to this page outside the test just like I imagine they can get to your links outside of the test so then I’ll jump over to browse and then I’ll actually go to this page and this will be my page two um but then let’s say I want to track I’ll go back to compose I’m going to apply the modifications let’s say I want to track then the Clank the link on the
(01:39) about so I’ll just come here and then I’ll do and S equals two um so I’ll save that then I’ll go back to browse I’ll go to the about page and assuming this is Page Three I’ll come here go back to compose apply the modifications and then I will let’s say track the link to the privacy and I’ll edit the link within here and I’ll just do and SQL s equals three so I know if people are getting to these Pages outside because there’s they’re not having the S equals three so you know
(02:14) you’re a member of that particular activity the fact that you’re getting that content um so applied those changes with visual editor or if it’s doing form based but then here in Adobe Target you can you can leave it Adobe Target reporting and then just configure the conversion to be viewed a page and then do you could do URL contains uh SE oops I can’t type S equals one you can add a new another URL to be S equals two uh but what I like to do uh I I try to run everything through a for T because
(02:51) it’s so much better um selective particular report so we get that configured um but then down here I don’t use an analytics metric to be kind of a waste because you’re telling the reporting to be uh Adobe analytics here so in analytics workspace you have all of the uh analytics metrics within there um so I just like to do conversion which is an adobe Target related metric allows me to use Target profiles uh any metrics within Target um also by choosing or by letting it go into Adobe a4t the URL parameter
(03:29) tracking is is within there as well so you can build a segment uh for that so I’m just going to do view to page URL is or I can do contains and I can do s equals one uh add another URL or s equals two add another URL s equals three so this this will get aggregated within um as visitors go throughout here then that goes into Adobe analytics and under Adobe analytics that’ll be activity conversions and then you can kind of break it down by Page to give you that funnel view um but if you’re not using a through T
(04:07) if you wanted to use Adobe Target you could build a funnel out like this so you could do a conversion view to page URL contains and you can do s equals one then come down here add a new metric and then this will be conversion view the page URL contains s equals two and so you can build you could have as many of these Adobe Target related metrics uh within and that’ll give you a funnel view it won’t port this information into Adobe analytics you have to choose Adobe analytics here and then at that point
(04:45) you get one single metric from Adobe Target to go into analytics as activity conversion so hopefully that was helpful

Adobe Target Server Side Delivery API

By MiaProva

On September 12, 2022

In Adobe Target, YouTube

Adobe Target offers a few ways to leverage Adobe Target server-side. This is a video about the implementation of Adobe Target’s server-side delivery API. Traditionally, Adobe Target is installed client-side via a tag management platform, with server calls made out. In the client-side world, the visitor API service is on top, followed by the Adobe Target call and the Adobe Analytics call. The Adobe Target delivery API allows for standard HTTP requests, and Adobe also has SDKs for Node.js and Java. There are some limitations to processing cookies or redirect calls, but there are workarounds. Integrating the experience cloud is a common issue, but this can be resolved by putting the visitor ID service before the Adobe Target call. The video provides an example of a server-side call and passing parameter value pairs. Overall, this video provides a basic overview of Adobe Target’s server-side delivery API.

Links mentioned in the video and sample code:

https://developer.adobe.com/target/implement/delivery-api/#section/Getting-Started

https://developers.adobetarget.com/api/legacy-api/index.html#getting-started

** If you are leveraging A4T, implement the Visitor ID service before Adobe Target and pass that visitor ID to Adobe Target as you do Analytics.

###
Post https://miaprovaamericaspart.tt.omtrdc.net/rest/v1/delivery?client=miaprovaamericaspart&sessionId=d359234570e04f14e1faeeba02c6ab9914e
content-type: application/json
cache-control: no-cache

{
"id": {
"tntId": "f64f23fefcd74c7384936a1be29db123.35_0"
},
"context": {
"channel": "web",
"browser": {
"host": "demo"
},
"address": {
"url": "https://www.miaprova.com"
},
"screen": {
"width": 1200,
"height": 1400
}
},
"property": {
"token": "08b62abd-c3e7-dfb2-da93-96b3aa724d81"
},
"execute": {
"mboxes": [
{
"name": "server-side",
"parameters": {
"customer": "true"
},
"index": 1
}
]
}
}

Video Transcript

Transcript:
(00:00) a couple weeks back we got a comment a request from psy looking for us to do a video on server-side implementation of adobe target i replied you know um you know what exactly because it is a very very broad topic and it looks like uh detail about implementation of server-side delivery api so i put this together sai please let me know if there’s if there’s any questions and if uh other folks out there would like me to do a quick video on anything adobe target to be approval related certainly let me know very happy to easily do it
(00:30) so what is server side adobe target in the implementation so uh adobe target uh traditionally uh for the most part if at least in terms of like the customer user base client side where you install adobe target through a tag management platform and then server calls are made out and there could be a global mbox there could be client-side inboxes or i should say adobe target server calls they’re commonly referred to as mbox recall uh mbox recalls but here you can see these inbox calls or adobe target server uh calls taking place client-side
(01:08) what happens is a call goes out to adobe servers and it responds with any activities that are in place it also passes data to adobe target as well client-side here you can see in the mia provo chrome extension examples of a lot of client-side activities and passing data to the adobe target server call including our first party id that we use and you can also see the adobe marketing cloud visitor id commonly referred to as the ecid this is what enables a for t so this is the client side world where you have one the visitor api service on
(01:46) top that’s with the marketing cloud id number two is the adobe target call and then number three adobe analytics call would traditionally happen after that but thanks to this id we don’t have to really worry about that sequence the main thing is that the visitor id service fires before adobe target and adobe analytics so um as far as like the the options that are available so you’ve got the adobe target delivery api which is just standard http requests or https calls um that from any device it could be from
(02:22) anything that’s connected to the internet that supports these protocols but adobe actually has several sdks node.js so if your application is using node.js they could just simply uh install this sdk and they’re off to the races they can make all the configurations um that they need to do that then there’s the java sdk both work wonderfully i’ve got a lot of mia provo customers that are using it as well as using the delivery delivery api which is just standard http request one thing for uh to consider there are some
(03:03) limitations in terms of processing cookies or redirect calls but there’s ways around this you can kind of have the application read cookies and then pass the information along but the big thing i wanted to highlight here is the integration with the experience cloud many of the companies um i’ve heard from me approval customers as they they’ve they’ve installed the server side uh delivery apis everything’s working great in terms of changing the visitors experience but a for t broke because they didn’t put the
(03:35) visitor id service before the adobe target call this only happens uh where the adobe target delivery api on face on first load if that cookie isn’t there for the experience cloud id that’s when there’s a disconnect between adobe target and adobe analytics but it’s a pretty easy fix and actually makes perfect sense to put the visitor id service service side as well that will resolve that automatically i’m going to include a couple links in this video you know link to this documentation which outlines you know
(04:07) getting started there’s also this documentation that i love i love the developers adobe target.com because there are lots of legacy stuff in there and also the kind of like the updates that have been made um and so here here you can see examples of making uh the post requests and how that comes together but i went ahead and i created uh an activity in adobe target just so like the business side can understand what’s going on and so i’ll bring up uh to do visual code uh right here so here i’ve got
(04:41) an example post so this is like a server side call and so what happens is if if this was running on miyaprova’s website for example this code i should go back so this this code would actually fire before anything is returned to the browser here you can see an adobe target server call mbox and i’m passing parameter value pairs you can pass this along any type of data that you might have server side which is wonderful your client code that’s what makes up this part here you can get that in the admin section of adobe target but you’re
(05:19) going to want to pass in the session id that’s something that your application would typically manage standard 30 you know 30 sec 30 minutes of inactivity um and then an id this is the adobe target id that can be retrieved or this is you would also pass along here the experience cloud or marketing cloud id uh as well as your first party id as well and so it’s pretty straightforward it makes a call you can see here i made a call pretty fast uh most of the time let’s look on dns lookup so and this is uh microsoft uh
(05:53) visual code and here’s the response um i got the adobe target response here the telemetry service the unbox name here’s the code my offer that got returned back to the page these are response tokens which very very fun things we we make heavy use of them at mia provo but it’s profile attribute data that’s mapped to this visitor id and so what’s happening here i’ll jump back to adobe target you have to use form based adobe target because you’re actually using um an mbox or a server call name
(06:27) that’s not the global mbox you can’t use target global mbox as the name of the server call it won’t work because that’s reserved for the client-side global deployment of adobe target as far as what the response is you can do anything typically with server-side testing it’s json where you can pass back and then your application when it sees experience or whatever data you’re passing back your application would then do something with it you can see here i was uh given experience c but let me just update this
(07:00) to see if i get a different value i’ll close this response i’ll even update the session id so it’s a little bit different i’ll send the response and there i got experience a because i was a different visitor id but i can make this request all day and i’ll always get experience a because it’s adobe targets of you know a visitor based uh testing platform uh but yeah that’s how it all works comes together um the uh a for t uh should work fine there’s also a really cool thing to consider i’ll actually two things i want
(07:37) to add on here um as far as mia provo customers mia provo lives in an api world so any and all server-side testing that’s done in adobe target is is managed within miyaprova is available for program assignment alerts monitoring real-time reporting all of that good stuff is is available from a mia provo standpoint the other thing that’s pretty cool that i don’t um don’t see talked about enough is the coordination with adobe target client side and server side so let’s say i were to put on my blog adobe target
(08:13) server side okay and then i would go in adobe target with the visual editor here and modify some content just modify something that is on both the client-side space and server-side space so let’s say i modify the about me approva section here okay if i go to the blog that’s the server-side area the adobe target server-side delivery apis will automatically look to see what other tests that you’re in and actually apply these changes server side so that you would see the changes to your client side so something really really cool
(08:51) thought it would be helpful to highlight here but thank you again psy if there’s any other questions hopefully this answered it but if not let me know take care

Adobe Target Audiences and Locations

By Brian Hawkins

On February 15, 2022

In Adobe Target, YouTube

Over the years, we have gotten many requests from customers asking for clarity around how best to use Adobe Target Audiences and Locations when setting up Activities via the Visual Experience Composer (VEC) or Form-based creation.

This video will share best practices and explain how best to leverage the functionality.

Video Transcript

we put together this quick video to
hopefully help
some confusion out there and to share
some best practices and in ways to can
think about test locations and audiences
and how they play out when setting up a
test and adobe target whether using a
visual editor
or a form-based activity
so let me jump in here and show you uh
what’s going on here so i’m creating an
activity i’m going to use the visual
editor so here you supply the url this
is the location this is where you want
the test to execute we’re not thinking
about
using the target profile or anything
like that like you know for repeat
customers or people coming from google
or anything like that this is where the
test is running the location so i’m
going to enter in the url there
so the visual editor is loading and
doing its thing
so i’m clicking on the gear here and
then i’m going to apply page delivery
let’s say we want to expand on that
location
to apply to run on the mia provo blog
so i’ve got lots of options here to
expand on this location and and this is
the first part of the confusion uh
between
locations and audiences that we get
questions on
so
we’re limited here in terms of a list
there’s nothing to do with
people from texas or geographic data
it’s limited to location based which it
should it makes sense to do that let’s
say
i wanted to update this to go on the
blog i can do
or url
contains
www.miaprobot.com
blog cool so now whatever i do in the
visual composer will be applied here
uh on our homepage as well as here i can
also make sure i can use path i could do
you know things
that make sense for locations where
specifically
is the test running so i’ll just save
this update here
so within this section it’s best to
think of it at this experience stage is
not so much who’s going to become a
member of test but rather where the test
is running
you’ll notice there’s a component here
for audiences
i’m going to come back to this i think
this would be better served under the
targeting but i’m going to come back to
this in just a second here let me go
back into another window here and
i’m going to go ahead and create a form
based activity so create an a b test
come here i’m going to select form uh
properties uh is a whole other component
it is very it’s part of locations again
this whole first step whether this
visual editor where you put a url is
location
form is also location because properties
are defined uh you know based off of
where the organization uh defines the
properties and they’re based off of urls
or where the unbox calls are coming from
so now you’ll notice here in the form
target global emma so choose my inbox
now if you notice like in the visual
editor i supplied a url i told adobe
target this is where the test is running
but if i apply code in here i go ahead
and i create an offer and or pick an
offer
it’s a global inbox so it’s gonna that
offer is gonna fire and adobe rightly so
i was like whoa you should you should
refine and limit the scope
uh specifically limit where the code the
offer is going to fire the visual editor
absorbs this information automatically
and so
the test by default will only fire uh in
supply code based off of the url but the
refinements here
are audience refinements so in the
visual editor if you notice it’s it’s
based off of you get
uh
you get url per you know path domain
that sort of thing so here you could go
ahead and create an audience based off
of anything
browser operating system geo targeting
stuff that speaks to the the audience
that the the visitors that you want in
um yes there’s overlap i could go in
here and i could do site page uh current
page
url
due to do
contains
you know forward slash block cool okay
so
you’re able to accomplish that but
because you’re being exposed to
visitor stuff right um it’s creating
some some confusion so
even though you can create all of these
other different things based off of
these attributes
at this particular state please uh
consider you know think of this as the
scope of where you want the test to run
when it comes to audience members leave
that through here you can create
audiences you can use all the rich data
you’d like you can combine multiple
audiences
this is something very cool uh you’re
not able to do it in the audience
section although there’s a pretty big
update coming there which might enable
this um
but you think about it this day in the
targeting who
not where who experiences is is is the
where and and the same thing goes for
the visual editor use the
think of this as who’s going to become
members of this test
uh so
that makes sense so uh
here on the experience tab i said i’d
come back to this i’ll do this for both
so on the left here this is form base
okay
so you’ll notice here in the form base
audiences single and multiple
okay which i think is i think this needs
to be moved over to here as well but
they’re actually it makes sense for here
but let’s say i select multiple
audiences here
so i’ve got this odd i’m now
within i’m going to add an experience b
experience c
i’ll add in uh an audience let me just
create one here i’m going to say
chicago
add
rule geo
i’m not a big fan you know yeah i could
select city but
to me
companies are better to use dma you’re
going to get a wider a wider net in
terms of audiences so i’m a big fan of
dma but you can use city there
so wait for this to show up here in just
a second i’m just a shortcut
whenever i create an audience i like to
just create copies of all the ones i’m
going to use for the test
to do so dma i’m going to do this i’m
going to change this to san francisco
okay so yeah this is a much wider net
san francisco oakland san jose okay so
i’ll enter this to the dma
save okay cool so first test i want to
select
chicago so there’s my audience for
chicago i’m actually going to get delete
this i’ll stick with just an a and b so
chicago
i’m going to add in san francisco so
what this enables you to do
we still have the location specific i’m
actually going to update this because
because we need to do this so i’m going
to do
home page hopefully i have that in there
home
nope i don’t let me get out of there so
let me create the homepage big fan of
homepage is path
equals
that uh that allows it doesn’t create an
equal you don’t have to worry about
issues with contains uh or you know
lots lots of companies have had issues
not doing this this is an awesome uh
approach so i’m gonna do a current page
path
to do uh not contains we’re gonna use
equals here equals this so someone comes
in from paid search or something where
there’s utm or tracking parameters
you’ll still be members of this test
this limits the scope uh but this does
not uh if you’ve got lower environments
with different subdomains you’d want to
update that information
so here again
location
here is
audiences so basically if you get
experience a you can have an offer for
chicago and an offer for san francisco
for down here and i’ll and i’ll show you
an example of that
same thing applies within here so again
think of this section as
location where the test is running but
you do have the ability to add multiple
audiences with it within here same thing
as i did here so i’m going to change the
audience
i’m going to choose chicago done
and then i’ll add in san francisco
and here’s an example of how this comes
together
let’s say you’re united airlines i’m a
big united fan here um approaching a
million miler hopefully in the next year
or two
um but let’s say united wanted to run an
a b test where the control was the same
but let’s say they wanted to
highlight a new route for
uh people from from chicago here i i
typed this up so
multiple audience examples united wants
to run a test to visitors in chicago and
san francisco promoting new routes sfo
to ogg ogg is maui in hawaii and ord is
o’hare in chicago and ogg so
how the multiple audiences works is we
in the uh experiences we define the
location
but then we can also add in different
audiences like this and so the test
would look like this chicago you can
have a chicago imagery with text
promoting oh uh ord ogg
uh in san francisco the same thing so
that that’s kind of where that comes
together within adobe uh target within
here so hopefully that makes sense uh
like i said it was a big customer today
set up some tests and had it was a
little screwed up so i had enough
thought i’d make a quick video uh if you
like this and like others or got other
ideas for content to be helpful please
add it to the comments thank you
[Music]

Adobe Target and Local Storage

By Brian Hawkins

On January 30, 2022

In Adobe Target, YouTube

Spoiler Alert: If you don’t want to know today’s Wordle answer or how to access the solution without playing, please do not watch the video below.

Local Storage

Most websites widely use local Storage to store and access data. This data doesn’t expire like cookies and can hold considerably more data than cookies. Because of this, it is no surprise that there can be rich data to arm a testing and personalization engine like Adobe Target.

This video shows how easy it is to get data from Local Storage and make it available to Adobe Target for first impression targeting.

Adobe Target targetPageParams documentation: https://experienceleague.adobe.com/docs/target/using/implement-target/client-side/at-js-implementation/functions-overview/targetpageparams.html?lang=en

Code used to grab the Wordle solution from Local Storage to Adobe Target:

function targetPageParams() { 

		var str = window.localStorage.getItem("gameState");
		var parsed = JSON.parse(str);
		var solution = parsed.solution;

		return ("solution=" + solution); 

}

Activity Conversions Use Case

By Brian Hawkins

On January 22, 2022

In Adobe Analytics, Adobe Target

This week, we had a client reach out to us with an interesting use case with one of their Activities in Adobe Target.

The Activity was a test in their cart targeted to visitors who were making their third visit to that location. Adobe Target profiles easily support targeting such an audience but the Analysts needed to only count purchases if they happened during the same session as that third visit.

This video highlights how you can use Adobe Target ‘events’ and data like Profile Attributes as Activity Goals and still have the data in Adobe Analytics via A4T.

Video Transcript

hello so i’ve got a pretty cool use case
here a client of ours was asking us
about a specific situation a specific
business requirement and how to approach
it
so it’s like oh wow this is a wonderful
example of activity conversions
which we we get a lot of questions about
and and so here here’s a really cool use
case let me outline it for you so
the requirement is to create an audience
that starts incrementing visits
to the cart starting today so it’s brand
new audience it’s it’s not something we
we can bring in legacy visits to from
adobe analytics and share to the
experience cloud and i should have
prefaced this is for a test that they
want to run via adobe target
on the third visit to the cart they need
to show a promo code but only on the
third visit
fourth fifth sixth whatever other visit
only the third visit is to get this
particular promo code i think there is
some data behind the decision for the
third visit
but that wasn’t shared with me so
they also want to only count purchases
made from those visitors when their
virtual was made during that third visit
to the cart if someone came to the cart
on their third visit
adobe target would
put them and show them the promo code
these these folks big users of of a for
t
um they don’t want to see and use the
purchase event in in analytics because
it wouldn’t have the definition
associated from adobe target in terms of
the third visit
so the fourth requirement is to get this
data to get this success event into
adobe
analytics so they can do deeper analyses
apply their segmentation and all the
rich stuff that they do within that
particular world
so this is very doable this is a
wonderful example of taking a success
event from adobe target and giving it
over to adobe analytics to do the deep
diving so first things first in order to
uh
to create this required we’re going to
use the target profile
a wonderful little tool it’s the cdp
before cdp’s were a thing
so
we go into adobe target uh we go under
audiences and i went ahead and i created
this particular script already
so there it is cart visit to anonymize
the company i change the domain
but essentially what happens is anytime
this
url is seen it’s going to grab the
session value which is a
adobe manages it and compares it against
the the last one which is nice it’s a
wonderful way to increment visits
and so this this works good this handles
uh requirement one creating an audience
from from day x
uh based off of certain behaviors
so now we’ll go about kind of creating
this test i’ll go ahead and create this
test in target just to show you how this
all kind of comes together so
come over to here let’s just do an a b
test i’ll use form to be quick
to do next
so let’s just use target global mbox
now what i want to do is i want to limit
this to the cart so let’s uh
the cart but also uh the the third visit
i can combine it the next step but as a
best practice you should you should
location specific stuff here targeting
is more audience related even though the
cart page
is audience and uh but it’s better to
think this let me just rename this
card uh activity
conversions
demo
so we’re going to come in here add in
audience requirements let me just create
a
car page
site pages current page
url
a lot of companies are passing uh adobe
analytics page names it’s a wonderful
best practice i would encourage that
you’d be able to can use that definition
under custom and be able to use that as
an inbox parameter but this for demo
purposes let’s say that’s the cart page
boom cart page has been added okay i’ll
leave that i’m not going to sign an
offer but this would be the promo code
for people that come on their third
visit you can add in multiple
experiences what have you
next uh this would be your
cart visit behavior so what we want to
do is create audience so this will be
third visit to cart
target definition of visit since it’s
becoming from the target profile
okay we’ll go to visit a profile because
it’s a visitor profile attribute and we
will change this to cart visit not
contains
we’re going to do equals and i have it
the profile script it’s not going to be
3.0 it’s going to be 3 exactly 3.
and so this will make sure that this
didn’t get
will not show the promo code to people
who have visits greater than three or
less than three
so boom
first the location of the experience the
audience of the experience next i’m come
over here
and then you’ll remember the a for t was
a requirement so we’re going to choose
analytics
you will choose our
report suite in adobe analytics okay so
now
this is where
we’re satisfying this requirement okay
keep in mind they they
we we want to only count conversions
that happen
when it was happened during
the visitors
third visit to the cart so the same
session of that third cart visit here’s
how we’ll do this
so go back to target
so what we want to do
if i were to choose analytics metrics
you certainly want that would work but
they wouldn’t satisfy this case
for those companies that are using
heavy users of a4t this is kind of
this is helpful to see reporting in
adobe and adobe target
but you get a bonus metric this
conversion is adobe target data so i can
suit view to page which is nice i can
put the order thank you page but that
wouldn’t satisfy the requirement for the
third visit um and there’s nothing here
to kind of help me refine that
um
clicked in mbox this is a wonderful tool
um very popular for um
for visual editor uh driven campaigns uh
but for this case i’m gonna use target
global mbox i’m gonna do target global
inbox
now i’m gonna add in a requirement add
in audience targeting so what i’m going
to do here
is create a condition
that say only count conversions
uh on that third visit to the card so
first thing i need to do is i got to
create like an order thank you page
order think you page do to do
again we would you
friendly little tip here
pass the analytics page name to the
target global inbox that would be
available here let’s just do this
current page
url
contains
let’s just say
thank you dot html
it’s not a real page
for demo okay so i created the order
thank you page
so now what i’m going to do is combine
multiple audiences i’m going to combine
the order thank you page
i’m going to combine the third visit to
the cart
so and then i’ll save this
i’ll select it and hit done
so now this success event let me uh let
me rename this it won’t matter for
analysis just say
purchase on third card visit
oh running out of characters
cart
visit okay
so now um this is like this bonus
success event so i’m gonna simply hit
save and close
i’m not going to turn this on because uh
actually
no i’m not i actually don’t have offer
so i could turn it on um
so i could turn on no harm because
there’s just default content it’ll just
show
uh
so now the activity is live
and so within the reporting it’s a for t
so it’ll take a while to show data
within here i don’t think it’ll be yeah
so it’s not available just yet
but to
let’s just call this
a test within so this now we’re into
analytics
so organizations will have all of their
metrics and all that wonderful stuff as
well
but to get this metric this goal that we
configured here
this is an adobe target driven goal it
would show up in analytics workspace as
activity conversions
and this is applicable to any of your
activities that are running an adobe
target
now you can’t simply just drag over
activity conversions and call it a day
you’ve got to come into here and you’ve
got to adjust the attribution model you
have to change this to same touch
same touch and hit apply
boom you’re done
so what this organization will now be
able to do
is exactly what they wanted
to be able to see in adobe analytics
a success event based off an adobe
target definition of a success event so
really freaking cool wonderful way for
adobe target and adobe analytics to work
together server-side to pass that
information along so

And screenshots of the “Primary Goal Configuration” to automate the flow of this data into Analytics:

Adobe Target Host Groups

By Brian Hawkins

On January 19, 2022

In Adobe Target, YouTube

One of our customers here at MiaProva is expanding their testing efforts and use of Adobe Target well beyond their www and mobile site. They are bringing Adobe Target to their Email Platform, and we are helping them do so.

The magic that is making this possible is Adobe Target’s Delivery API. You have to call Adobe Target before emails get sent because you can’t put mboxes or Adobe Target server calls in email. The Delivery API does precisely this. It calls Adobe Target with data, just as a client-side mbox does on the site, and it gets a response based on any Activities and Audiences configured in Adobe Target.

Host Groups

The challenge this organization is dealing with was permissions within Adobe Target. The team developing this incredible capability for email testing with Adobe Target didn’t have the necessary Approver rights. Given they were new to Target and this organization has hundreds of live activities in place, handing out Approver rights wasn’t an initial option.

Host Groups was the fix, and after talking to a few other companies today, I realized a video might be helpful to the Target community, so here you go:

Video Transcript

okay so this is hopefully a quick video regarding adobe target host groups environments we are helping a big mia provo customer put testing as part of their email service so what they’re doing is actually quite fascinating and it’s awesome and this is a company that makes heavy use of adobe target across their public www properties and a really rich personalization program and they got really cool tools to manage their personalization program at mia prova but this team wanted to incorporate every target to do testing within their email platform and so what i’m going to go over now is something that team wasn’t familiar with they didn’t know about that option and i had several meetings with other adobe target customers today and was asking them as if they knew about this as well and it wasn’t something that was well understood so i said hey i’ll put together a quick video so every time adobe target gets called every time server side client side there’s something called the host group that gets passed along so you guys are probably all familiar with mbox parameters and profile parameters those lovely things you’re seeing them through the mia provo chrome extension here wonderful things that get automatically passed to adobe target client site or server side but there’s another thing that gets passed along so i’m going to copy doo doo doo doo it’s very it’s a lot easier to see this within here so i’m going to copy the mbox request or the adobe target server side request here copy is it a curl i’ll jump over to my lovely visual studio code and so this is what it looks like but the client side actually came from me at provo.com because it actually came from our home page so it’s it’s not something you can fake here or change here wherever the mbox or the adobe target server call came from is the host that gets passed along to adobe target but i’m going to go ahead and switch this to mia franklin franklin’s my dog who is sitting here next to me here so i’m going to generate a server call to adobe target by basically taking this data passing it over to adobe target but i want to show you something here in terms of like the the host groups so i’m just going to go to host groups here in brian so you can see brian and let me type in franklin so you know that that isn’t in here so what you will all see in this host group column is every single domain that adobe target made a request from in your account so you can see it’s empty and i wanted to show you just how quick this is so jumping back to a visual studio code i’m going to mimic the request boom so this is the response or response from adobe target you can see i have a lot of things going on here so i’ve got as you see on my home page lots of activities i demo help debug and show off a lot of things here so the response that you see here is just that all of the different activities the offer code basically what gets back what returns from the browser all cool stuff that powers your client-side testing you can see here all of the response tokens i make heavy use of that here as well so all dandy all works fun and easy but this testing team that wanted the email team that was building this service to put adobe target server-side using the delivery api wanted the ability to come into adobe target set up activities do their thing rock and roll but there was concerns given that the team was new to target they didn’t want to give them approver rights which which would essentially blow allow them to touch other activities if they use the wrong mbox name as part of the delivery apis it could create potential problems so lots of different custom things were talked about and then i was brought aware that i’ve made aware of the situations i’ve brought up host groups long term though long term it’s it’s definitely going to be the workspaces longer long term but for now as they’re building out this service we can incorporate workspaces later but host groups was the way to go so we wanted to give them the ability to get to to to modify activities modify offers because you could modify you can’t modify an offer if it’s live unless you have approver status here so what we did here is here’s an example of an adobe target server side call so we got my mbox name that’s taking place domain whatever so i’m going to update this to thinking is it mia dash franklin so oh let’s check to see so i’m going to so i’ll just make this call really quick to adobe server side boom nothing ah this is default content didn’t get any content returned but i’m going to come over to here let’s look at the host groups and see if i got franklin in there let’s see let’s try brian there’s brian let’s try mia dash franklin there it is mia dash franklin so this is a production host group and so what that means is that if it’s a production host group that the activity has to be approved has to be turned on there’s no way around that and this is the activity that we’re using host demo it’s not not approved but what we can do is we can say okay for staging host group for for activities and staging let’s change the activity mode to active and inactive activities and so i’m going to hit save here so i say that so basically if it’s a staging host group that means unapproved like this activity here it’s inactive should technically be able to fire so let me go over here and search for mia franklin i’m going to change the environment i’m going to change franklin over to staging and hit save so that’s now staging my activity here let’s take a look at this it’s using host demo i’m just returning this json object hello world no targeting in place because i’m using you know i’m using basically this this mbox name um don’t say to do not approve so let’s go back over to studio code i’ll close this response here and i will do a refresh boom lovely so there you go so you can see kind of i got my content back as well i cut the response back as well as all of the response tokens as well so this was huge so just to kind of refresh host groups very very powerful way to allow organizations to qa things but be careful though if you were to put a host group in there let’s say your your development or staging environment what could what could happen like so for example if if i were to use something like if i were to go to let’s say miaprova.com if i were to put me a pro let me put www if i were to change this to staging what would that happen is that all of the unapproved activities on the site so basically all of the ones that are inactive within fire so something to be very very careful with for this particular situation was really helpful um and there you have it

Amplitude and Adobe Target

By Brian Hawkins

On August 13, 2021

In Adobe Target, Features

Amplitude is a Digital Optimization System that we have been asked about quite a bit lately. It turns out, MiaProva has some friends there from our Omniture and Adobe days, and so we got a much closer look at the solution and some of the use cases that organizations are using it for.

They offer a free trial that allows you to send 10,000,000 hits per month, and so we decided to kick the tires and see if we could create an integration for those organizations that use Amplitude and Adobe Target.

*Image from: https://amplitude.com/digital-optimization-system*

Amplitude Data Consumption

We are by no means experts and have minimal experience with Amplitude, but from what we figured out so far, there are many different ways to collect data via SDK Libraries. Given that most organizations using Adobe Target leverages Javascript, we decided to create our Adobe Target custom integration based on their Javascript SDK.

Users and Events

Greatly simplifying things, with Amplitude, you send in a Visitors ID (or use theirs), pass in any Properties related to that ID, and any Events as you wish.

Here is an elementary example of passing to Amplitude that a Visitor is a “Cubs” fan:

var userProperties = {
    favorite_baseball_team: "Cubs"
};
amplitude.getInstance().setUserProperties(userProperties);

This data would then be correlated with the User that was initially defined. An event represents something that has happened like ‘clicked,’ ‘searched,’ ‘hovered,’ ‘started a video,’ etc… Really anything that all and these Events can be Arrays and have Properties similar to how User data is passed. Here is what an Event call looks like:

var event = "MiaProva_trial";
amplitude.getInstance().logEvent(event);

We’ve configured this event to fire when a visitor arrives on our trial page: https://www.miaprova.com/trial as a straightforward example. This documentation goes into much more advanced approaches as well.

Passing in your Adobe Target data

Adobe Target has some wonderful mechanisms to make data available for other solutions like Amplitude. Those organizations that use our popular Chrome Extension get to see Adobe Target Response tokens as one way to make the Activity meta-data visible. We did something similar with our approach to Amplitude.

We first had to decide whether we wanted to push the data as an “Event” Property or “User” Property. This decision has some significant implications for the Analysis and the management of data. While folks can debate the approaches, the best approach is a “User Property.” Adobe Target defaults to the Visitor counting methodology, and for excellent reason. Participating in a test is not like clicking a button or visiting a page, but rather something tied to the User so that it can be correlated to Events after entering into the Activity.

With that in mind, this is the single step needed to push your Adobe Target test data to Amplitude. Keep in mind; these steps assume you have Amplitude snippet in place or the npm/yarn installation. Modifications can be made as needed depending on how you manage Adobe Target’s deployment – we are using Adobe Launch.

You need to add this code to the bottom of your Adobe Target at.js file. This code can be added via the Adobe Target UI before your download the at.js file or it can be custom code added via Launch to execute after Target is Loaded.

     document.addEventListener(adobe.target.event.REQUEST_SUCCEEDED, function (e) {
         if (e.detail.responseTokens) {
             var rt = e.detail.responseTokens,
                 ids = [];
             window.targetExperienceList = '';
             for (var i = 0; i < rt.length; i++) {
                 var inList = false;
                 for (var j = 0; j < ids.length; j++) {
                     if (ids[j] == rt[i]['activity.id']) {
                         inList = true;
                         break;
                     }
                 }
                 if (!inList) {
                     ids.push(rt[i]['activity.id']);
                     targetExperienceList += (targetExperienceList ? ',' : '') + rt[i]['activity.name'] + ':' + rt[i]['experience.name'] + ':' + rt[i]['experience.trafficAllocationType'];
                 }
             }
         }
         if (window.targetExperienceList) {

             var values = [targetExperienceList];
             var identify = new amplitude.Identify().set('Activity:Experience', values);
             amplitude.getInstance().identify(identify);

         }

     });

Pretty easy, right!? Let us break things down so all can see what is going on with this code because developers can use this code to push data to any solution, including CDPs, data layers, etc…

Line 1: This is an event listener that will execute the code within it after a successful Adobe Target server call (mbox call:) has taken place.

Lines 2 – 19: We are creating a window scoped variable called “targetExperienceList” that will have a value that will equal a concatenation of all “Activities, Activity Experience, and Activity Allocation” that were tied to the response of the successful Adobe Target server call (mbox call:). On MiaProva.com, this is what the value looks like:

You won’t typically see this sort of thing, but we have quite a few Activities running here for demonstration purposes. For those of you not familiar with “Activity Allocation,” that value is only pertinent to Automated Personalization and Auto-Target, where Adobe has Control and Targeted Groups. All other Activity types will have ‘undefined’ as a value.

Lines 20 – 26: Here, we are first checking to see if there is a value for “targetExperienceList”. This value would exist if the Adobe Target server call (mbox call:) had Adobe Target Response Tokens that showed that the Visitor was in a live Activity. If so, then it would execute Lines 22-24, which pushes all the Adobe Target data to Amplitude as User Properties. This could differ from the above User Properties because we treat the values like an array if the Visitor gets into more than one Adobe Target Activity on a single Adobe Target server call (mbox call:).

And there you have it:

Then you can analyze as you wish, create user cohorts (not available in free trial), create dashboards, visualize paths, etc…

Happy testing, folks!