> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/connectors/destinations/google/ads-pixel.md).
# Ads - Pixel
Fire the Google Ads tag with the segment's technical name, so Google Ads can build a website visitors list from it.
The Google Ads Pixel connector sends online data to Google Ads from the visitor's browser. The mediarithmics JavaScript tag loads the Google tag with a key/value indicating that the user is in a given segment; you then build a website visitors list on that event.
{% hint style="danger" %}
**Consent Mode V2.** From March 2024, and depending on your region, you must implement Google Consent Mode V2.
* Working with a Google-certified CMP? Check with your IT department or CMP provider that it has been updated to support Consent Mode V2.
* Working with any other CMP? Check that it will be GCM V2 compatible.
Google's documentation: [Consent for tags](https://developers.google.com/tag-platform/security/guides/consent), [Consent mode in Tag Manager](https://support.google.com/tagmanager/answer/10718549), [Consent Mode V2](https://support.google.com/tagmanager/answer/13695607).
{% endhint %}
## Description
### What you can do with this connector
* Retarget a visitor who looked at a product on your site without buying it.
* Reach visitors who are **not logged in**, which Customer Match cannot do.
### Which identifiers are sent
**None.** Google IDs go from the visitor's browser straight to Google Ads; nothing is stored on mediarithmics' servers. Your Google Ads audience only starts growing from the moment the synchronisation is set up.
Google is reached by several connectors and they behave differently - [the comparison is on the Google page](/connectors/destinations/google.md).
## Connector setup
### Prerequisites
**Tag activation.** The mediarithmics tag must call the `syncFeeds` method to trigger client-side tags such as the Google Ads pixel:
```javascript
mics.call('syncFeeds');
```
{% hint style="warning" %}
Without this line the client-side feed does not work. If you see synchronisation problems with Google Ads, check that `syncFeeds` is being called - with your account manager or solution architect.
{% endhint %}
**Audience technical name.** For Google to recognise it, the segment's technical name must contain **no special characters** - letters, figures and underscores only.
{% hint style="warning" %}
If the segment is already activated on another platform, changing its technical name can break that link. Set the technical name as soon as the segment is created, before activating anything.
{% endhint %}
**A Google Ads tag**, and its ID:
1. Go to Google Ads and select the right account level - the specific account you will run the campaign on, not the MCC account.
2. Go to **Audience management**, under **Tools and settings**.
3. Create a new **Web visitors** segment.
4. On **Member Segment**, create a *visitors of a specific tag*.
5. Click **New Tag** at the bottom.
6. Click the **i** button. The ID shown there is what you enter as **Pixel id** on the feed.
### Setup steps
{% stepper %}
{% step %}
**Check that the mediarithmics tag calls `syncFeeds`.**
{% endstep %}
{% step %}
**Check the segment's technical name.**
Letters, figures and underscores only. Fix it before activating.
{% endstep %}
{% step %}
**Create the tag in Google Ads and note its ID.**
{% endstep %}
{% step %}
**Select the Google Adwords Pixel connector, on the client-side side, and fill in its configuration.**
Field
Name
The name displayed in the mediarithmics platform.
Pixel id
The ID of the tag you created in Google Ads.
{% endstep %}
{% step %}
**Create the CDP-based audience in Google Ads.**
See [Create a CDP-based audience in Google Ads](#create-a-cdp-based-audience-in-google-ads).
{% endstep %}
{% endstepper %}
Creating and activating the feed on a segment is covered in the **Audience & Activation** section, under *Activate your audiences › Send your first-party data to a destination*.
### Create a CDP-based audience in Google Ads
1. Sign in to your Google Ads account.
2. Click the tools icon in the top right corner.
3. Under **Shared library**, click **Audience manager**.
4. Click **Audience lists** in the left page menu, then the plus button, and select **Website visitors**.
5. Enter a descriptive name for the data segment.
6. Fill in the **Tag Source** with the corresponding information.
7. Choose the **Visited Page** template from the **List Members** dropdown.
8. In the **Page URL** dropdown, select the segment you want to use.
9. Select the **True** option.
10. Click to create the segment.
## Good to know
There is **no consent status to set on this connector** - it is handled directly by the Google Ads remarketing tag. See [Google - Consent management](/connectors/destinations/google/consent-management.md).
This is a client-side connector, so it carries the client-side constraints: volumes ramp up as users visit your site, a segment exit cannot be signalled, and nothing is sent when the tag is blocked or consent is refused. See the **Audience & Activation** section, under *Activate your audiences › Set up a destination › Feed*.
## FAQ
#### Nothing is syncing with Google Ads. What should I check first?
That `mics.call('syncFeeds');` is present in your tag. Without it, no client-side feed fires.
#### Google does not recognise my segment. Why?
The technical name probably contains a special character. Only letters, figures and underscores are accepted.
#### Do I need to fill in consent statuses?
No. The Google Ads remarketing tag handles consent directly for this connector.
## Partner documentation
Google Ads documents its own platform at . Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.mediarithmics.io/connectors/destinations/google/ads-pixel.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.