Google Ads Customer ID Validator

Google Ads Customer ID: the AW- prefix, the hyphenated form and the 2018 rebrand

Every Google Ads account — the platform formerly known as Google AdWords until the July 2018 rebrand — is identified by a numeric Customer ID assigned at account creation. The same ID has two surface forms: the hyphenated NNN-NNN-NNNN shown in the UI top bar and the prefixed AW-XXXXXXXXXX used inside tracking scripts. Both refer to the same underlying account; the prefix variant became canonical with the launch of gtag.js, which uses the leading namespace to distinguish Google Ads from Google Analytics (G-), Floodlight (DC-) and Universal Analytics (UA-).

Validation reduces to two regular expressions: ^AW-\d{9,11}$ for tag-style IDs and ^\d{3}-\d{3}-\d{4}$ for the human-readable form. The numeric body is between 9 and 11 digits — Google never publicly committed to a fixed length, and IDs grow as the platform allocates new accounts. This validator strips whitespace, normalizes both forms and reports the canonical equivalent so you can paste an ID copied from the dashboard and use it in tagging code without manual conversion.

Where the Customer ID appears: gtag, Conversion API, Performance Max and remarketing

The Customer ID is the routing key for every tracking call. Main surfaces:

• gtag.js global tag: gtag('config', 'AW-1234567890') sets the conversion-tracking destination.
• Conversion event: gtag('event', 'conversion', { 'send_to': 'AW-1234567890/abcDEF123' }) — the segment after the slash is the Conversion Label.
• Conversion Linker tag: a Google Tag Manager template that writes the _gcl_aw cookie so attribution survives navigation.
• Enhanced Conversions API: server-side endpoint that hashes user-provided data (email, phone) and ties it to the Customer ID for first-party attribution.
• Performance Max: Google's AI-driven campaign type (launched 2021) inherits all conversion sources tied to the Customer ID.
• Remarketing audiences: built from the _gcl_aw cookie plus Customer Match lists scoped to the Customer ID.
• Cross-account conversion sharing: managed at the MCC (Manager Account) level, but each child ID still appears in the send_to.

<!-- Global site tag (gtag.js) - Google Ads -->
<script async src="https://www.googletagmanager.com/gtag/js?id=AW-1234567890"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'AW-1234567890', { 'conversion_linker': true });
</script>

Smart Bidding, Quality Score and the Brazilian advertising market

Google Ads operates a real-time auction for every search query, display impression and YouTube pre-roll. The Customer ID groups campaigns whose bids, budgets and audiences feed Smart Bidding — Google's machine-learning bid optimizer that targets metrics like Target CPA, Target ROAS and Maximize Conversions. Quality Score (1 to 10) for search ads remains the dominant lever for CPC: higher relevance and landing-page experience translate into lower auction prices.

Brazil is the third-largest Google Ads market in the Americas, with annual spend in the order of R$ 20 billion as of 2024 — dominated by agencies, e-commerce verticals and the financial sector. The Google Display Network (GDN) reaches over 2 million sites and apps, while YouTube Ads share the same Customer ID infrastructure. Brazilian advertisers typically configure BR location targeting, PT-BR language and the standard Brasil network setting, with separate campaigns for the Search and Display channels because performance characteristics diverge sharply.

LGPD, consent mode and avoiding the dev-ID-in-production anti-pattern

Under Brazil's LGPD (Law 13.709/2018), conversion tracking, remarketing cookies and Customer Match uploads all require an explicit legal basis — typically consent for behavioural tracking. The recommended pattern is Google Consent Mode v2, which sends ping signals before consent is granted and full hits afterwards, modeling the missing conversions statistically. Failing to wire consent is the most common LGPD audit finding for Brazilian advertisers.

A persistent anti-pattern is shipping a development Customer ID into production. Every test event becomes a real conversion, polluting Smart Bidding training data and triggering disclosure errors with the client. Use environment-scoped configuration (e.g. window.__GADS_ID read from a server-rendered template) and validate the ID at build time. This tool helps detect copy-paste mistakes — pasting a Universal Analytics ID like UA-12345-1, a GA4 ID like G-XXXXXXXXXX or a Floodlight ID DC-XXXXXXXX into a Google Ads field fails the regex immediately.

FAQ

Should I use the AW- form or the raw 123-456-7890 form?

Use the AW- prefix in all tagging code, gtag and GTM containers — it is the modern canonical form. The hyphenated raw form is for human reference in invoices, support tickets and the dashboard breadcrumb.

Is the Customer ID confidential?

No. The ID is embedded in every page that loads the Google Ads tag and is trivially observable. What must stay confidential is the OAuth credential or developer token that grants programmatic access to the Google Ads API.

Do other ad platforms use a similar identifier?

Yes. LinkedIn uses an Insight Tag Partner ID, Meta uses the Pixel ID, TikTok uses a Pixel Code and Microsoft Advertising uses UET Tag IDs. Each has its own prefix and regex; do not mix them.

Is consent really mandatory for Brazilian campaigns?

Yes, when the tracking processes personal data — which Google Ads always does via the _gcl_aw cookie. The LGPD's principles of purpose limitation and transparency require informing the user and offering an opt-out, typically through a Consent Management Platform integrated with Google Consent Mode v2.

Does this validator confirm the account is active?

No. It only confirms the format matches Google Ads conventions. Verifying activation, billing status or admin access requires the Google Ads API and a developer token tied to your MCC.