Hi Matt, can you provide a little more detail about what you're trying to accomplish? Are you trying to suppress the initial page view (s.t)? If not, which event is firing that you would like to suppress? There are many potential ways to accomplish something like this so in order to give you the best possible answer, we would want some more information on your specific use case. If it's not possible to share pertinent details here then I'd recommend reaching out to your account manager to discuss the challenge in depth.
Hi Clint -
Thanks for the response. I am trying to prevent a custom event from being assigned to the s.events and s.products variables for specific pages (i.e.: product detail pages, cart pages, etc.). This specific custom event should ONLY fire on a particular page (the Order Confirmation page), but right now it is firing on other pages as well.
For example, if I land on a product detail page, there is a custom event (I will call it eventXX) that is being assigned to the s.products and s.events variables when I don't need it to be.
I hope that is a bit more specific.
Thanks Matt, the detail is very helpful. I've asked one of our Solution Engineers to weigh in here because this is not a scenario I have personally run across and I'd rather someone more knowledgeable answer the question.
Keep in mind that if a data source is mapped to the event then anytime the data source contains a value the event will get set. In this case you can add a Set Data Values extension and set a condition to only set the data source when necessary. If the event is getting triggered via an extension, a condition may be needed or updated in the extension.
I can give more specific details if you can provide the account/profile you are working in and the event number that you're trying to prevent from firing?