If multiple experiences target the exact same selector on the page, all
experiences are still returned. Due to the selector conflict, only one
of these experiences will actually be visible to the user while the
others will effectively do nothing. This leads to additional unnecessary
client-side processing and misleading A4T impression metrics.Please only
return the highest priority experience for a given selector.
In order to see where a particular offer is used you need to click on it
and view the details to see which activities it is used in. It would be
helpful to display a number next to each offer in the list that
signifies how many activities / experiences the offer is used in.Also, a
filter would be EXTREMELY helpful in the offer search to be able to
filter by active/inactive offers. We find that our offer library has a
ton of outdated items but we do not have an easy way to clean it out
Our developers do not like the excessive number of calls required for
each regional mbox inside of our SPAs, however they like the added
structure of regional mboxes for offers and personalized content. It
would be nice to be able to return regional mbox content setup in the
Form Composer via the global mbox. For example, a list of mbox names
could be passed as parameters to the global mbox for a particular
page/route. The global mbox could return the content for each of those
mboxes listed in a...
A4T currently only includes Activity and Experience level information.
If we want to track offer impressions with Adobe Analytics we need to
use workarounds that are clunky. For example, historically a way to
track impressions of offers was to include a specific URL parameter in
the CTA of the offer and then scrape the page for that parameter and
store in an Adobe Analytics list var. Or you could potentially use the
information from the ttMETA plugin to pull info from the ttMETA object.
Or you c...
Currently the "option.id" in the response tokens is useless and cannot
be mapped to anything. Please add in "offer.id" to response tokens. We
do not want to get rid of the deprecated ttMETA plugin until offer.id
works properly. Note you may also want to update the product
documentation. "option.id" != "offer.id".
The current URL search for activities only searches the base URL that
the Activity was setup against. It does not consider any additional
pages for that activity. Additional pages and other URL based
configurations should be considered in the search.
We run automated nightly regression on our website, however this uses
mboxDisable to regression test the base page without Target. We would
like to regression test Target activities, but we would need a
comprehensive list of preview URLs to do that. We are currently building
a list of these URLs manually in a spreadsheet. Now that QA URLs
persist, this is feasible. However it would be nice to have an automated
solution via Target APIs to pull preview URLs or a way to export in bulk
in the Target...
Add the ability to add tags to rules which can be used for
filtering/searching in the Rules list.Auto-tagging could pull in basic
info into different tag categories. This can be based on the dropdown
values selected in the rule configuration, and if custom code is used.
For example:Extensions usedEvent Types usedCondition types usedException
types usedAction types usedUses custom code (Core)Uses custom code
(Analytics)Custom tagging could be used to allow users to provide
additional info for wha...
Add support to easily access the DTM rule name which is currently
triggered.This can be used for monitoring purposes. For example, you
could populate an s.prop with the rule name and create a simple
Analytics Workspace to monitor that rules are firing as expected over
time. This would also mean you could use anomaly detection.(This was
inspired by Jim's "Tag Fire Count" idea)
There are times when Adobe makes changes to how the DTM library (and
presumably Launch) is built and things may be minified differently, etc.
It would be nice to be notified when the underlying build process
changes to make our IT partners more comfortable. We have run into a few
occasions where we made a very small change and the entire library ended
up being completely different when doing a file compare.
The new rule builder allows for much better control, but its hard to see
the complete logic of the rule unless you give all of your events,
conditions, exceptions, etc descriptive names for what they are actually
doing.It would be nice to have a toggle for a detailed view that
basically expands all of the little components to show the complete
logic. This is similar to how Adobe Analytics does this on click of the
info bubble for custom segments. However, for the purposes of Launch
rules, I thin...