adobedtm.com
adobedtm.com is the host Adobe serves tag containers from — the product line known over the years as Dynamic Tag Management, Launch, and now Adobe Experience Platform Tags. If you found the name in a request log or a privacy report, someone on the site's marketing side published a container to it, and that container's job is to fetch other scripts according to rules the site controls. This index recorded it on 255 of the 5,294 sites measured, 4.8%, which makes it the twelfth most widely seen of the 88 companies indexed here.
The same container, two opposite loading orders
The clearest thing in this group is a split that runs straight through it.
On one side, pages where nothing at all reached a third party early: dnsmadeeasy.com made its first outside contact at 3,153 ms, windows.com at 2,598 ms and digicert.com at 2,408 ms, and on all three the crawl recorded zero companies inside the consent window. comcast.net reached 21 companies in total and only 1 of them landed inside it.
On the other side, pages where almost everything is early: avast.com contacted 10 companies with 9 inside the window, first contact at 632 ms. wiley.com had 5 of 5 inside it. nvidia.com had 2 of 2.
One product, two behaviours. That is the expected result for a mechanism whose entire configuration lives with the site rather than with the vendor — the container does what the site's rules tell it to, including when.
It rarely arrives alone
The co-presence profile reads as one product family. demdex.net, Adobe's audience-management host, was on 129 of the 255 sites, 50.6%. everesttech.net followed on 60, 23.5%; hlx.page on 33, 12.9%; omtrdc.net on 32, 12.5%. Two measurement hosts sit just outside the family: go-mpulse.net on 42 sites, 16.5%, and akstat.io on 31, 12.2%.
Outside that cluster, Google was present on 112 sites, 43.9%, and OneTrust on 101, 39.6%. Meta Pixel reached 22, 8.6%.
The practical use of that profile is diagnostic. Finding adobedtm.com in a request log is a reason to look for the rest of the family, because loading them is a common thing to configure a container to do.
The sites carrying it are large, and the medians follow
The median site here contacted 9 companies over 38 requests, with 1 of them classified as tracking. Among the 88 companies in this index that is 41st by median company count — above the middle, not extreme.
The examples run much wider than the median suggests: t-mobile.com at 26 companies and comcast.net at 21 against nvidia.com and cookielaw.org at 2 each. Enterprise tag management is bought by organisations with enough marketing surface to need a container, and those organisations tend to have accumulated a long list to put in it.
After the consent window closed, the median site added 2 more companies — a figure worth reading on its own rather than by subtracting one median from another.
Late first contact by the standards of this index
The median first third-party contact on these sites came at 792 ms, and the earliest anywhere in the group was 75 ms. Rank the 88 companies here from the latest median first contact to the earliest and adobedtm.com sits 24th, so this is a comparatively late-starting group.
The example that most complicates the picture is ibm.com: first contact at 528 ms with 5 of its 9 companies inside the consent window, against dnsmadeeasy.com's 3,153 ms with none. Both are enterprise sites running the same container product.
Consent tooling, and what the early-contact figure covers
A consent tool was detected on 151 of the 255 sites. Seen alongside were OneTrust on 123, an IAB TCF consent tool on 19, Osano on 5, Cookiebot on 3 and Usercentrics on 1 — overlapping counts, since a page can carry more than one banner product. The sample even includes cookielaw.org, the host OneTrust serves its own banner from, at rank 367 with 2 companies contacted.
On 235 of the 255 sites, 92.2%, some company was contacted before the banner could have been answered, and the median site had 6 companies inside that window. adobedtm.com was present on those 235 pages; the count is recorded per site, so it does not say which companies arrived.
For a page you can open rather than a group of 255, MurmStack reports the same three things per site: how many companies, how many before the banner, how early the first request left.
| Site | Companies | Before consent | First contact |
|---|---|---|---|
| digicert.com | 5 | 0 | 2408 ms |
| windows.com | 7 | 0 | 2598 ms |
| samsung.com | 5 | 1 | 1875 ms |
| adobe.io | 8 | 6 | 1024 ms |
| comcast.net | 21 | 1 | 1966 ms |
| avast.com | 10 | 9 | 632 ms |
| ibm.com | 9 | 5 | 528 ms |
| wiley.com | 5 | 5 | 1092 ms |
| dnsmadeeasy.com | 7 | 0 | 3153 ms |
| nvidia.com | 2 | 2 | 921 ms |
| cookielaw.org | 2 | 2 | 597 ms |
| t-mobile.com | 26 | 6 | 951 ms |
| Tool | Sites |
|---|---|
| OneTrust | 123 |
| IAB TCF consent tool | 19 |
| Osano | 5 |
| Cookiebot | 3 |
| Usercentrics | 1 |
Seen on the same pages
Companies most often contacted by the same sites. Co-presence only — the crawl records what arrived, not who called whom.
- demdex.netTogether on 129 of these sites
- GoogleTogether on 112 of these sites
- OneTrustTogether on 101 of these sites
- everesttech.netTogether on 60 of these sites
- go-mpulse.netTogether on 42 of these sites
- hlx.pageTogether on 33 of these sites
- omtrdc.netTogether on 32 of these sites
- akstat.ioTogether on 31 of these sites
Questions
What is adobedtm.com doing on a site I visited?
It is serving a tag container the site published. The container fetches whichever scripts the site's marketing configuration lists — analytics, advertising, personalisation — so its effect differs from deployment to deployment.
Does finding it tell me what data left the page?
No. It tells you a container was fetched. What that container then loaded is a per-site configuration, which is why the figures on this page are counts of what each page did rather than a claim about the host.
Why does demdex.net keep appearing next to it?
demdex.net is Adobe's audience-management host and it was present on 129 of the 255 sites here, 50.6%. The two belong to the same product family, and a container is a normal way to load the second.
Are sites using it slower to make contact?
As a group, somewhat. The median first contact is 792 ms, which is 24th latest of the 88 companies in this index. Individual sites vary far more than that: 3,153 ms on dnsmadeeasy.com against 528 ms on ibm.com.
How many of the adobedtm.com sites showed a consent banner?
151 of 255 had a consent tool detected, most often OneTrust, which was seen on 123 of them.