Aborting all analytics server call

Question

Hello Analytics Experts,I hope everyone is doing well. I have a scenario question, is there a way to abort all server calls when a certain condition doesn't meet? I know that Adobe has s.abort(), but this option will only work in certain conditions. I am exploring the possibility that if a user opt-out, all server calls will be aborted. I know that we have some extensions like ECID, but I am trying to avoid using any of the extensions.Question:Is there a way to create a condition in Launch that when the user opt-out, all server calls will be aborted, and when I opt-in, then, that is the time when the beacons start to fire again? I don't know if there is a way to inject a Global Privacy Setting like "navigator.globalPrivacyControl" or "Sec-GPC:1", but seems like this is browser-specific only. Hoping that there is a way to implement it from the Client side (adobe). I hope this question makes any sense.Thank you in advance.

Jennifer_Dungan · Accepted Answer

Thanks for the insights, @bjoern__koth and @jennifer_dungan.

I do have 1 follow-up question, does s.abort also prevent the target call or Google floodlight?

Since our rules contain a floodlight tag, I am under the impression that even if we prevent the beacons from firing, the 3rd party tag will still continue to trigger.

Have you encountered any scenarios that could also prevent the 3rd party call from firing when certain conditions are met? if yes, would you mind sharing the solutions you did?

Thanks in advance 🙂

Hi @herder,

the s.abort only affects Adobe Analytics (since it affects only the s object which is used exclusively by Analytics).

This is another reason why adding conditions to your rules is the better option. Conditions stop the entire rule from triggering.

Let's say your rule looks like this:

(You have a trigger: Dom Ready; and 3 actions: Set Variables, Sent Beacon and your Floodlight code)

Right now, all of these will run when the DOM is ready.

But, let's add a condition:

Now, when the DOM is ready, it must first pass my condition that analytics is opted in...

In my example, I am using the opt-in configuration I set up in my ECID extension:

Here, I explicitly set Analytics Opt-in to "false" as my previous value, but in a real scenario I would be using data elements to extract the user's chosen opt-in status based on whatever the site is using to control your opt-ins.

Jennifer_Dungan · Answer

You can create a condition on your rules that won't even let the rule run if the user hasn't opted in.  While you do have to add that to all your rules, this would be more efficient on the site performance since you wouldn't even run the code if the user isn't opted in.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded