Special characters are not allowed in cookies per RFC 2109, 2965, and
6265. However, when storing a Data Element value for a Session in DTM,
the value is not URL-encoded in the session storage cookie that DTM
creates. This lack of URL encoding of whitespaces and special characters
many of my Data Element values contain caused multiple services on one
of my sites to fail when trying to parse those non-compliant cookies.
Please update DTM libraries to automatically encode and decode values
+1,000,000! Enabling bot filtering out of the gate is a big step, and
being able to apply a segment to "preview" or analyze impact from bots
is huge. Honestly, if it's a report that is available in Adobe Analytics
- Reports & Analytics, I should be able to segment on the values in that
The way I see it, there are two core benefits to this feature:
Operational - when something breaks either on your site or in the
implemented analytics code, many times it will cause an anomaly in the
data somewhere. As an example, one of my site's primary success events
dropped ~21% in a single day due to an implementation issue.
Unfortunately, dashboards and reports were not so granular to highlight
the drastic loss in data and seasonal cycles hid a lot of the impact for
weeks on end. Having an...
Since there should be no deduplication issues for overall trended
calculated metric reports at a report suite level, why not show the
total value for that calculated metric, since it's simply a calculated
metric for the entire date range? This would make dashboard widgets much
more useful to include calculated metric totals when possible.