We are an Ecommerce technology solution provider to many clients around the world and often have clients using DTM for their own tagging deployments. Up till now we have been told we cannot run two DTM libraries on the same page (our customers and our own). Will this change with the Launch product such that we don't have to forego our own tag deployments (given the customer always comes first) via Adobe Tag Manager and can actually have two separate Launch libraries running side by side?
Deploying multiple instances of Adobe Launch on the same page will also not be supported. However, you could have multiple rules that fire different beacons to different report suites. Some of this functionality exists in DTM today, but Launch will make it a lot easier.
Have you tried this approach already? If so, were there other issues that caused you to abandon this practice?
Thanks for the feedback and prompt response Jantzen. I'm sure the product team is aware but they should strongly consider making this an option to at the least stay on par with your primary competition; https://goo.gl/CTb4XX. It is costing you business without that feature.
Thanks for explaining the challenges. As far as I'm aware, the product team is not working on any project to allow deployment of multiple instances of legacy DTM or Adobe Launch on the same site. Having two completely independent instances of the same code on a page is inefficient and could cause unexpected conflicts. I understand the need for agencies such as yourself to have an independent implementation so I will pass your comments on to the product team. I'm sorry you were given a date on product roadmap items. Typically, official roadmap items are only discussed with customers/partners by the product team directly after undergoing an NDA process.
My recommendation would be to contact your partner sales manager to see if they can schedule a meeting with the product to discuss this need specifically. There may be other options that could be built into Launch in the future.
With that said, some of your requirements might be solved by Launch. For example, you can already have different data elements today (although it wouldn't be strictly recommended if they are gathering the same data). Also, you could fire completely independent beacons with differing variables and tool settings. Permissions are being reworked, but I'm not sure if they will be as granular as you might need. Even if they were, admins would obviously have access to everything within that implementation.
1. We need to be able to fire tags to different report suites that use completely different data models and configurations (i.e. SDR's) for the exact same web site
2. We need to be able to have different tools, rules and data elements for the same web site. One set for our own uses and needs and one for our clients needs and uses
3. We need to have security such that we can view, modify etc the tools, rules and data elements for our tags and not allow our customers access to view and modify them. Likewise our customers would like to have the security in place that would allow them to prevent us from viewing and modifying their tools, rules and data elements.
4. Our clients have other pages they host beyond the ones we host for the Ecommerce solutions we provide ot our clients. Pages such as Home, Merchandising, Digital Marketing Landing and other types of pages. Ideally they would want the same DTM Web Property library in those pages as well as the the pages we host for them. And we would like to avoid having our library in their pages for obvious reasons.
Given I don't think any of those are unrealistic expectations for a business model like ours with clients like ours I had thought, and was told by Adobe consulting the only way we could accomplish that would be to run two independent DTM Web Property libraries on the same page. Of course they also told us that functionality was on the road map for Q1 2017.
We are suppose to be in a business partnership arrangement with Adobe but unless the above requirements can be met we have to resort to allowing our clients to use Adobe products for their analytics needs and we have to fallback to using Google for our analytics needs. So in essence cutting the potential hits to Adobe by 50% for each of our clients web sites.