Adobe Target XF are getting gated by Consent Platforms due to Adobe RUM script | Community
Skip to main content
Kshg7030
Kshg7030
Level 2
February 3, 2026
Question

Adobe Target XF are getting gated by Consent Platforms due to Adobe RUM script

  • February 3, 2026
  • 1 reply
  • 22 views

Hi All,

We have an Adobe Analytics + ECID + Target integration on our site which is implemented via Adobe Launch Data collection and Target is using the Target v2 extension. We have a consent partner for managing cookies and consent. We have already put all target related cookies under strictly necessary to deliver the user experiences.

However, Target XF are showing blank spaces on page until user accepts the Analytics cookies from the consent banner.  Upon further investigating this, we found that the Setup in launch is using the Pre-hiding snippet from a load rule to manage Flicker on site while Target is rendering. Also with this, the Consent Partner is blocking the “Adobe rum” script which is causing the XF to not load and the white space to show on site due to the pre hiding snippet from launch.

We are unsure as how to manage this effectively while maintaining compliances with GDPR policies. For now, we think we can allow the ‘RUM’ script which will load the XF without user consent, but not sure if this will break any compliance issue or cause and issues further down the line. Also, can anyone suggest how to use the pre-hiding snippet Load request in launch so this can be avoided in future

Script - https://rum.hlx.page/.rum/@adobe/helix-rum-js

Pre-Hiding Snippet Load rule Action - 

 

1 reply

Gokul_Agiwal
Community Advisor
Gokul_AgiwalCommunity Advisor
Community Advisor
February 3, 2026

Hi ​@Kshg7030 -  quick question, 

  1. Which consent platform you're using
  1. how come Target classified under strictly necessary cookies category? 
Kshg7030
Kshg7030Author
Level 2
February 4, 2026

Hi Gokul,

  1. We are using Osano as consent platform.
  1. The target mbox and at.js cookies are categorized under necessary by the consent partner in order to deliver user experiences to targeted users, so that the XF are not blocked or gated by user consent and we can show them the desired content based on the audiences segmented.

I hope this answers your concerns. 

Gokul_Agiwal
Community Advisor
Gokul_AgiwalCommunity Advisor
Community Advisor
February 4, 2026

Thank you for the answers. 

What I understood now is that, the your launch rule inject the pre-hide snippet and same time your CMP platform blocking the Adobe RUM script. 

 

then let’s talk about Pre-hide snippet first - 

So as per Adobe guidance,  If you load at.js via a tag manager, which is also loaded asynchronously, you must add the snippet before loading the tag manager. 

so move prehide logic out of Launch rules and add into a head section directly or in external JS file  
For more info https://experienceleague.adobe.com/en/docs/target-dev/developer/client-side/at-js-implementation/at-js/manage-flicker-with-atjs#managing-flicker-when-loading-atjs-asynchronously 

 

About RUM Script - Why CMP blocking? 

AEM expert can answer better here about RUM script but if your CMP blocking rum script, considering as 3rd party script / tracking script. Whether this to be classified as strictly necessary depends on your use case and what this script does exactly in your setup, please check

GDPR Concerns : 

Ideally, consent is generally required for non-essential cookies/trackers, but not needed for “strictly necessary” cookies. 

So in your use case, are you sure that you want Adobe target cookies classified as strictly necessary? 

FYI - Adobe target support opt-in functionality via tags so you control when Target fires based on consent. If your consent model says “Target is strictly necessary,” you may fire Target immediately; if not, gate it. 

https://experienceleague.adobe.com/en/docs/experience-platform/tags/extensions/client/target-v2/overview#atjs-settings 

last thing - how Target XF delivered? Are you exporting XF from AEM?  

Thanks

Terms & ConditionsAccessibility statement

Loading footer...