Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Integrate Third-Party Libraries Using the Privileged Script Tag

Some components within an LWR site encapsulate their elements in shadow DOM, which prevents global interaction with those components. As a result, third-party JavaScript libraries such as Google Analytics and Google Tag Manager can have trouble querying the DOM globally on an LWR site. When programmatic access to an element within the DOM is needed, you can write scripts within an <x-oasis-script> privileged script tag. Loading third-party libraries using this privileged script tag lets those libraries bypass any shadow DOM boundaries.

Use the custom <x-oasis-script> tag in place of the standard <script> in the head markup or inline. Scripts loaded within this custom tag run inside a special iframe that’s exempt from shadow DOM and are always executed asynchronously.

<x-oasis-script> uses the same syntax as the <script> tag.

1<x-oasis-script src="third_party_library.js"></x-oasis-script>

You can also use the tag to add event listeners and to import and export global variables with the imported-global-names and exported-global-names attributes. If you have custom code within the <x-oasis-script> tag, add the attribute hidden="true" to the tag. This attribute ensures that the custom code within the tag remains hidden from site visitors while the page is loading.

For example, this code sample defines a global variable—testVar—on the outer window, which is then imported for use in the x-oasis-script window. The global variable must be imported to define it in the privileged scope.

1<script>
2    window.testVar = "myTestVar";
3</script>
4
5<x-oasis-script hidden="true" imported-global-names="testVar">
6    // Custom code to access testVar
7    console.log(window.testVar)
8</x-oasis-script>

In turn, this example exports the testVar global variable from x-oasis-script.

1<x-oasis-script hidden="true" exported-global-names="testVar">
2    window.testVar = "myTestVar";
3</x-oasis-script>
4
5<script>
6    // setTimeout is needed in case this script tag is run before oasis script
7    setTimeout(function(){
8      // Custom code to access testVar
9      console.log(window.testVar)
10    }, 5000);
11</script>

If you include a third-party library inline or in the head markup, remember to switch to Relaxed CSP and to allowlist the remote host.

Tip

LWR Sites for Experience Cloud

Integrate Third-Party Libraries Using the Privileged Script Tag

See Also