> ## Documentation Index
> Fetch the complete documentation index at: https://docs.replo.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Why does Replo warn that a pixel might already be firing?

> Avoid double-counted events when a tag manager already fires the pixel you're adding in Replo.

When you add a pixel in **Site settings** → **Scripts & Pixels**, Replo checks whether a tag manager on your site already fires it, and warns you if it might.

Google Tag Manager, Elevar, and Segment can all fire a pixel (Meta, GA4, TikTok, Pinterest, Snapchat, Reddit, X) on your behalf. If you also add that pixel directly in Scripts & Pixels, every event fires twice and your ad platform reports inflated numbers. Replo reads your Google Tag Manager container to check which pixels it already fires; Elevar and Segment don't expose that config publicly, so Replo flags them as worth checking by hand. Keep the pixel in only one place.

More in [Adding Scripts](https://docs.replo.app/features/scripts.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.