# Image Trackers Some third-party images set cookies as soon as they load — tracking pixels, social badges, and embed previews. A browser requests an image the moment it parses a live `src`, so those cookies land **before the visitor makes a consent choice**, and Consent Pro cannot intercept the request. A cookie-setting image therefore needs one manual change to the markup. After that, Consent Pro loads it once the visitor accepts the required categories. ## Find them Scan the site, then open the **Manager** and look for trackers carrying a **from Image** badge. Opening the tracker shows the image it was attributed to. For how detection works — including `httpOnly` cookies read from response headers — see [Image Trackers](/runtime/image-trackers#how-detection-works) in the JavaScript API docs. ## Block one The image has to render with no `src` attribute at all, so the markup must be yours to control. Use an **Embed** element (or page custom code) for the image, rather than a native Image element. 1. Place the image markup in an **Embed** element. 2. Leave out the `src` attribute. 3. Put the URL in `fs-consent-src` and add `fs-consent-categories`. 4. Publish the site. ```html ``` Consent Pro sets `src` when the visitor accepts the category, and removes it again if consent is revoked. **tip Essential images need no change** Essential cookies don't require consent, so an image that only sets an essential cookie can keep its normal `src`. Label the tracker as **Essential** in the Manager so it is still disclosed. For the category values and multi-category behaviour, see the [category reference](/runtime/image-trackers#category-reference). ## Related - [Image Trackers](/runtime/image-trackers) — detection details and full attribute reference - [Sitemap Setup](/webflow/sitemap) — review discovery and scan coverage - [When Trackers Appear in the Preferences Panel](/webflow/publishing-trackers) — tracker changes reach visitors only after a publish