How to load s object but not make a server call (Launch/AA/AA ext.

[MichaelJo4]

We are doing some One Trust cookie consent work. On some of the sites they want the s object to load but not make a server call. We are using Launch, AA ext. All of the rules are blocked from executing. Assuming using something like s.abort = true; somewhere might work but not sure where to put it? Any ideas on any approach at all??

Thanks,

MJ

[yuhuisg]

Server calls are sent to AA only when you use the "Send Beacon" action from the AA extension in any rule. So if you don't want to send server calls, ensure that none of your rules use that action. If you do have such rules, disable them or delete the specific "Send Beacon" action from them.

[leocwlau · Accepted solution]

We are also interested to implement OneTrust but have not started yet, so it is not answering directly to OneTrust implementation but generally the AA library loading and tracking.

Since you are using Adobe Launch and the Adobe Analytics extension, the "s" object is loaded automatically by Adobe Launch when the page is loaded and executing the Launch JS.

As @yuhuisg tracking happened only by the "Send Beacon" action, or calling s.t()/s.tl() function.

From your mention of s.abort=true, you can use that to stop data from being sent to Adobe if you had the "Send Beacon" or called s.t/s.tl. You can go to the Adobe Analytics extension, configure tracker using custom code, and then define the s.doPlugins function to set s.abort=true according to an indicator you have on the page to stop tracking right before data sending out.

You can find an exact example at abort | Adobe Analytics.

[Jennifer_Dungan]

@yuhuisg and @leocwlau did a great job talking about not triggering the beacons - s.t() and s.tl() 

But I just wanted to add one more piece.. I would expect that for your consent model, that you should be able to use Conditions on your rules... rather than attempting to abort the process.

Basically, run the consent model first.. if the user accepts tracking, then the condition should be set up to allow the rules to run... if the user doesn't accept, then the condition should stop the rule from running completely.

You would only add these conditions to your tracking rules, and things that can't run without permission... but base items would still run.