ObservePoint Applications: Migrating Adobe DTM to Launch
DTM to Launch
When migrating tag management systems, ObservePoint can help ease the process and ensure data validity even as things change across your site!
Where to start?
Ensure you have Audits and Web Journeys set up to monitor the core areas of your site. Anything that is key to your analytics and would require immediate action to fix should be monitored in some way. Remember, Audits are for page load events and monitoring your site on a wide scale. Web Journeys are created to validate key user flows or paths on the site, anything a user can interact with on the site that’s measured and important to your analytics set-up (e.g. add to cart, important calls to action, searching on the site, etc.).
You want to have Rules set up to alert you to any anomalies in both your Web Journeys and Audits. Rules are the key way to receive alerts if anything breaks! They can be as simple as looking for tag presence or as complex as checking a variable value against a Data Layer variable. Don’t worry about having a rule for everything, focus on the things that would call for immediate attention!
Before creating a Comparison, you'll need to enable tags for Comparison. By default you can enable three tags for Comparison, but you can talk to your account executive about adding more if needed. To see comparisons for audits you'll want to go to the Comparison Library:
To get to the settings click on the Comparison Settings button in the top right area of the Comparison Library. (You can also access these settings through your Tags Setup section in the Admin area of ObservePoint.) From here you may see tags that you've already added to use for filtering purposes. If you don't see the tag that you want simply use the search bar at the top left to search for your tag by name. Pick the three tags that are most important to you at a variable level. For example, your key analytics tags are likely important here (Google Analytics, Adobe Analytics, etc.).
To ensure that you can run Comparisons using the tag make sure to toggle on "Enabled for Comparison". You will only be able to toggle on three total tags, but you can always return to the settings and adjust which three tags you want to use in Comparisons. You can speak to your ObservePoint consultant if you’re interested in increasing this limit.
The second step to adding a tag for Comparisons is to align which request you're looking to compare. (Some tags may have multiple requests on a page that have different variables.)
Open up the tag you're interested in and go to the Comparison Configuration tab.
From here you can decide to add variables to exclude if you are not interested in the results of certain variables. A perfect example is a variable that changes throughout the day like a timestamp. You can also choose variables to exclude after you have run the report by using the eye icon.
Using Remote File Mapping
Remote file mapping is a way to simulate a swap between an existing tag management system and a new library or file. You can use this function in both Web Journeys and Audits. Go to the edit screen of any journey or audit and toggle on the switch for Remote File Mapping.
Here you want to identify the request URL for your Adobe DTM, then you’ll put the URL for your Adobe Launch library in the second line. (Typically you can find this URL in the header tags of the HTML of your site or in the request URL section of the Page Details report in ObservePoint.) Save your audit or web journey and then rerun it.
Once done you can check your web journey or audit to see how the tag implementation would look with this new library. Remember, this is only a simulation of a file swap. We don't make any actual changes to your site, so running a web journey or audit can be done on your production sites with no harm.
Within a web journey you can see at the tag level what changes happened between the latest run and previous run.
From this report I can easily see where any tags fell off or appeared between the two runs. I can also go to the variable level to see this detail for the tags set up for Comparisons.
I can see that there was a change for the variable fid between these two runs. This probably isn’t a big concern to me as my fid value is inherently dynamic. I may want to go into my Tag Setup and exclude this variable.
For Audits, I need to go to Comparison Results within my audit reports to see this same information. It’s presented a little differently as you see below:
You can click view details to get more detailed information on any of these results.
Along with your Comparisons, any rules that were applied to the Audits or Web Journeys run with remote file mapping will also give you an alert if something is wrong with the library you’re testing.
Some Best Practices
To keep on top of your implementation as you roll out Launch, we recommend that you make sure you have Run-Over-Run Comparisons assigned to your Audits. This allows you to make these Comparisons as you make your actual releases.
You will either want to create Audits and Web Journeys for the parts of your site you have Launch implemented and assign correlating rules to those Audits and Web Journeys or you’ll want to make sure you filter your rules to only apply to the pages where Launch is present.
You can filter a rule by URL as you can see above. Make sure to keep things updated as you continue to roll out your releases.
Speak to your consultant if you’re interested in tying Audits and Web Journeys to your releases through a CI/CD Integration. This can help keep work off your plate and monitoring in place!
By testing out new releases using Remote File Mapping before your release hits prod and by having up to date Audits and Web Journeys with Comparisons running on prod, you’ll be able to catch any changes to your implementation that occur as you roll out with Adobe Launch!
Contact your ObservePoint consultant if you have any questions about the functionality mentioned in this article!