Unfortunately, the code snippet in your example will always result in
this manner, with the race condition if it's done outside of Launch's
rule order controls (for example, if you are doing this within custom
code action blocks). In your example, "
window._satellite.track('commonsPageLoad'); " gets fully executed, but
it is only a direct call that then 'triggers' another, completely
separate process. The separate process does not have any relationship or
callback to this. The direct call gets a...
To answer your question directly: You make a rule, then within the
'actions' of that rule you add an Adobe Analytics 'Set Variables'
action. As you customize your 'set Variables' action, you get a nice UI
in which you can set an evar or sprop directly to a data-element. You'll
need to have rules that set variables, execute the proper beacon send,
and then clear out the variables too.One straightforward example is a
typical pageload rule. When the page is done loading (let's say 'DOM
Ready' in th...
Both our ideas are the same thing, just in a slightly different way. For
your example, I would set event2 equal to a new data-element, then I can
use that data element to evaluate eVar5 and return a value (even if that
value returned is an empty string, which would sobsequently NOT set the
event on the record).This event2 = %DataElement% approach allows you to
do a true/false type thing (which your use case describes), as well as
set the event to a value if needed. It even handles the simple use...
The direct call is made in a synchronous manner - but you can think of
all the subsequent activity of the rule running afterwards. The
execution of another Rule Trigger is completely external to the initial
direct call line, so there's no control on timing there.If you need to
control the timing, you do have a few options...Option 1 (do it
yourself): create your own callback, promise, or other control alongside
your DCR to ensure it does no continue until the timing you
desire.Option 2 (let Laun...
To add on to this; I really wish that every update had some sort of
release notes. There have been AA and ECID extension updates with
absolutely no release notes. We don't know if there was a fix to an
issue, or a change in the way the extension behaves.Even if you hunt for
release notes; the Adobe Launch Release Notes pages and the Experience
Cloud Release Notes pages do not always give info.
We can add the votes from here also: Ability to Turn Off/On ActivityMap
Module in Adobe Analytics ExtensionThis is a crucial item for protecting
against unintended/accidental PII collection on poorly designed sites.
It is very unfortunate that we have to edit appmeasurement just to turn
Can you share some of the details about how your Rule is setup?For
instance:Are you using a single rule with a trigger of the click event
-> and then a single action block for AA(Set Variables) ? Do you have
additional actions like Send Beacon, Clear Variables, or custom code
within that Rule?
I've seen some cases where a Dev environment all of the sudden
'disappears' , resulting in any attempts resulting in 404-errors. If
you're using launch command, it's no big deal since you just switch it
off - or to a different environment, but if you are using the DTM/Launch
Switch you will not be able to switch environments since you cannot get
to the menu (i.e. you only get the default chrome extension menu).If you
go into Launch and simply rebuild the library, you should be ok. If for
How are your different rules and their corresponding action blocks set
up?I think the issue your seeing is stemming from something you hinted
at in this quote, but I'm not sure without more info:Where are you doing
the logic to set s.products and s.events? Are you using other
extensions, , setvars custom code section, or custom code blocks?
Thanks Stewart,To wrap this up; I tried a few scenarios to see the
results on "counter-type custom events". Below is the outline and
results.Quick result summary:Yes, if your data element returns '0'; or
you place a 0 in the GUI, then the counter event will not be set for the
record in the report suite after processing. However, the event and
value are still included in the beacon call.Side note: Any other values
returned, that I've tried, still result in the custom event being
collected as usua...