Report Suite ID is read-only; you cannot change it in a Processing Rule.  https://experienceleague.adobe.com/docs/analytics/admin/admin-tools/manage-report-suites/edit-report-suite/report-suite-general/c-processing-rules/c-processing-rules-configuration/processing-rule-dimensions.html?lang=en

The only 1up props have over eVars these days is pathing. If you don't need pathing for the data, just use an eVar.

Non-Sequential HTML tags are output as adobedtm.com hosted iframes.  Because this is content hosted on a different domain, it does not have scope/visibility of the parent page (browser Same-Origin Policy limitations). In order to ensure both snippets of code are on the parent page and have visibilit...

I would say props should also potentially be additive because you can configure them to be list props. I think it would be good to have a checkbox next to events and additive/list type variables (events, products, props, listX, hierX) to enable them to be appended instead of overwriting.

Unofficially, there is a _satellite.Logger object that stores SATELLITE:[..] stuff for a given page duration.  _satellite.Logger.getHistory() returns a full array of all current logged entries, which is stored in _satellite.Logger.messages array if you'd rather reference it directly. But this is NOT...

Okay well to be clear..  depending on what the full details/requirements for the tags vs. the site are, you may not have to do a full page refresh to make the tracking trigger. There are alternatives to "refresh the page" and "artificially re-invoke/eval PLRs"!. For example, Let's say you have a pag...

The short version is no, DTM does not expose the rule name for you to reference.I have spent a fair amount of time trying to find some unofficial method or property with it, but it is simply not exposed within the scope of anything you can passively do.I have also spent a fair amount of time figurin...

It is possible to get DTM to re-evaluate  page load and event based rules after page load, but it involves some internal _satellite method calls passing some dummy/rebuilt objects, it is not supported by Adobe for public use, and in practice it won't actually work for you 9/10 times.Given the curren...

Here are some links that might be helpful for you, as far as the merchandising eVar stuffhttps://analyticsdemystified.com/adobe-analytics/merchandising-evars-omniture/ https://analyticsdemystified.com/adobe-analytics/advanced-conversion-syntax-merchandising/ What is Merchandising | Omniture Products...

As was mentioned above, you don't need to declare s.eVar82 when using it in products syntax. On a sidenote: when you populate an eVar with the full eVar syntax, it is case-sensitive, and the "V" is capitalized.  So even if you need to declare it; s.evar82 is not the same as s.eVar82.Example:s.eVar82...