Adding the snippet
Add the runtime through Script Manager, scoped to the intended storefront pages and placed early enough for registered gating. Script Manager lists the entries managed through that feature, including their location and scope, but it is not an inventory of code embedded in the theme, checkout or an app’s separate delivery path.
Script Manager, head, all pages
<script
src="https://strongprivacy.com/embed/v1.js"
data-site-id="YOUR_SITE_ID"
data-api-base="https://strongprivacy.com"
data-privacy-url="/privacy"
data-platform="custom"
defer
></script>Use Script Manager as your audit list
- Review every Script Manager entry and assign its consent category from its actual purpose
- Entries scoped to checkout are a separate surface with their own constraints
- Apps installed from the marketplace often add their own entries; those are the ones to look at first
- A scan of the live storefront is still required: Script Manager shows intent, not behaviour
Common questions
Does the snippet apply to checkout?
Checkout is a separate surface with platform constraints on what can run. Scope deliberately, scan it separately, and be clear in your declaration about which cookies belong to the platform.
Sources and verification
Verified on . Product-behaviour statements were checked against the current implementation and tests. The links below are the verification basis recorded for this article. They support the stated facts, not a legal conclusion for every site or configuration; recheck changing vendor behaviour before relying on it in production.
- BigCommerce: Scripts API and Script Manager
Vendor documentation
Checked
- StrongPrivacy custom-site installation guide
Product documentation
Checked
See what your own site is loading
A browser scan reports the requests and storage it observed during the sampled journey. Use configured workspace scans to compare the states and pages that matter to your implementation.