Important notice
The Classic Experience will be sunset on
Aug. 1.
If you have questions, contact your Customer Success and Implementation Manager,
Account Manager, or
support@trustarc.com.
Webflow is a no-code visual development platform that allows users to build responsive websites, landing pages, and e-commerce stores without writing code. It functions like a graphic design tool, enabling drag-and-drop design while automatically generating clean, semantic HTML, CSS, and JavaScript behind the scenes.
This guide provides guidance on how to integrate the TrustArc Cookie Consent Manager into a Webflow website. It is designed to walk users through the configuration, deployment, and verification of the consent banner to ensure compliance with privacy regulations.
By integrating TrustArc Cookie Consent Manager with your Webflow site, you can:
What you can do
✓Automatically inject cookie banners into your site
✓Manage and update privacy configurations via TrustArc
✓Dynamically load scripts based on user location and consent preferences
✓Track consent through standard event listeners and Google Tag Manager
✓Enable seamless integration with Google Consent Mode
This section provides the steps to integrate and deploy the TrustArc Cookie Consent Manager (CCM) onto your Webflow site. The process involves installing the application, authorizing its access to your Webflow custom code, and configuring the essential parameters for your cookie banner.
1
Install and open the TrustArc Cookie Consent Manager (CCM) app.
2
Authorize the app to access your Webflow site. This grants permissions to read and update the custom code on your Webflow pages.
3
In the app, select the desired Webflow site to connect. Then, click Authorize App.
4
Accept the TrustArc Terms of Use and confirm that you have a valid TrustArc account. Then, click Continue to Application to proceed.
5
Click + Create New Configuration, provide a Configuration Name, then click Create.
6
Select a CCM version and provide the following CMP configurations to set up the cookie banner:
CCM Version: Choose CCM Advanced for greater customization.
CMP Script ID: Enter the unique CMP ID provided by TrustArc.
CMP Script Parameters: Enter additional parameters for customizing the CMP script. (Example for CCM Advanced: &c=teconsent&behavior=&country=us&js=nj¬iceType=bb>m=1&pcookie)
Banner Container: Specify the ID or HTML element where the cookie banner will be displayed. Defaults to consent_blackbar based on the CMP version selected.
7
(Optional) Enable the Display Cookie Preferences Link feature.
Alternatively, use the website editor to add an element with the teconsent ID in the website's footer link, matching the configuration in the CMP Script Parameters field.
8
Enable Standard Event Listener to fire custom events for Google Tag Manager (GTM) when consent is given in the dataLayer variable.
9
In the Opt-out Setting field, enter the region code(s). By default, if the user's region is set to the US, users will be automatically opted in to tracking.
10
Enable Google Consent Mode if the client uses gtag.js. Then, configure the following:
In the Consent Behavior field, select which TrustArc cookie has configurations for opt-out preferences.
Fill in the following optional fields as needed:
Google Analytics (GA) Measurement ID
Enable Data Reduction
Enable URL Passthrough
Set the Consent Type Mapping for Google (choose options as needed).
Set Wait For Update to 500 milliseconds.
11
Enable Webflow Analyze and Optimize for Webflow tracking consent integration. Then, map the consent category. The category comes from the Cookie Consent Manager set up in the CMP Configuration section.
12
Click SAVE & NEXT.
13
Choose the Webflow site you authorized earlier.
14
For a new app, register the script from TrustArc to be published on Webflow. A new script (version 1) will be registered.
15
Click Deploy Consent Manager. Wait a few seconds while the script installs.
16
After deployment, confirm that you understand that publishing will apply all ongoing changes. Then, click Publish.
17
Once published, your script is live. To view the active site, click View Site.
Verifying the Banner on the Live Site
This section guides you through the process of verifying that the TrustArc Cookie Consent Manager is correctly installed, loading its assets, and displaying the dynamic banner on your live Webflow site.
1
Open your Webflow site in another tab.
2
Confirm that the cookie banner is visible.
3
Open Developer Tools > Network Tab. Look for a CDN call referencing version 1 of the script for the new app submission.
4
The Response tab contains the code snippet responsible for loading all necessary assets onto the page. This is the same essential loading mechanism used for the other extensions referenced in the application submission.
Updating and Redeploying the Script
Follow these steps when you make a change to your configuration within the TrustArc settings and need to update the live site.
1
In your application, click Start Over.
2
Make the desired changes to the configuration (for example, disabling an option or adding a new parameter). Then, click SAVE & NEXT.
3
Select the site(s) where you want to publish the update.
4
The version has changed since modifications were made. You must re-register and redeploy the script.
5
Click Deploy Consent Manager to deploy the updated configuration.
6
Confirm that you understand that publishing will apply all ongoing changes. Then, click Publish. The script is now updated on the back-end, ready to be pulled by your website.
7
Visit the live site and check the network call (specifically the CDN call). You should now see the new version loading (for example, Version 2) on the page, confirming your update is active.
Getting the User Tracking Choice
This section details the steps to retrieve the user's current tracking preference.
1
Open your Webflow site in another tab.
2
Open Developer Tools > Console Tab. Call the function wf.getUserTrackingChoice(), which returns the user's current tracking choice:
'allow' — The user has opted in to tracking.
'deny' — The user has opted out of tracking.
'none' — The user hasn't made a choice.
In the example, the function returns allow because the connection is detected from an implied location (the US). The Cookie Consent Manager's default settings will automatically opt the user in to tracking. User selections immediately update their tracking status.