Enhanced Conversion Data Validator

Inspect and validate Enhanced Conversion data sent to Google Ads and / or Google Analytics 4. You can manually paste em parameter…

As of June 2026, Enhanced Conversion Data Validator has 36 users and a 5.00/5 rating from 1 reviews in the Productivity category.

Usersno change0%
36
36
Ratingno change0%
5.00
1 reviews
Reviewsno change0%
1
Version
2.5.2
Manifest V3
90-day change · In the last 90 days this extension 1 version update.

History

5 snapshots

Tracking since May 14, 2026.

38.1622.56.84May 14, 2026Jun 8, 2026
View as table
DateUsersRatingReviewsVersion
May 14, 20262.3
May 20, 20262.3
May 26, 202695.0012.5.2
Jun 2, 2026235.0012.5.2
Jun 8, 2026285.0012.5.2
Now365.0012.5.2

Changelog

  • May 20, 2026
    description
    Inspect and validate Enhanced Conversions data sent to Google Ads and / or Google Analytics 4. 
    
    You can manually paste em parameter values or record requests while you browse and check what data is included in your Google Ads conversions, user-provided data events or GA4 reqests. 
    
    Recording automatically collects em (and eme) parameters in all Google Ads / GA4 collect requests. Shows all request parameters and decodes user data payloads. Hashed data can be checked with clear text input fields for known values. 
    
    - Troubleshooting: You can inspect user_data objects pushed via GTM, gtag, or raw JSON before they get processed by your tags. 
    
    - Structure validation: address fields (first_name, country, postal_code, …) outside of user_data.address trigger a structure-error warning — these don't reach Google as expected
    
    - Google Tag Gateway compatible: Tag Gateway and server-side GTM on first-party origins are captured as well
    
    - Export: captures as JSON for documentation or analysis (each entry tagged source: 'ads' | 'ga' and transport: 'google' | 'first-party', plus eme when present)
    Inspect and validate Enhanced Conversion data sent to Google Ads and / or Google Analytics 4. 
    
    You can manually paste em parameter values or record requests while you browse and check what data is included in your Google Ads conversions, user-provided data events or GA4 reqests. 
    
    Recording automatically collects em (and eme) parameters in all Google Ads / GA4 collect requests. Shows all request parameters and decodes user data payloads. Hashed data can be checked with clear text input fields for known values. Displays additional conversion data like value, currency, product data, customer status flag, Google Consent Mode flags.  
    
    - Troubleshooting: You can inspect user_data objects pushed via GTM, gtag, or raw JSON before they get processed by your tags. 
    
    - Structure validation: address fields (first_name, country, postal_code, …) outside of user_data.address trigger a structure-error warning — these don't reach Google as expected
    
    - Google Tag Gateway compatible: Tag Gateway and server-side GTM on first-party origins are captured as well
    
    - Export: captures as JSON for documentation or analysis (each entry tagged source: 'ads' | 'ga' and transport: 'google' | 'first-party', plus eme when present)
    
    ---
    
    Changelog
    -----------------
    
    v2.5.1 / v2.5.2:
    - Fix: (silent) error when accessing system settings for dark mode, user data validation issues (street, postal code) 
    
    v2.5:
    - Settings tab (⚙ icon, top right): existing settings moved to new tab, new settings for dark mode and text scaling added.
    - User-data indicator on extension icon: When active, the toolbar badge shows `ud` / `eme` / `em` on the current tab whenever a built-in Google endpoint (Ads `/ccm`, `/pagead`, GA4 `/g/collect`) receives user data — independent of recording, so the icon can act as an ambient "is ec data flowing here?" indicator while you browse. 
    - Conversion summary on captures: a compact second line under the identifier pills shows event type, value + currency, item count (tooltip with SKU × qty @ price), new-customer flag, customer LTV, shipping cost + destination and order ID. Sourced from Google Ads conversion parameters  and GA4 commerce params. 
    - Consent Mode warning: a red `no ad_storage` pill (or orange `ad_storage unset`) is added to the card whenever `gcs` / `gcd` indicates that ad_storage was not granted.
    - Power-user shortcut: Ctrl/⌘+click anywhere on a card opens the detail view directly (the `i` icon still works the same).
    - Clear textboxes: link next to the EM Decoder and Object Analysis textareas — one click empties the field and clears the decoder output.
    
    v2.4:
    - Recording UI overhauled: `Permit` and `Start`/`Stop` are separate buttons now. The URL field is always editable and auto-updates when you switch tabs (unless you are typing in it).
    - Permit-button live status: shows `Permitted ✓` when the origin in the URL field is already covered. `Start` refuses to run on a site that is not permitted, with a clear error.
    - Auto-stop on panel close (default on): closing the side panel ends the recording. Uncheck the new option to keep capturing in the background.
    - Include-subdomains toggle (default off): broadens the Permit request to `https://*.<base>/*`, so a single grant covers shop subdomains and a first-party sGTM on its own subdomain.
    - GA4 / sGTM `user_data` capture: `ep.user_data.*` event parameters and top-level `user_data` JSON bodies are extracted and shown like an `em` payload. Click such a capture to load it into Object Analysis. Only fields with known identifiers (email/phone/address with or without `sha256_`) count — meta keys like `_tag_mode` are ignored.
    - Initiator filter: requests fired from Google's own UIs (`analytics.google.com`, `ads.google.com`, `tagmanager.google.com`, `tagassistant.google.com`) are ignored.
  • May 20, 2026
    short_description
    Inspect and validate Enhanced Conversions data sent to Google Ads and / or Google Analytics 4. 
    
    You can manually paste em…
    Inspect and validate Enhanced Conversion data sent to Google Ads and / or Google Analytics 4. 
    
    You can manually paste em parameter…

