> For the complete documentation index, see [llms.txt](https://help.leadboxer.com/leadboxer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.leadboxer.com/leadboxer/guides/filter-leads-from-ad-campaigns.md).
# Filter Leads from ad campaigns
About your setup\
Getting data from your ad campaigns works best if you make use of UTM tags.
If you are not familiar or would like to learn more, please see this article: [getting started with UTM tags](/leadboxer/capture-website-and-email/website/tracking-marketing-campaign-data-utm-tags.md)
#### Example
If you want to see only the leads coming from paid ad campaigns:
1. Open **Leads & Accounts** and add the **Utm Tags** filter (under the behavioural filters).
2. Enter the UTM value your ads use, for example `cpc` (or `paid`, `ppc`, whatever you use as `utm_medium` in your ad links). To look at one campaign, enter the campaign name you use as `utm_campaign`.
3. Add the **First Source / First Medium / First Campaign** or **Last Source / Last Medium / Last Campaign** columns to see where each lead came from. "First" is the visit that brought the lead in, "Last" is the most recent one.
4. Save the filters as a [Segment](/leadboxer/using-the-app/elements/segments.md), turn on a daily notification in HTML format and add your marketing team as recipients.
Google Ads clicks without UTM tags can still be recognised by their `gclid`. See [UTM tags for Google AdWords](/leadboxer/capture-website-and-email/website/utm-tags-for-google-adwords.md).
---
# 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.leadboxer.com/leadboxer/guides/filter-leads-from-ad-campaigns.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.
