Skip to content

Shopify Integration

Last updated: November 3, 2026

This installation uses the shared Web CMP runtime, which supports IAB TCF 2.4. TCF behavior depends on the published property configuration; verify the actual installation and connected tags.

Use the Cybexo CMP theme app embed to connect a Shopify storefront to CYBEXO. The embed provides early IAB TCF initialization and connects the shared Web CMP to Shopify’s Customer Privacy API. The app works without Google Tag Manager: enable the embed, enter your CYB App ID, and keep the default Shopify App (no GTM) option. The optional GTM route is for stores that choose to use GTM.

  1. Open the CYBEXO dashboard and create an App for your Shopify storefront.
  2. Add the storefront domain and configure the banner’s regions and privacy options.
  3. Enable Google Consent Mode and configure the IAB TCF options required by your implementation.
  4. Copy the real CYB App ID, beginning with CYB-.

A retired App ID must be replaced with a new CYB App. Changing an old ID’s prefix does not migrate it.

  1. Install or open Cybexo CMP in Shopify.
  2. Go to Online Store → Themes → Customize → App embeds.
  3. Enable Consent management under Cybexo CMP.
  4. Paste the CYB App ID.
  5. Keep Shopify App (no GTM) under Setup mode and leave the GTM container ID empty.
  6. Save the active theme. Test the storefront’s banner, saved choices, Shopify categories and any Google tags as described below.

The app supplies early denied Google defaults, loads the single managed loader.js and sends consent updates. Keep Consent Mode enabled in CYBEXO. No additional CMP loader or Google consent snippet is needed. The app does not install Analytics or advertising tags, and merchants do not select an engine release.

Select Google Tag Manager in the embed and enter your GTM container ID. Install the current CYBEXO CMP Gallery template in that container, use the same CYB App ID, and trigger one CMP tag on Consent Initialization – All Pages. Preview and publish the container. The embed loads it; remove duplicate container installations and competing consent writers.

The template recognizes Shopify, sets defaults through GTM’s native consent APIs and loads the shared CMP. Existing stores retain their selected mode. Switching modes requires coordinating the embed and tags, removing the prior installer and consent owner, and testing a fresh visitor.

The cybexo.settings_id shop metafield takes priority when present. The embed keeps its existing setting key during upgrades, but the saved value must be a current CYB App ID.

Keep one consent installation per storefront. Remove an older direct loader, a duplicate container installation, or a competing CMP before enabling this embed. The one configured CYBEXO GTM tag is required for Google Tag Manager mode. Adding the standalone Web loader alone does not provide this Shopify consent adapter.

The merchant setup guide provides the same steps in the app’s onboarding page.

In Settings → Customer privacy, configure consent regions to match the regions where the CYBEXO banner collects consent. Use one storefront cookie banner and avoid a competing Shopify banner.

Configure Shopify’s data-sale opt-out page and Global Privacy Control behavior independently for applicable regions. The CYBEXO embed does not replace that separate flow.

Shopify category CYBEXO mapping
Analytics The independent Analytics preference must be permitted, together with the effective Google Analytics consent gate.
Marketing All three Google advertising signals—ad_storage, ad_user_data, and ad_personalization—must be granted.
Preferences The same conservative personalization gate as Marketing. TCF does not provide a separate Shopify preferences category.
Sale or sharing Owned by Shopify’s independent data-sale opt-out and GPC flow. Generic Accept All, Reject All, and TCF customization leave sale_of_data unchanged.

A completed visitor choice records the mapped categories through Shopify’s granular API. Initial loading, regional defaults, and ordinary restoration do not create new Shopify decisions. A completed choice made in another open tab is synchronized to the current tab, including Shopify categories, without creating another CYBEXO decision or receipt. Shopify’s yes, no, and empty states are handled distinctly; the adapter does not read or write Shopify cookies directly.

If a stored CMP choice expires or becomes invalid, Shopify may retain an earlier platform choice. When Shopify’s Customer Privacy API is available, the adapter exposes this difference for review and waits for a fresh visitor decision. It does not fabricate a new platform decision during page load.

The app embed uses Shopify’s compliance_head placement for early TCF initialization and the Shopify adapter. In Google Tag Manager mode, the embed loads the configured container; the CYBEXO template owns denied defaults and updates through GTM’s native consent APIs and loads the shared CMP. Keep the CMP tag on Consent Initialization, and load measurement only after native defaults. Avoid an additional consent writer in a theme, app, Google channel or custom pixel.

In Shopify App (no GTM) mode, the embed supplies the early Google defaults and starts the shared loader itself. Place direct measurement after that bootstrap. Shopify’s extension placement cannot move scripts already earlier in the theme’s head; verify the emitted page order. Verify this mode on its own storefront and tags; a successful GTM test does not verify app-only delivery.

Updates use the effective consent state after a completed visitor action. Repeated notifications are deduplicated. Delayed Shopify API availability retains the newest completed choice, writes are serialized, and retries are bounded. An invalidated choice cancels pending work. Failure is reported rather than represented as a successful platform update.

These read-only checks help diagnose the integration:

window.CybexoShopifyBridge?.status()
window.Shopify?.customerPrivacy?.currentVisitorConsent?.()

A synced status confirms the adapter’s platform readback for the last choice. review with platform-choice-needs-review means the CMP requires a fresh decision while Shopify retains an earlier grant. An error requires investigation; make a new explicit choice after correcting a temporary delivery problem.

Scenario Expected result
Fresh visitor in a consent-required region One banner; early TCF API and all four Google consent types initially denied; no fabricated Shopify decision.
Accept All Permitted Google signals and the corresponding Shopify categories update after the choice.
Reject All Google consent and mapped Analytics, Marketing, and Preferences categories are denied. Independent sale/share remains unchanged.
Withdraw advertising personalization Marketing and Preferences are denied; a separately permitted Analytics choice remains independent.
Withdraw Analytics Analytics is denied while other permitted choices remain intact.
Reload and reopen settings The CMP restores the visitor’s current choice without recording a new Shopify choice merely because the page loaded.
Temporary API or runtime failure No invented grant; errors remain visible and a new explicit decision can recover after the problem is fixed.

Use Google Tag Assistant to verify that denied defaults are processed before your Google tags initialize, then check the effective consent state after acceptance and withdrawal. Confirm the actual emitted HTML order as well. A data-layer entry alone does not prove that a tag received or enforced the expected consent state. Run Runtime Verification as an additional installation check.

Theme app embeds run on the online storefront, not Shopify checkout pages. Checkout and Shopify pixels use platform-managed environments. Verify each configured integration against Shopify’s customer privacy settings; do not assume the parent storefront’s scripts run inside a pixel sandbox or checkout.

Consent signals do not install or automatically control every third-party tag. Configure each tag or pixel to use its supported consent integration, and test both acceptance and withdrawal. A working integration is separate from any formal Google or IAB certification.

See Shopify’s Customer Privacy API and theme app extension configuration for the platform contracts.

Issue Check
Banner missing Active theme, enabled embed, current CYB App ID, storefront domain, regional settings, and existing saved choice.
Duplicate banner or blocked initialization Remove the competing CMP, old direct loader, or duplicate tag-manager installation.
Shopify categories do not change Inspect bridge status and API availability; complete a new explicit choice after correcting the problem.
Google tags disagree with the banner Check effective consent and tag order in Tag Assistant, including each Shopify pixel integration.
Upgrade retains an older App ID Create a current CYB App and update the saved embed value. Do not rename an old ID or install a second loader.