> 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
As a Comparison Shopping Service (CSS) partner advertising on Google Ads, you can turn any existing catalog landing page into a trackable destination by adding parameters to the URL. You aren’t limited to pre-built tracking links — you can link straight to product pages and still generate trackable clicks.
## Partner setup
### Prerequisites
Confirm with the brand that they've enabled [CSS Partner Tracking](/brand/what-would-you-like-to-learn-about/platform-features/tracking/set-up-tracking/accept-clicks-on-landing-pages.md).
{% stepper %}
{% step %}
### Tracking requirements
Add these parameters to the product page URL: `irmp` with your impact.com partner ID, and `irad` with the ad ID (usually the catalog ID, 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 generates a click.
**Example:**
```
https://www.brand.com/product-page?irmp=12345678&irad=54321
```
{% endstep %}
{% step %}
### Brand requirements
Ask the brand whether they need additional analytics parameters on the landing pages.
**Example:**
```
https://www.brand.com/product-page?irmp=12345678&irad=54321&utm_medium=css
```
#### How a click is created
The `irmp` and `irad` parameters trigger a trackable click through the landing page tag. The brand must implement one of the following on every landing page:
* Universal Tracking Tag (UTT) configured with the Identify function.
* PageLoad API (PLA) requests.
{% 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
```
For more parameters you can add to the landing page, see [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, since it applies only to redirect-based tracking links.
* The `u=` parameter isn’t needed, since you bypass the gateway.
## Troubleshooting
| Symptom | Likely cause | Fix |
| --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| No clicks are tracked. | 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. | Sub ID parameters not on the landing page URL. | Make sure `subId1`, `subId2`, and `subId3` are in the *Final URL Suffix*, not just the *Tracking Template*. |
| Conversions tracked but attributed to wrong partner. | Multiple partners using the same or incorrect `irmp` value. | Each partner must use their unique impact.com partner ID. |
## FAQ
Does this work with Shopify stores?
Yes. Shopify plugin integrations use the PageLoad API via server-side web pixels, which is fully compatible with `irmp` parameter detection.
Can I still use my existing redirect tracking links alongside this?
Not in Google Ads. Use direct links in Google Ads, and use your existing tracking links everywhere else.
Can other partners see my data, or can I see theirs?
No. CSS Partner Tracking is isolated per partner. Your `irmp` value only triggers attribution for your account.
What if the brand doesn't have UTT or PLA?
This method requires a landing page tag. If the brand only uses server-side click IDs or promo codes, the `irmp` method won't work. The brand must implement UTT or PLA first.
---
# 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://help.impact.com/partner/what-would-you-like-to-learn-about/platform-features/tracking/google-ads-and-impact.com-css-partner-tracking.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.