🚀 New: Boost your SEO with SchemaForge – Our free JSON-LD generator for modern stacks. Check it out →

Technical Docs & FAQ

Single source of truth for technical integration, Google Tag (GTG) rules, banner standards, and Frequently Asked Questions.

1. Google Consent Mode v2 Setup (Basic vs. Advanced)

CookiePrime provides native support for Google Consent Mode v2 across all 4 mandatory consent signals: ad_storage, analytics_storage, ad_user_data, and ad_personalization. Note that Google Consent Mode is a technical signal transmission layer and is not intended to replace or solve for any single regulatory requirement on its own.

Basic vs. Advanced Configuration

A. Basic Consent Mode (Tags Blocked Before Consent)

In Basic Consent Mode, Google tags (such as Google Analytics 4, Google Ads, or Floodlight) are completely blocked from loading or executing on the page until the user explicitly interacts with the banner and provides affirmative consent.

  • Page Load: No Google scripts are loaded. No pings or cookies are sent.
  • On Consent Grant: CookiePrime unblocks the scripts, triggering gtag('consent', 'update') followed by a cookie_consent_updated event in the DataLayer to fire the tags.
  • Best For: Strict opt-in jurisdictions where unconsented pings are prohibited.

B. Advanced Consent Mode (Tags Unblocked / Cookieless Pings Enabled)

In Advanced Consent Mode, Google tags load immediately when the page loads, but they initialize with all consent signals set to denied.

  • Page Load: Google tags issue cookieless, anonymized pings for measurement.
  • On Consent Grant: CookiePrime issues a gtag('consent', 'update') command updating signals to granted. Tags then transition seamlessly to collecting full analytics and advertising data.
  • Fallback Window: Initialized with a default fallback window (wait_for_update: 500ms) to prevent data loss.

C. Disabling or Switching Consent Mode Commands

Advertisers can easily switch between Basic and Advanced mode or completely disable Consent Mode commands through the CookiePrime Graphical Dashboard (under Banner > Google Consent Mode) or via script attributes:

  • To Enable Advanced Mode: Set data-advanced-mode="true" and data-wait-for-update="0" on the loader script, or select "Advanced Mode" in the UI.
  • To Revert / Disable Consent Mode Commands: Set data-consent-mode="false" or disable Consent Mode in the UI. CookiePrime will immediately fall back to hard script blocking without issuing gtag() commands.

2. Google Tag (GTG) & Script Load Order Rules

Proper execution order is critical to ensure Google Consent Mode signals are set before tags process user data.

Google Tag (GTG) & Load Order Rules

What is Google Tag (GTG)? GTG is Google's unified tagging framework (used by GA4 and Google Ads) that automatically detects consent state on the page.

⚠️ CDN Injection & Load Order Warning

Automated "one-click" CDN script injection offered by various CMS platforms or plugins often strips customer control over execution order. If Google Tags fire before the CMP sets its default consent state, signals will be flagged as "late."

Mandatory Requirement: The CookiePrime script (or the CookiePrime GTM Template default command) MUST load and execute BEFORE any Google Tags fire on the page.

How to Verify if a Tag is Enrolled in GTG

  1. Open your website in Google Tag Assistant or open your browser's Developer Tools Console (F12).
  2. Inspect the network pings sent to google-analytics.com/g/collect.
  3. Look for the gcs (Google Consent Status) and gcd parameters in the request URL payload. If present, the tag is enrolled in GTG.

3. Debugging Mode & Troubleshooting Late Signals

CookiePrime provides an interactive Debugger to verify script load order and proactively flag configuration errors.

Interactive Debug Mode

Site administrators can verify their setup interactively by appending ?cookieprime_debug=true to their URL or opening the browser console (F12). The console will display real-time execution logs:

[CookiePrime] ✅ Default consent state set (ad_storage: denied, analytics_storage: denied)
[CookiePrime] ✅ Developer ID set in dataLayer: dMjJjND
[CookiePrime] ⚖️ Framework Resolved: STRICT_OPT_IN (Region: EU)
[CookiePrime] ✅ Consent mode updated on user action

