Setting up trackers of third-parties

Consent Pro
1

When using iframe embeds they are automatically blocked if the URL is referred to a tracker, correct?

If the URL does not have a tracker associated with it or if this tracker has a category of “essential” the iframe will not be blocked.

Im my case I have a Vimeo iframe embedded and even though I scanned for the trackers it is not blocked. I assume this is because the only tracker found was “cf.turnstile.u” (“__cf_bm”) and it is currently marked as essential. The other trackers (“_cfuvid”, “COOKIE_ID_PICOX_ID”, “player”, “vuid”) set by Vimeo are from “https://player.vimeo.com” and are not automatically added when scanning the page. Would this require me to add them manually or are cookies from different domains not influencing the blocking of content?

2

Hey @vierless_julian! There’s an important distinction worth clarifying here — the scanner and the iframe blocking mechanism are actually two separate systems.

The scanner’s role is to detect trackers and populate your preferences panel with their names, purposes, and categories. It doesn’t automatically gate whether an iframe loads or not.

Iframe blocking is always attribute-based and requires manual setup on the element itself. To block a Vimeo iframe until consent is given, you need two things:

  1. Replace the src attribute with fs-consent-src
  2. Add the fs-consent-categories attribute set to the appropriate non-essential category

Your iframe should look like this:

<iframe
  fs-consent-src="https://player.vimeo.com/video/[your-video-id]"
  fs-consent-categories="[your-category]"
  frameborder="0"
  allowfullscreen=""
  title="Vimeo video"
></iframe>

The available non-essential category values are analytics, marketing, and personalization. You’ll need to pick whichever fits your Vimeo embed based on your privacy policy.

To directly answer your two questions:

  • Cross-domain cookies from player.vimeo.com — whether or not they’re detected by the scanner has no effect on whether the iframe is blocked. That’s determined entirely by whether fs-consent-src and fs-consent-categories are on the element.
  • Adding Vimeo trackers manually in the app is useful for displaying them correctly in the preferences panel, but it won’t trigger iframe blocking on its own. The attributes on the iframe are still required.

Update the iframe with those two attributes, choose the right category, and you should be good to go :flexed_biceps: