Can you elaborate on what you mean that it doesn't work at all? Do you
see errors when you look at the developer console, and have you
confirmed that a value is set for s.pageName?To enable the traffic
variables in your reporting, follow these instructions
Yes, it is that simple! Instead of writing a lot of custom code, you can
leverage the Adobe Analytics extension by setting the report suites for
each environment using data elements. You reference the value (which
should be a string) from the data element by wrapping the data element
name in %'s. See below:
Your data element needs to be called from somewhere, such as a rule or
extension, in order to output the message. This is why you don't see
anything automatically when you load a page even though there is nothing
syntactically wrong with your code. As this guide explains, a data
element's value will attempt to be reset any time it is called:
https://jimalytics.com/tag-management/adobe-launch-data-elements-guide/
Also, If you must to log messages to the console, it is recommended to
always use th...
You can add or remove resources, and toggle between revisions of those
resources as long as you are working with a library in Development. If
your library has been moved out of Dev, you'd have to first reject it
from its current environment and move it back into Dev which will enable
you to make changes again. This is meant as a way to help streamline the
publish workflow, but it has some major inconveniences. However, it
sounds like Adobe is making improvements to this and they're working on
a ...
Alandy_Iceboats Multiple libraries can exist in Dev status but they
cannot share the same embed codes, so in this case you'd need to create
a new environment. You can do this by going to the Environments tab and
selecting "Add Environment".The new environment will have its own unique
embed code, allowing you to test only your newest changes and keep them
separate from the rejected library. It sounds like your team's workflow
would not permit merging your newest changes into the rejected library...
SDI Toolkit is an extension I use that provides some really useful data
element and rule UI helpers. Some features I use often: - Data Element
Translator: a lookup table to dynamically map data element values to new
values. Great for a wide variety of scenarios. - Malformed URL: detects
errors in URLs to help you maintain integrity of campaign tracking -Set
/ Remove cookies or storage items.
https://www.searchdiscovery.com/solutions/partners/adobe/adobe-launch/sdi-toolkit/Time
and Scroll Event -...
I think you may be looking for Adobe Experience Platform Mobile SDKsThis
page of the documentation contains a helpful breakdown of Launch data
elements and rules in the context of a mobile property. Rules Engine -
Adobe Experience Platform Mobile SDKs I hope this is helpful!
Hi richm, The basic selector you'd need to broadly target all links with
data-target="#accessories":a[data-target='#accessories']If there are
other links on the page using that data-attribute and you want to
exclude them from your rule, you can leverage the parent div with ID
#recommendations and other classes assigned to parent elements to make
the selector more specific to that section, for example:
div#recommendations ul li a[data-target='#accessories']
Hi Sundhara, First, which version of Chrome are you using?Can you verify
that you're able to see the Tagtician extension loaded in your developer
console? In other words, is Tagtician there but the rules are not
loading? Are you seeing the beacons fire when you check for them in your
Network tab? If you are seeing beacons firing and you just aren't seeing
the rules fire, check that you don't have any other extensions installed
that could be blocking Tagtician. Thanks,Alice