Troubleshooting "Late" Consent Signals

If CookiePrime Debug Mode or Google Tag Assistant flags a consent command as "Late" (meaning Google tags fired before the default consent command was set):

  1. Step 1: Verify GTG Enrollment: Check if the tag flagging the late signal is enrolled in Google Tag (GTG).
  2. Step 2: Adopt Advanced Consent Mode (U+C): If GTG enrollment is verified, CookiePrime strongly recommends migrating the customer site to Advanced Consent Mode (U+C), enabling Data Transmission Controls and Global Consent Defaults according to their region's legal requirements. Advanced Consent Mode is the recommended mechanism for GTG-enabled tags because it natively supports cookieless pings prior to consent update calls.
  3. Step 3: GTM Migration or Manual Script Reordering: Alternatively, migrate all tags into a single Google Tag Manager container deployed via GTG, or manually reorder on-page scripts so that the CookiePrime snippet / GTM container is placed at the absolute top of the <head> element.

5. Multi-Platform Deployment Guides

Deploy CookiePrime across Google Tag Manager, WordPress, Shopify, BigCommerce, or Custom HTML setups.

A. Google Tag Manager (GTM) Template

Deploy CookiePrime codelessly via our custom GTM Tag Template.

  1. Download the official CookiePrime GTM Template definition file below.
  2. Open your Google Tag Manager dashboard container, go to Templates, click New under Tag Templates. To publish the template, click on the 3 dots (More menu) and select Import. Upload the downloaded `.tpl` file and save.
  3. Go to Tags, click New, and select the newly imported CookiePrime CMP definition block. Enter your unique API Key.
  4. Banner Trigger: Set the tag trigger to fire on Consent Initialization - All Pages. This ensures the banner fires first on all pages before any tracking occurs.
  5. Analytics Trigger: Ensure your analytics and marketing tags (e.g., GA4, Facebook Pixel) are set to trigger on standard All Pages (NOT Initialization) so they do not interfere with the banner.
  6. Save your configurations, then click Submit and Publish your workspace.
Download GTM Template (.tpl)

B. BigCommerce App

Secure your BigCommerce storefront with automated, seamlessly integrated privacy enforcement.

NOW LIVE IN BIGCOMMERCE APP STORE

  1. Search for CookiePrime in the official BigCommerce App Marketplace.
  2. Install the app and authorize the connection to your store.
  3. Follow the guided onboarding to select your banner template.
  4. Your store will automatically inject the required compliance scripts without any manual coding.

C. WordPress Plugin (WP Consent API & SiteKit Support)

Integrated natively with the WP Consent API. Download our official CookiePrime WordPress Plugin.

  • Install the CookiePrime WordPress Plugin via Plugins > Add New.
  • Enter your API Key under Settings > CookiePrime.
  • Our plugin registers with WP Consent API to guarantee that SiteKit and other Google tags receive default consent states before firing, regardless of active theme or caching plugins.

D. Shopify App (Customer Privacy API)

Integrated natively with Shopify's Customer Privacy API.

NOW LIVE IN SHOPIFY APP STORE

  • Search for CookiePrime directly within the Shopify App Store.
  • Install the app to authorize the connection.
  • Our app hooks directly into Shopify's Customer Privacy API to automatically synchronize buyer consent signals with Google Consent Mode and your storefront analytics pixels.

E. Custom HTML Script Injection

Paste the loader snippet at the absolute top of your <head> element:

<!-- CookiePrime Privacy Engine -->
<script src="https://storage.googleapis.com/cookieprime_bucket/public/loader.js" data-id="YOUR_API_KEY"></script>

6. Support Policy & Service Level Agreements (SLAs)

⚠️ Troubleshooting Direction Notice

IMPORTANT: All clients and website administrators implementing CookiePrime must direct initial troubleshooting inquiries regarding Consent Mode, missing GTM signals, or banner behaviors to **CookiePrime Support FIRST**, rather than Google.