Permissions & access

Permissions
storagesidePanelwebRequesttabs
Host access
https://*.googleadservices.com/pagead/*, https://*.googleadservices.com/ccm/*, https://www.google.com/pagead/*, https://www.google.com/ccm/*, https://www.google-analytics.com/g/collect*, https://*.google-analytics.com/g/collect*, https://*.analytics.google.com/g/collect*

Screenshots

Enhanced Conversion Data Validator screenshot 1Enhanced Conversion Data Validator screenshot 2Enhanced Conversion Data Validator screenshot 3Enhanced Conversion Data Validator screenshot 4

About

Inspect and validate Enhanced Conversion data sent to Google Ads and / or Google Analytics 4. 

You can manually paste em parameter values or record requests while you browse and check what data is included in your Google Ads conversions, user-provided data events or GA4 reqests. 

Recording automatically collects em (and eme) parameters in all Google Ads / GA4 collect requests. Shows all request parameters and decodes user data payloads. Hashed data can be checked with clear text input fields for known values. Displays additional conversion data like value, currency, product data, customer status flag, Google Consent Mode flags.  

- Troubleshooting: You can inspect user_data objects pushed via GTM, gtag, or raw JSON before they get processed by your tags. 

- Structure validation: address fields (first_name, country, postal_code, …) outside of user_data.address trigger a structure-error warning — these don't reach Google as expected

- Google Tag Gateway compatible: Tag Gateway and server-side GTM on first-party origins are captured as well

- Export: captures as JSON for documentation or analysis (each entry tagged source: 'ads' | 'ga' and transport: 'google' | 'first-party', plus eme when present)

---

Changelog
-----------------

v2.5.1 / v2.5.2:
- Fix: (silent) error when accessing system settings for dark mode, user data validation issues (street, postal code) 

v2.5:
- Settings tab (⚙ icon, top right): existing settings moved to new tab, new settings for dark mode and text scaling added.
- User-data indicator on extension icon: When active, the toolbar badge shows `ud` / `eme` / `em` on the current tab whenever a built-in Google endpoint (Ads `/ccm`, `/pagead`, GA4 `/g/collect`) receives user data — independent of recording, so the icon can act as an ambient "is ec data flowing here?" indicator while you browse. 
- Conversion summary on captures: a compact second line under the identifier pills shows event type, value + currency, item count (tooltip with SKU × qty @ price), new-customer flag, customer LTV, shipping cost + destination and order ID. Sourced from Google Ads conversion parameters  and GA4 commerce params. 
- Consent Mode warning: a red `no ad_storage` pill (or orange `ad_storage unset`) is added to the card whenever `gcs` / `gcd` indicates that ad_storage was not granted.
- Power-user shortcut: Ctrl/⌘+click anywhere on a card opens the detail view directly (the `i` icon still works the same).
- Clear textboxes: link next to the EM Decoder and Object Analysis textareas — one click empties the field and clears the decoder output.

v2.4:
- Recording UI overhauled: `Permit` and `Start`/`Stop` are separate buttons now. The URL field is always editable and auto-updates when you switch tabs (unless you are typing in it).
- Permit-button live status: shows `Permitted ✓` when the origin in the URL field is already covered. `Start` refuses to run on a site that is not permitted, with a clear error.
- Auto-stop on panel close (default on): closing the side panel ends the recording. Uncheck the new option to keep capturing in the background.
- Include-subdomains toggle (default off): broadens the Permit request to `https://*.<base>/*`, so a single grant covers shop subdomains and a first-party sGTM on its own subdomain.
- GA4 / sGTM `user_data` capture: `ep.user_data.*` event parameters and top-level `user_data` JSON bodies are extracted and shown like an `em` payload. Click such a capture to load it into Object Analysis. Only fields with known identifiers (email/phone/address with or without `sha256_`) count — meta keys like `_tag_mode` are ignored.
- Initiator filter: requests fired from Google's own UIs (`analytics.google.com`, `ads.google.com`, `tagmanager.google.com`, `tagassistant.google.com`) are ignored.

Technical

Version
2.5.2
Manifest
V3
Size
41.79KiB
Min Chrome
114
Languages
1
Featured
No

Metadata

ID
oofghodijgflljjckgomndgkobnahhcp
Developer ID
u9ce0150feba373510b48359e6048867f
Developer Email
[email protected]
Created
May 13, 2026
Last Updated (Store)
May 17, 2026
Last Scraped
Jun 8, 2026
Website
markus-baersch.de
Privacy Policy

Data sourced from the Chrome Web Store · last verified Jun 8, 2026.