> For the complete documentation index, see [llms.txt](https://community.commandersact.com/adloop/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.commandersact.com/adloop/vii-adloop-tracking-and-attribution/d-attribution-kpi-for-marketing-optimization/useful-clicks-1.md).

# Useful clicks 1

Optimizating your digital marketing only on conversions & revenue would mean that you leave out most of your campaigns. To answer this challenge, Adloop created the **useful click** .

## 1- What are useful clicks?

Well, that’s up to you!

YOU decide what makes a click useful to your business. Is a click useful only if the user sees more than 2 pageviews? Or if he sees a product page?

When setting up the Adloop Tracking & Attribution data source, you will have to choose the useful click definition, using goals & events from your Analytics data source. You can combine several goals & events if you want, using logical connectors “or” & “and”.

![](/files/SsBk828j8jojTGvAwwIc)

Here for example, a click will be considered useful if:

* there is at least 2 pageviews, or
* at least one product search, or
* at least one product view

## 2- Useful clicks KPI

noteTo create custom metric, visit \[\[our dedicated page|Calculated-metrics]]!

> To create custom metric, visit [our dedicated page](https://github.com/CommandersAct/Adloop-Documentation/blob/master/wiki/spaces/AHEN/pages/2001469485/Calculated+metrics/README.md)!

To analyze your digital marketing, we advise you to create two KPI using the useful clicks:

a - Cost per useful click

> Ad Spend / Useful Clicks

b - Useful click ratio

> Useful Clicks / Adloop Clicks

Adding those two KPI to your report will enable you to highlight any elements not driving enough qualified traffic.

It is especially interesting to compare the cost per useful click with the Advertising CPC, to highlight the difference between the two.


---

# 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://community.commandersact.com/adloop/vii-adloop-tracking-and-attribution/d-attribution-kpi-for-marketing-optimization/useful-clicks-1.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.