Google Support requires proof of prior contact and escalation with CookiePrime Support before investigating tagging discrepancies on client sites.

Staffed Support Coverage & SLAs

CookiePrime provides staffed technical support covering Consent Mode v2 implementation, banner GUI customization, script interception, and continuous troubleshooting:

  • Support Channel: Contact Form & Email (contact@cookieprime.com)
  • General Customer Support Response SLA: Initial technical response within **4 business days (96 hours)**. All initial responses are technical and actionable, not automated blanket receipts.
  • Dedicated Google Escalation POC Response SLA: Technical point-of-contact (POC) escalation turnaround within **2 business days**.
  • Escalation POC Email: samir.moukhliss@cookieprime.com

7. Frequently Asked Questions

Find answers to common queries about CookiePrime, multi-platform integrations, and mobile privacy infrastructure.

General

Web Consent

Mobile SDK

Compliance

Billing & CMS

What is CookiePrime?

CookiePrime is a high-performance consent management infrastructure built specifically for developers. We deliver automated cookie auditing, geographic-aware responsive banner themes, and advanced compilation interception code scripts for native mobile platforms.

How does the web free trial operate?

Our website consent trial runs completely unrestricted for 10 days. No credit card strings or billing fields are required—all you need to connect is a valid development email interface.

How do I embed CookiePrime into my core HTML template?

Paste our unified script element as the absolute first node inside your website's main <head> block:

<!-- Global CookiePrime Integration -->
<script src="https://storage.googleapis.com/cookieprime_bucket/public/loader.js"
    data-id="YOUR_DOMAIN_ID"></script>

Replace the data-id string with the real token generated inside your client dashboard.

Can I distribute configurations via Google Tag Manager?

Yes. We provide a lightweight, secure custom .tpl Tag Template container. Importing this template into GTM cleanly activates Google Consent Mode v2 variables and schedules dataLayer hooks automatically without forcing manual block writing into your source templates.

What makes the Mobile SDK unique? EARLY ACCESS

Unlike standard web wrappers that try to block tracers at the network layer, our lightweight 420KB Kotlin library utilizes deep class loading and DEX compilation analysis. It catches and intercept tracking payloads exactly at their instantiation runtime phase.

What is the newly added Package Whitelisting feature?

Package Whitelisting lets engineers protect trusted modules or internal application monitoring libraries from default blocking loops. By adding specific class namespaces to your whitelisted configuration array during initialization, those packages are completely skipped by the automated interceptor loop, guaranteeing uninterrupted execution.

Which libraries can the dependency scanner analyze?

The compiler trace logs comprehensively scan for over 27+ industry-standard SDK signatures out-of-the-box. This includes full detection for Firebase Analytics, the Facebook SDK, Google AdMob, and AppsFlyer, alongside deep category sorting for variables like crash_reporting and anonymous pattern trackers.

What is Cryptographic Consent Auditing?

For high-risk environments, every single user transaction state change generates an immutable SHA-256 ledger token locally inside the sandbox. This tamper-proof audit trail creates secure proof of interaction that helps operators easily verify compliance metrics for regulatory inspections.

What if I encounter Google Consent Mode update warnings?

If you see tag latency drops or signal matching faults during testing, please **contact our support engineers first at support@cookieprime.com**. We will analyze your container and template lifecycle values to fix any mapping errors quickly.

How does licensing scale on Shopify & BigCommerce stores?

Stores utilizing our native App Store integrations on Shopify or BigCommerce are enrolled in a unified, flat-rate Professional plan at $6.00/mo.

Why must Shopify and BigCommerce subscription billing pass through their platform?

Per strict App Store regulatory ecosystem guidelines, all software subscriptions, application charges, and license matrices must be securely executed via the native **Platform Billing APIs**. External payment processing gateways are entirely restricted for native app store setups.

Does Wix require special parameters to load the banner?

Yes. Wix requires your site layout to operate on a **Premium Subscription Plan with a connected custom domain**. Free Wix site frames (such as standard `.wixsite.com` URLs) block external script injection scripts completely, which stops consent banners from loading.