Skip to main content

Understanding Tag Account IDs

Learn what Tag Account IDs are, why they matter for tag management, and how to validate them across different platforms.

Written by Luiza Gircoveanu

Overview

A Tag Account ID is a unique identifier that associates a tag or pixel with a specific account, tracking property, or customer within a third-party vendor's system. It's the value that tells the vendor whose data they're collecting and where to send that information.

In ObservePoint, the Account column in the Tags Report displays this ID number. A single tag can have multiple accounts associated with it, and the Account ID field captures which account(s) the tag is configured to use.

Tag Account ID Impact

Proper configuration of Tag Account IDs is critical for several reasons:

  • Data Integrity - The Account ID determines where your tracking data is stored. An incorrect or missing Account ID means your data goes to the wrong place.

  • Validation Rules - When creating Tag & Variable Rules in ObservePoint, rule failures can occur if the rule's expected Account ID doesn't match the actual Account ID of the tag firing on your pages. This makes Account ID visibility essential for debugging.

  • Multi-Property Setups - Organizations with multiple websites, applications, or regional properties often use different Account IDs to separate data streams. Verifying correct Account ID usage ensures each property reports to the right destination.

  • Compliance & Auditing - Proper Account ID mapping is part of a mature tag governance program and helps demonstrate that tracking is intentional and correctly configured. It's very common for 3rd party agencies to implement tags that use their own tags which may result in non-compliance.

Account IDs by Technology Type

Different types of vendors use Account IDs differently. Here are common examples:

Analytics Platforms

  • Google Analytics 4

    • Format: Measurement ID (e.g., G-XXXXXXXXXX) or older UA format (UA-XXXXX-Y)

    • Purpose: Identifies which GA4 property receives your page data

    • Example: G-5XB4KW8H2J tells Google Analytics to send data to a specific property

  • Adobe Analytics

    • Format: Report Suite ID (e.g., mysite-prod or mysite-dev)

    • Purpose: Identifies which report suite collects the data

    • Example: A company might have separate Account IDs for production (mysite-prod) and staging (mysite-dev) environments

  • Universal Analytics (Legacy)

    • Format: UA-XXXXX-Y where XXXXX is the account ID and Y is the property number

    • Purpose: Identifies which UA property received data

Advertising Platforms

  • Google Ads / Google Tag Manager

    • Format: Container ID (e.g., GTM-XXXXXX) or conversion ID

    • Purpose: Routes conversion and audience data to the correct Google Ads account

    • Example: GTM-T5H39PSN identifies a specific GTM container

  • Meta (Facebook)

    • Format: Pixel ID (e.g., 123456789012345)

    • Purpose: Associates user events with a specific Facebook ad account

    • Example: Used for retargeting, conversion tracking, and audience building

  • LinkedIn Ads

    • Format: Partner ID or Conversion ID

    • Purpose: Tracks conversions and audience events for LinkedIn campaigns

Social Platforms

  • TikTok

    • Format: Pixel ID (e.g., 123456789012345)

    • Purpose: Tracks user actions for ads and analytics

What Does "None" Mean?

When a Tag Account ID appears as "None", it means ObservePoint couldn't extract the Account ID because either the vendor's tag doesn't expose it in a readable way, or the tag isn't configured in ObservePoint's database yet.

How to Handle "None" Values:

  • Known Vendors: Verify the network request for the tag contains a Tag Account ID either in the query parameter string or in the request payload. Research documentation for that specific tag to validate which variable uniquely identifies your organizations implementation of that technology, and contact our support team to request a Tag update.

  • New Vendors: Request a tag through ObservePoint's Support portal.

Identifying Tag Account IDs

In Your Tag Code

Most Account IDs appear in your page's network requests, JavaScript configuration, or data layer:

  • In JavaScript:

// Google Analytics gtag('config', 'G-XXXXXXXXXX');  // Facebook Pixel fbq('init', '123456789012345');  // Adobe Analytics _satellite.getVar("trackingServerSecure")

  • In HTML/Data Layer:

// Data layer format dataLayer = [{   'google_analytics_id': 'G-5XB4KW8H2J',   'conversion_tracking_id': '987654321' }];

  • In Network Requests (Observable in browser DevTools):

  • Query parameters: ?id=GA-123456 or ?cid=987654

  • Headers or request payload with tracking IDs

Using ObservePoint Tools

  • Debugger: The Tag Account column shows detected Account IDs for each tag

  • Tags Report: Filter or group by Account to see which pages use which Account IDs

Best Practices

  1. Document Your Account IDs: Maintain a registry of which Account IDs map to which properties and purposes

  2. Validate Consistency: Use ObservePoint rules to verify that the correct Account IDs appear on the correct pages

  3. Monitor for Changes: Set up consent categories (approved lists) and alerts to flag unexpected changes in Account IDs, which may indicate misconfiguration or unauthorized tag additions

  4. Test Before Deploying: Verify Account IDs in staging environments before pushing to production

  5. Handle None Values: Investigate any "None" values to determine if they indicate a configuration issue or a limitation of automatic detection

Conclusion

Tag Account IDs are foundational to tag governance—they ensure your tracking data reaches the right vendors. ObservePoint's reporting tools make Account ID visibility straightforward. Start by auditing your current Account IDs and setting up validation rules to catch misconfigurations early.

Related Articles
Did this answer your question?