> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.hoppyapps.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# 🔗 Integrate Hoppy Cookie with Transparency & Consent Framework v2.3 (TCF)

The Transparency & Consent Framework v2.3 (TCF) integration helps your store communicate consent signals to IAB-registered vendors in a standardized way.

When enabled, Hoppy Cookie generates and manages a valid TCF consent string (TC String), exposes the official `__tcfapi` interface, and shares visitor consent preferences with participating advertising and analytics vendors.

Hoppy Cookie is already registered as an IAB Consent Management Platform (CMP ID: 454), so no additional registration or external setup is required.

---

# **⚠️ Before You Begin**

Before enabling TCF, make sure:

* Hoppy GDPR EU Cookie Banner is installed and active  
* Your Cookie Banner is published  
* The App Embed is enabled inside your Shopify theme

💡 No API keys, credentials, or external accounts are required.

⚠️ TCF only applies to visitors located in GDPR regions.

If you plan to use **Google Consent Mode V2** for GDPR traffic, TCF should be enabled first.

---

# **🛠️ Step 1 — Open the Integrations Section**

Inside your Shopify Admin:

→ Open **Hoppy GDPR EU Cookie Banner**

→ Click **Integrations**

Locate:

**Transparency & Consent Framework v2.3 (TCF)**

and open the integration page.

---

# **🚀 Step 2 — Enable TCF**

At the top of the page:

→ Click **Turn On**

Once enabled:

* The integration status changes to **On**  
* The app loads the IAB Global Vendor List (GVL)  
* The storefront begins exposing the `__tcfapi` interface  
* GDPR visitors receive a TCF-compatible consent experience

💡 The banner and preferences popup automatically adapt to the TCF structure when required.

---

# **🧩 Step 3 — Select Collaborating Vendors (Optional)**

Below the integration toggle, you'll find the:

### **Search Vendors**

field.

This allows you to choose which vendors from the IAB Global Vendor List are allowed to receive consent signals.

### **How to Add Vendors**

→ Start typing a vendor name

→ Select the vendor from the results

→ Repeat as needed

### **How to Remove Vendors**

→ Click the **×** next to the vendor name

to remove it from the selected list.

---

### **Important Behavior**

If no vendors are selected:

→ All vendors from the Global Vendor List are allowed by default.

For most merchants, selecting only the vendors actively used on the storefront is recommended.

This helps keep consent communication more accurate and easier to manage.

---

# **💾 Step 4 — Save Your Changes**

After enabling TCF and selecting your preferred vendors:

→ Click **Save**

The app will:

* Store your TCF configuration  
* Update storefront settings  
* Republish the necessary banner configuration

Once saved, the storefront begins using the updated TCF settings automatically.

---

# **🔄 How TCF Works**

After activation, the consent flow works automatically for GDPR visitors.

### **What Happens Behind the Scenes**

1. The app loads the latest IAB Global Vendor List  
2. Visitors interact with the TCF-compatible consent banner  
3. Consent choices are converted into a TC String  
4. The TC String is stored on the storefront  
5. Consent signals are shared through the `__tcfapi` interface  
6. Participating vendors adjust behavior based on the granted permissions

This process happens automatically without requiring any manual intervention.

---

# **🧪 Step 5 — Verify the Integration**

After saving, it's recommended to verify that TCF is working correctly.

---

## **Check the Integration Status**

Return to:

**Integrations → Transparency & Consent Framework v2.3 (TCF)**

The status badge should display:

**On**

---

## **Test from a GDPR Region**

Because TCF only applies to GDPR visitors:

→ Test using an EU VPN location

or

→ Use available Shopify testing tools for regional storefront behavior

The TCF consent experience should appear automatically.

---

## **Verify the TC String**

After submitting consent preferences:

→ Open your browser's Developer Tools

→ Check browser cookies

Look for:

euconsent-v2

You may also find the same value stored in localStorage.

Its presence confirms that a valid TC String has been generated and stored.

---

## **Verify Vendor Behavior**

If specific vendors were selected:

→ Confirm those vendor scripts load correctly

→ Verify they respond appropriately to consent selections

If using Google Consent Mode V2 alongside TCF, test both integrations together to ensure consent signals are flowing as expected.

---

# **⚠️ Common Troubleshooting**

## **TCF Banner Is Not Appearing**

Verify:

* The visitor is located in a GDPR region  
* The Cookie Banner is published  
* The App Embed is enabled

TCF functionality only activates when GDPR requirements apply.

---

## **Vendor List Is Not Loading**

The Global Vendor List is cached temporarily for performance.

If vendors do not appear:

→ Refresh the page

→ Wait a few minutes and try again

→ Verify your storefront can access the vendor list service

---

## **Vendors Are Ignoring Consent**

Verify:

* The correct vendors were selected  
* The vendor supports the `__tcfapi` interface  
* The vendor is registered within the IAB framework

TCF only affects vendors that participate in the framework.

---

## **Google Consent Mode V2 Is Not Working**

TCF is required for Google Consent Mode V2 in GDPR regions, but it does not configure Google Consent Mode automatically.

After enabling TCF:

→ Configure Google Consent Mode V2 separately from the Integrations section.

---

# **⚠️ Important Notes**

### **GDPR Regions Only**

TCF applies only to visitors located within GDPR-covered regions.

Visitors outside those regions continue using the standard consent experience.

---

### **Empty Vendor List Allows All Vendors**

If no vendors are selected manually:

→ All vendors from the Global Vendor List are allowed by default.

---

### **Consent Is Stored Automatically**

The generated TC String is stored automatically and reused according to consent requirements.

No manual cookie configuration is necessary.

---

### **TCF Is Required for Google Consent Mode V2**

For GDPR visitors, Google Consent Mode V2 depends on TCF being active.

TCF should always be configured before enabling Google Consent Mode V2.

---

# **🎉 Final Result**

Once configured successfully:

✅ GDPR visitors receive a TCF-compliant consent experience

✅ Consent choices are converted into a valid TC String

✅ The `__tcfapi` interface becomes available on the storefront

✅ IAB-registered vendors receive standardized consent signals

✅ Vendor permissions can be controlled directly from the app

✅ Your store is ready for Google Consent Mode V2 and other TCF-compatible services

The Transparency & Consent Framework v2.3 integration helps ensure consent information is communicated in a standardized format that major advertising and analytics vendors can understand and respect. 🔒

---