We have two products that provide the same downloadable content. The content is just accessed differently.  We have the server-side tracking enabled on Product A but we are unsure if that exists for Product B (however we have the standard tracking enabled for Product B ex. click tracking using Launc...

Thank your for your excellent advise! Unfortunately going to the dev team to help fix this will take a quarter but we will have the requirements for this set up to fix. 

Currently the debugger is showing duplicate hits for each rule that is sending a beacon.  Also, I can see the console logs say the rule has fired but I dont see anything on the debugger (for some rules) while others are consistently firing duplicates.  Any idea what I can use to do my troubleshootin...

I don't believe its a timing issue as the data element is populated before the search event fires.  Since I can already see the correct value using the _satellite.getVar('Search_Term').  It is most likely the latter - Maybe the input box disappears as soon as the search is performed (so the Data Ele...

I have a data element that captures the Search_Term when users types it in the search bar. The data element is using Core - DOM Attributes:  The rule is triggered via custom events when a user conducts a search action.  When I type in the search bar and use the _satellite.getVar('Search_Term') I get...

Not only did this help, it also addressed some issues that I had not yet discovered. Kudos!

I am updating an existing implementation that uses a colon delimiter. One of the fields we have is a text field which captures the texts of various items some of which are article names. The issue is some article titles have a colon which is throwing off the existing rule. Here is the expression I a...

Thank you for confirming. I have confirmed that the hits are going into analytics as we have hit IDs & other IDs I can see coming into the report suite.  How can I open a ticket with client care if that is the case? 

What is off-putting to me is that other rules that have a similar setup are firing and the debugger is working for those. Its only these two rules that are causing this issue.  The debugger is only capturing some Adobe default attributes. The debugger is clearly showing that there is a hit but the v...

Thank you for your response.  We can rule a few things out based on what you asked to confirm. 1) There are other rules that are based on the same custom events that are tracked and the data is flowing to the debugger without issues. 2) All the server domains are the same so if one is working the ot...