> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/partner/what-would-you-like-to-learn-about/platform-features/tracking/google-ads-and-impact.com-css-partner-tracking.md).

# Google Ads & impact.com - CSS Partner Tracking

impact.com makes it possible for Comparison Shopping Service (CSS) partners advertising on Google Ads to turn any existing catalog landing page into a trackable destination by simply adding a parameter to the URL. This means CSS partners aren't limited to pre-built tracking links; you can link straight to product pages while still generating trackable clicks for yourself.

## Partner setup

### Prerequisites

Confirm with the brand that they have enabled the [Comparison Shopping Service (CSS) Partner Tracking](/brand/what-would-you-like-to-learn-about/platform-features/tracking/set-up-tracking/accept-clicks-on-landing-pages.md) functionality.

{% stepper %}
{% step %}

### Tracking requirements

Add the `irmp` parameter with your impact.com Partner ID and the `irad` parameter with the respective ad ID (usually the catalog ID) to the desired product page. This will usually be listed in the catalog you're using.

Don't use impact.com tracking links. Instead, link directly to the product pages, adding the necessary `irmp` and `irad` tracking parameters. When the impact.com tag on the page detects these parameters, it will generate a click.

**Example:**

```
https://www.brand.com/product-page?irmp=12345678&irad=54321
```

{% endstep %}

{% step %}

### Brand requirements

Consult with the brand if they need additional analytics parameters to be added to the landing pages.

**Example:**

```
https://www.brand.com/product-page?irmp=12345678&irad=54321&utm_medium=css
```

{% endstep %}

{% step %}

### Additional Parameters

Add `subId1`, `subId2`, `subId3`, and `sharedid` parameters to the product pages as needed.

**Example:**

```
https://www.brand.com/product-page?irmp=12345678&irad=54321&utm_source=css&subId1=ABC&subId2=DEF&subId3=XYZ&sharedid=123456
```

Additional parameters that can be added to the product landing page are available here: [Direct Tracking Parameters](/other/reference-documentation/direct-tracking-parameters.md).
{% endstep %}
{% endstepper %}

### What you don't need

* Domain certification isn't required during the setup process, since you're linking directly to the brand's site rather than routing through a third-party redirect.
* The `force_deeplink=1` parameter isn't needed either, since it only applies to redirect-based tracking links.
* The `u=` parameter in tracking links is also unnecessary, as you're bypassing the gateway entirely.

## Troubleshooting

| Symptom                                                             | Likely cause                                                                                                     | Fix                                                                                                                                                                                                                                                                                                        |
| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Clicks are flatlined.                                               | Brand has not implemented UTT or PLA tracking, or the CSS Partner Tracking feature was not enabled on their end. | Confirm with the brand that their landing page tracking implementation is active and firing on all landing pages, and ensure they have the [CSS Partner Tracking](/brand/what-would-you-like-to-learn-about/platform-features/tracking/set-up-tracking/accept-clicks-on-landing-pages.md) feature enabled. |
| Parameters appear in Tracking Template but not on the landing page. | Wrong Google Ads field used.                                                                                     | Move parameters from Tracking Template to Final URL Suffix.                                                                                                                                                                                                                                                |
| Attribution works for some brands but not others.                   | Brand may use www→non-www redirects that strip query parameters.                                                 | Ask the brand to confirm their site preserves URL parameters across redirects.                                                                                                                                                                                                                             |
| Sub IDs not appearing in reports.                                   | SubId parameters not on the landing page URL.                                                                    | Ensure `subId1`, `subId2`, `subId3` are in the Final URL Suffix, not just the Tracking Template.                                                                                                                                                                                                           |
| Conversions tracked but attributed to wrong partner.                | Multiple partners using same or incorrect `irmp` value.                                                          | Each partner must use their unique [impact.com](http://impact.com/) partner ID.                                                                                                                                                                                                                            |

## FAQ

<details>

<summary>Does this work with Shopify stores?</summary>

Yes. Shopify plugin integrations use the Page Load API via server-side web pixels, which is fully compatible with `irmp` parameter detection.

</details>

<details>

<summary>Can I still use my existing redirect tracking links alongside this?</summary>

Don't use both types of tracking in Google Ads, only direct tracking. Use direct links in Google Ads. Use traditional tracking links outside Google Ads.

</details>

<details>

<summary>Does the brand see my partner data / do I see other partners' data?</summary>

No. Each Direct Traffic Tracking rule is isolated per partner. Your `irmp` value only triggers attribution for your account.

</details>

<details>

<summary>What if the brand doesn't have UTT or PLA?</summary>

This method requires a landing page tag. If the brand only uses click ID server-side or promo codes, the `irmp` method won't work. The brand would need to implement UTT or PLA first.

</details>


---

# 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 dynamically by asking a question.

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

```
GET https://help.impact.com/partner/what-would-you-like-to-learn-about/platform-features/tracking/google-ads-and-impact.com-css-partner-tracking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
