---
title: BluePoint GA4 Multiple IDs Alert
type: article
created: '2025-12-17'
updated: '2025-12-17'
source_docs:
- raw/2025-12-17-bluepoint-atm-marketing-call-109522267.md
tags:
- ga4
- google-analytics
- callrail
- bluepoint-atm
- web-analytics
- tracking
- technical-issue
layer: 2
client_source: null
industry_context: null
transferable: true
---

# BluePoint GA4 Multiple IDs Alert

## Overview

During the December 17, 2025 marketing sync, CallRail flagged the BluePoint ATM website for having **multiple Google Analytics 4 (GA4) IDs** installed. This is a configuration error that can cause duplicate data, inflated metrics, and unreliable reporting across all GA4-dependent workflows.

The issue was surfaced via a CallRail integration alert and requires investigation to confirm which ID is correct and remove any duplicates.

## Background

CallRail integrates with GA4 to pass call tracking data into analytics. When it detects more than one GA4 measurement ID on a page, it raises an alert because it cannot reliably determine which property to send events to. This can silently corrupt attribution data.

The BluePoint website previously had a GA4 ID configured — likely during an earlier CallRail setup session where the ID was copied and pasted manually. The current hypothesis is that a second ID was introduced at that time or during a subsequent site update.

## Symptoms

- CallRail integration alert: *"Multiple Google Analytics IDs found on your website"*
- Uncertainty about which GA4 property is receiving live data
- Potential for split or duplicated session/event data in GA4 reporting

## Investigation Steps

1. **Audit the website's tag implementation** — Check Google Tag Manager (or hardcoded script tags) for all GA4 measurement IDs present on the site.
2. **Cross-reference against the BluePoint GA4 property** — Confirm the correct measurement ID from the GA4 admin panel (`Admin → Data Streams → Web stream details`).
3. **Remove or disable the incorrect ID** — If a stale or duplicate tag exists in GTM, pause or delete it. If hardcoded, remove from the site template.
4. **Verify in CallRail** — After cleanup, confirm the CallRail alert clears and the integration shows a single, valid GA4 ID.
5. **Validate data flow** — Confirm events (calls, form fills) are flowing into the correct GA4 property.

## Status

| Item | Status |
|---|---|
| Alert identified | ✅ Confirmed (Dec 17, 2025) |
| Root cause investigation | 🔲 Pending — assigned to Mark (Asymmetric) |
| Duplicate ID removed | 🔲 Pending |
| CallRail integration verified | 🔲 Pending |

**Owner:** Mark Hope (Asymmetric)
**Flagged in:** [[meetings/2025-12-17-bluepoint-atm-marketing-call]]

## Why This Matters

GA4 data informs SEO performance tracking, paid campaign attribution, and the conversion path analysis Asymmetric is actively building for BluePoint's high-traffic blog pages. Inaccurate data at the analytics layer undermines all downstream reporting and optimization decisions.

## Related

- [[clients/bluepoint-atm/_index]]
- [[knowledge/web-analytics/callrail-number-swapping-failure]]
- [[knowledge/integrations/hubspot-lead-notification-logging]]