# Take Meta, GA4, and Google live

Critical notes;

1. It is important to ensure that you have one feed for each channel and not duplicating signals \[ remove the other source of data ]
   1. Meta, TikTok, Snap, etc channels cannot have de-duplicated dual data streams from two sources
      1. Create a new feed to your main pixel \[ using the same process ] by clicking Meta in the All channels, and ensure your browser check is turned ON
      2. Remove/Delete old data feeds to the pixels to prevent duplication of data \[ performance will drop in 24-48 hours here if not done right ]
      3. Steps (i) and (ii) have to happen almost simultaneously
      4. No change in your campaigns needed and there is no impact to to main pixel 
      5. **Note**: it is critical NOT to have two sets of data to your events manager \[ you can check by going to your conversion event and checking ]
   2. For Google Ads, you have to swap your old primary with Blotout conversions \[ move Blotout conversions to primary while switching old ones to secondary ]
      1. Check if secondary client and servers are tracking correctly
      2. At a minimum your conversions \[ client + server ] = old primary conversion before you take this live
   3. For GA4 you can;
      1. Continue tracking Blotout in a separate property \[ as setup ]
      2. OR replace existing GA4 property with Blotout 
         1. Create a new GA4 connection to your existing GA4 property
         2. Remove old stream \[ Note: this is a critical step ]
2. You are set and have gone live with Blotout  and your post cookie ID Graph is now operational to power any channel.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.edgetag.io/knowledge-base/lead-gen-best-practice-for-first-time-setup/take-meta-ga4-and-google-live.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.