> 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/reporting-for-partners/click-reports/click-tracker-cpc-earnings-report-explained-for-partners.md).

# Click Tracker CPC Earnings Report Explained for Partners

{% hint style="warning" %}
**Important!** The report covered in this article is part of impact.com's legacy CPC tracking functionality and should only be used to view historic data. To see your CPC V2 payable clicks, see [Payable Click Data Report for Partners](/partner/what-would-you-like-to-learn-about/platform-features/reporting-for-partners/click-reports/payable-click-data-report-for-partners.md) instead.
{% endhint %}

Before the release of CPC V2, brands were able to sift through and reject partner clicks that fell out of contract or exceeded their payout budget. impact.com's CPC functionality no longer allows brands to reject clicks, instead allowing them to create highly customisable payout rules to predetermine what kind of clicks they're willing to pay out for.

#### Access the report

1. Open the **Click Tracker CPC Earnings** report.
2. Under the report heading, set the **Date Range**, select the **Program** for which you want to view reporting, then select ![](/files/UtRJFdjmzq4JXmuHsnuw) **\[Search]**.
   * View the *Table reference* below for more information.

<details>

<summary>Table reference</summary>

|                  |                                                                          |
| ---------------- | ------------------------------------------------------------------------ |
| **Table Column** | **Description**                                                          |
| Date             | The date on which the click event was generated.                         |
| ID               | The impact.com-generated action ID for the click event.                  |
| Brand            | The brand program for which you drove the click event.                   |
| Event Type       | The event type associated with the click event.                          |
| Status           | The action status for the click event (e.g., Approved).                  |
| Payable Clicks   | How many clicks within the click event you could have been paid out for. |
| EPC              | Your earnings per click (EPC) for the click event.                       |
| Earnings         | Your total earnings for a particular event type.                         |
| Tax              | The amount of tax assessed for the click event.                          |

</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/reporting-for-partners/click-reports/click-tracker-cpc-earnings-report-explained-for-partners.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.