Skip to main content
The Lemrock Pixel only runs for visitors who accept it. Declare Lemrock in your consent management platform (CMP: Didomi, OneTrust, Axeptio…), then make your install follow the visitor’s choice.

1. Add Lemrock to your CMP

In your CMP’s vendor list, select Lemrock AI (IAB TCF vendor ID 1662). The pixel sets two first-party cookies on your main domain, and nothing else: lemrock_click (ad click ID, 90 days) and lemrock_consent (refusal, 180 days). Then turn on your CMP’s option to ask again when the vendor list changes. Visitors who answered before you added Lemrock aren’t covered until they answer again. The pixel doesn’t read your CMP’s signals (IAB TCF, Google Consent Mode) by itself:
  • GTM: require ad_storage on the Lemrock tags. See GTM setup, step 5.
  • Script: load the snippet only after the visitor accepts. See Script, step 4.
  • Shopify: set the custom pixel’s permission to Required, with Marketing. See Shopify.
Events that fire before the visitor accepts are not sent later.
Don’t call lemrock("consent", false) by default on every page: it deletes the click cookie, so the ad click is lost even after the visitor accepts.

3. Check

In a private window, open your site with ?lrclid=lr_clk_0000000000000000000000 in the URL, then look at DevTools (F12) > Application > Cookies:
  1. Before you answer the banner, and after refusing: no lemrock_click.
  2. After accepting (in a new private window): lemrock_click is set.