Henkelman.jp — Tracking & Consent Status

At a glance

1Google Ads and Meta conversion tags

Google Ads records a conversion directly only for visitors who accept cookies; Meta records conversions for every visitor. Google's figure is therefore a lower bound and the two counts cannot be placed side by side.

Reported inquiries

Google's click volume in both months was above the 700-click threshold, so modeling was eligible; it produced no Inquiry Complete conversions in September. With the Phase 2 budget, click volume is expected to fall below the threshold. The Google Ads total includes any modeled conversions.

Who configured what

The container's version history (section 2) shows: Cookiebot and the GA4 events were added on 16 Dec 2025 and the Consent Mode default state on 12 Jan 2026, both published by partoutinteractive@gmail.com. The Google Ads tags (Dec 2025 and 30 Aug 2026) and the Meta Pixel tags (Dec 2025 and 22 Jul 2026) were published by Gaku (tsunekawa@ga-ku.co.jp).

Google's native tag types in GTM respond to Consent Mode automatically. The Meta tags are a community template and Custom HTML, which GTM does not gate unless an “additional consent” requirement is set on the tag. No such requirement was set on any tag, by either party. We found no setting that deliberately exempts Meta; the difference follows from the tag types.

If Meta is aligned with Google

If the Meta tags are changed to fire only after consent, Meta will stop recording conversions from visitors who do not accept cookies. Meta has no equivalent of Google's conversion modeling for declined consent (section 5). Fewer conversion signals will reach Meta's delivery optimisation, so campaign performance is expected to decline. The size of the drop depends on the share of visitors who do not accept, which Cookiebot's consent statistics can show (not yet pulled).

2What the GTM container shows

Container GTM-NCPRJVG5 (account 123478869, container 237490072). Published version 15 “Google New”, 30 Aug 2026, by tsunekawa@ga-ku.co.jp. The default workspace has no unpublished changes. The container's “Consent Overview” option appears to be off, so GTM shows no per-tag consent summary.

Tag inventory (17 tags)

“Built-in” means the tag type itself reads the Consent Mode state (Google tag types). “None” means the tag has no built-in consent behaviour and no additional consent requirement was added. User-defined variables: Adwords ID, Metings ID, CV24 – Tracking enabled (all constants). The trigger “Trigger - Contactform JP” (form submission on the old site path) is unused.

Version history

Consent default as published

gtag('consent', 'default', {
  'ad_storage': 'denied',
  'ad_user_data': 'denied',
  'ad_personalization': 'denied',
  'analytics_storage': 'denied',
  'wait_for_update': 500
});
gtag('set', 'url_passthrough', true);
gtag('set', 'ads_data_redaction', true);

Tag “Google tag default state”, trigger Consent Initialization – All Pages. The Cookiebot template on the same trigger has “Enable Google Consent Mode” switched on and updates the state when the visitor responds.

Outside GTM

The site's own HTML contains a GA4 snippet for G-FRSPPVR249 (gtag.js) in addition to the GA4 tag in GTM. It runs before GTM's consent default is applied and writes the _ga cookie regardless of consent; GA4 is therefore loaded twice on each page.

3Cookiebot: banner shown to visitors from Japan

Cookiebot shows the consent banner to visitors from Japan although its own regulation check reports that the GDPR does not apply to them.

• Cookiebot (CMP ID 13a86e93-ba89-4992-b025-85fe6b04c1ac) is loaded on every page through GTM. Geo-targeting is not enabled, so the banner is shown to all visitors worldwide.
• For a visit from Japan, Cookiebot's runtime object reports regulations.gdprApplies = false (also ccpaApplies = false, lgpdApplies = false), yet the banner is displayed and the Consent Mode default stays “denied” until the visitor responds.
• The first layer of the banner offers two buttons, “カスタム化” (Customize) and “全て許可” (Allow all). There is no “Reject” button on the first layer; a visitor has to open the second layer to decline. The Dutch Data Protection Authority's guidance asks for the reject option on the same layer as accept (Autoriteit Persoonsgegevens: Clear cookie banners).
• Before the banner is answered, the cookies _ga and _ga_FRSPPVR249 (GA4, from the hard-coded snippet in section 2) and _fbp (Meta) are already set.
• Google's EU user consent policy applies to end users located in the EEA, the United Kingdom and Switzerland. It does not require consent signals for users located in Japan (Google: EU user consent policy).

4consortiumventure24.com: a tracking tag without consent

A Custom HTML tag in GTM named “TEMP – CV24 tracking test” loads a script from consortiumventure24.com on every page, with no consent condition. It sends visitor data to that server for every visitor, including those in the EEA.

What this means in practice: the tag transmits personal data (IP address, user agent, browsing data) and stores cookies without consent, for all visitors, while the Google tags on the same site are consent-gated. The tag's name and its on/off variable suggest it was added as a test and left active.

5Can Meta be set up like Google?

Partly. Meta can be gated on consent in GTM, which matches Google's “basic” consent mode. Nothing on Meta's side matches Google's “advanced” mode, where tags keep sending cookieless pings and lost conversions are modeled.

Server-side tagging, the Conversions API or a first-party domain do not remove the consent requirement for storing cookies or sending personal data to Meta; they change where the request is sent from, not whether consent is needed. Chrome's Attribution Reporting API, the proposed cookieless alternative, was retired by Google in October 2025 (Google: Privacy Sandbox update).

6Points to confirm with Henkelman

• Whether the consent-first configuration (all denied by default, banner for every visitor) is a deliberate Henkelman policy for the Japanese site, and whether it is meant to apply to visitors located in Japan.
• Whether Meta was knowingly left outside the consent flow, or whether it should be aligned with Google (section 5), accepting the measurement loss described in section 1.
• Who commissioned the “TEMP – CV24 tracking test” tag, whether a vendor contract exists, and whether it should be stopped.
• Whether the GA4 snippet hard-coded in the site's HTML (outside GTM) should be removed, so that GA4 runs once and respects the consent default.
• Whether the first layer of the Cookiebot banner should offer a Reject button, as the Dutch DPA's guidance describes.

7Method and references

All observations date from 23 October 2026.

• Loaded https://www.henkelman.jp/ja and /contact/ in a fresh browser session without responding to the Cookiebot banner; recorded the cookies set, Cookiebot's runtime state, the Consent Mode default in the dataLayer, and the outgoing requests (Google Ads conversion pings, GA4, Meta Pixel, consortiumventure24.com).
• Read the GTM container GTM-NCPRJVG5 in the Tag Manager interface (tags, triggers, variables, container settings, version history) and parsed the published container file to confirm each tag's trigger and consent settings.
• Retrieved the site's HTML to check for tags outside GTM.
• Downloaded the consortiumventure24.com script for inspection and looked up the domain's registration record (RDAP).
• August and September 2026 figures are taken from Google Ads and Meta Ads reporting as used in the monthly reports; the website inquiry total is from the form submission records.

References

• Google: Consent mode concepts (basic vs advanced, cookieless pings)
• Google Ads: conversion modeling eligibility, 700 ad clicks per 7 days
• Google Tag Manager: consent settings on tags (additional consent checks)
• Google: Set up Cookiebot to obtain user consent (cookie_consent_update trigger)
• Google: EU user consent policy
• Meta: Pixel consent, revoke / grant
• Meta: Business Tools Terms
• Meta: About Conversions API
• Autoriteit Persoonsgegevens: Clear cookie banners
• Cookiebot: display the banner to visitors from specific regions only
• Dutch Digital Agencies: Partout
• Lead Forensics: official WordPress plugin (tracking code format)
• Google: Update on plans for Privacy Sandbox technologies