Implement necessary solution to make Adobe-managed hosted Launch script URL as a first-party resource
Recently we came across situation where we found out that adblockers are not blocking assets.adobedtm.com domains as well, impact of this launch scripts which is hosted in akami (adobe managed hosting option), entire ecosystem of AEP is failed on on webchannel.
Here the concern was core functionality and value proposition of Adobe Experience Platform (AEP) and Adobe Analytics implementations.
As you are aware:
- Adobe positions AEP, Launch (Tags), and related solutions as enabling:
- First-party data collection
- Server-side tracking
- Resilience against ad blockers and privacy restrictions
However, in our case:
- Adobe Launch scripts hosted on Adobe-managed Akamai domains are being blocked by ad blockers
- When these scripts are blocked:
- Data collection fails at the source
- Downstream AEP and Analytics capabilities become ineffective
So concern here If the entry point (Launch script) itself is blocked, first-party data collection and server-side tracking become significantly limited in real-world scenarios. These scripts are hosted by Adobe-managed endpoints (contract with Akamai). I am sure this type of setup is widely used across thousands of Adobe customers globally not just by us. From an ecosystem perspective, Adobe is in the best position to engage with major ad blocker providers and tell them that
- Clarify that these domains are not ad-serving endpoints
- Prevent blanket blocking of Adobe-hosted Launch libraries
However having said, adobe also can implement permanent solution to this problem with below idea. Idea we are proposing here is, make Adobe-managed hosted Launch script URL as a first-party resource.
To serve an Adobe-managed hosted Launch script URL as a first-party resource, either update the guidelines and make necessary changes to launch scripts which will help customer’s to set up a reverse proxy on your own web infrastructure.
Or Implement the solution which customers are submit their request through the Adobe-Managed Certificate Program to make cname entry adobe hosted lunch script domain
Step 1 - for every customer, in akami instead of putting launch script under generic domain assets.adobedtm.com, it should be offer solution where customer can see their launch script urls smoething like this https//<customername>.assets.adobedtm.com/launch.min.js, then through
step 2 - Through Adobe-Managed Certificate Program, they can submit request to make this 3rd party url as first party by allowing CNAM configuration.
This way without changing too many things, customer will benefit from adobe managed hosting option and they dont need to invest in IT infra with self hosting as adobe launch is purely maketer’s tool.