How to Manage Consent for Fonts, Embedded Forms, Videos, and Other Third-Party Content
Analytics and advertising tags are not the only things on a page that contact other companies. Web fonts, embedded forms, videos, maps, and chat widgets all load from third-party servers, and many set cookies. This article explains how to find them, how to decide what to do with each, and how to apply the decision with Captain Compliance.
Why these need attention
Each of these items makes the visitor’s browser contact another company. That company receives the visitor’s IP address and the address of the page. Some items also set cookies or run scripts. A consent setup that covers only your tags leaves them running whatever the visitor chooses.
Find what your pages load
Scan the site and review what the scan found. See How to Review and Classify Cookies After a Scan.
Open a page in a private or incognito browser window, and open the browser’s developer tools on the Network tab. Before you choose in the banner, list the third-party domains that the page contacts.
For an outside view of the live site, run a Patrol scan. See How to Run a Website Scan in Patrol.
Three ways to handle an item
Approach | When to use it | How |
|---|---|---|
Remove the third party | You can host the resource yourself | Serve the files from your own domain. No request leaves your site, so no consent is needed. |
Use a privacy mode | The vendor offers a version that sets no cookies until the visitor acts | Switch the embed to that version. The vendor is still contacted, so decide whether a consent category should also apply. |
Hold it until consent | Anything else that is not strictly necessary | Give the item a category, and block it until the visitor allows that category. |
Common cases
Content | What it does | Usual handling |
|---|---|---|
Web fonts from a font service | The browser downloads font files from the service on every page | Host the font files on your own domain. Auto Blocking and Strict Mode act on scripts and iframes, and a font stylesheet is neither. |
Embedded forms and schedulers | Load a script or an iframe, and often set tracking cookies | Turn off the vendor’s tracking cookies if it has that setting. Treat the form as Functionality if it is the purpose of the page, and otherwise by what its cookies do. |
Videos | Load an iframe that can set cookies | Use the vendor’s privacy mode, such as YouTube’s youtube-nocookie.com embed address, and hold the iframe under Functionality or Targeting. |
Maps | Load an iframe or a script from the map provider | Hold under Functionality, or replace the map with an image and a link. |
Chat widgets | Load a script and set cookies to recognize the visitor | Hold under Functionality. |
Social embeds and share buttons | Load scripts that can follow the visitor across sites | Hold under Targeting, or use plain links. |
Bot protection on forms | Loads a script and sets cookies for security | Often treated as strictly necessary where it protects a form, but views differ. Load it only on pages that need it. |
Payment and sign-in frames | Needed for a service that the visitor asked for | Strictly Necessary. Do not hold these. |
Hold content until consent
Auto Blocking: add a rule for a script address, an iframe, or an inline script pattern, and give it a category. Captain Compliance holds the item until the visitor allows the category, and then activates it without a page reload. See How to Block Scripts Before Consent with Auto Blocking and Strict Mode.
Strict Mode: use it for scripts that must not run at all before consent.
Google Tag Manager: for anything that loads as a tag, use the tag’s consent settings. See How to Gate GTM Tags with Native Consent Settings.
Explicit consent logic: for everything else, such as code that adds a font stylesheet or an image pixel, run the code only when the category is granted. See How to Gate Non-Essential Scripts and Beacons Using Explicit Consent Logic.
Keep the page usable
A held form or video leaves an empty space. Add a short message in its place that says why the content is hidden, and point visitors to the Cookie Preferences link in your footer. See How to Add a “Cookie Preferences” Option to Your Website Footer.
Do not hold content that the visitor needs for a service they asked for, such as checkout, payment, or sign-in.
If a held item breaks other parts of the page, load it only on the pages that use it.
Test
Open the page in a private or incognito browser window, with the developer tools on the Network tab.
Before you choose, confirm that the page makes no requests to the services that you held.
Select Allow, and confirm that the content appears.
Start again, select Reject, and confirm that the content stays hidden.
For a full test plan, see How to Test Consent Banner Configuration & Behavior.
