Data Warehouse had a dedicated DataWarehouse API v1.3 but has been deprecated and my understanding is due to be shelved completely sometime this year. Though, it was lacking in the features I desired anyway (read on)The current standard is to use Report.Queue  to request a Data Warehouse report. 1) ...

There are specific configuration values you need to populate those columns with. Which value(s) to use depends on your needs.See: PER Modifier Headings

DTM has a (number of) "page views" condition. It keeps track of this within its own library, and it is incremented each time the library is loaded.  Adobe Analytics isn't part of the DTM library and is just a tool implemented through the library, same as any other tool or tag (albeit more integrated...

Oh, right. I suppose you cannot demote Published back to dev.  I'm not really sure why you'd want/need to do this anyways?  Offhand I can't really think of a use-case for it that wouldn't already be covered by just pushing a different build to production.  But in general, I'm a big fan of the philos...

I think in practice most people have a single dev environment and production environment and effectively only have like one person actively doing things at a given time, so I will agree that in practice, the environment/publishing process is a little bit overkill for a lot of people. But I do have c...

Without seeing your config, my first guess is that you have not setup a rule to fire Adobe Analytics (AA).  With DTM, when you setup AA as a tool, it will automatically trigger on page load without setting up any rules.  But in Launch, the opposite is the case: by default it will not trigger, so you...

Okay well, not sure why your site does that.. seems like that's something that should ideally not happen.  But in that case, I would ignore k= param and just look for query= param for search term.

I have not found it officially stated in documentation either, buta) I have seen it confirmed by Adobe in Slack #measure > #adobe-dtmb) I can also see it in the DTM library code:c) You can do your own quick test to see it in action. Create a Data Element named current_time.  Make it Custom Script ty...

Okay well if those query parameters really do represent arbitrary text a visitor enters into fields, then personally I would push them to separate Adobe Analytics variables instead of concatenate them, because there's no guarantee on how many characters they will be or what characters will be entere...

As others have stated, can you please clarify / provide more details about which query parameters represent what? Based on what you've said vs. what I see in the URL, it seems like k=, c=, and l=  are pre-defined dropdown/selection/filter values, and t= is the actual search term?  If so, I would con...