> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/add-ons/paid-search-ppc/reporting-and-performance-reviews.md).

# Reporting & Performance Reviews

### Accessing Your PPC Reports

Your PPC reports are provided by your Customer Success Manager and are powered directly by Google Ads data. Once you receive your report link, you will have access to real-time campaign performance data that updates automatically.

The report link can be shared with anyone within your organization who would like visibility into campaign performance. Because the report updates automatically, you can continue using the same link each month without needing a new report to be sent.

For easy access, we recommend bookmarking the report link in your web browser. As long as your PPC campaigns remain active, you can use the bookmarked link to view real time performance data whenever you'd like. This allows you to check campaign results, lead activity, and performance trends at any time without waiting for a monthly report update.

### When Reports Become Available

As part of our initial campaign launch process, PPC reports are typically created approximately 30 days after your campaigns go live. This allows enough time for data collection and performance analysis during the first month of advertising.

Once your campaigns are live, reporting data is available in real time.

### What Your PPC Reports Include

Your report provides visibility into key campaign performance metrics, including:

* Keywords your campaigns are targeting
* Clicks, impressions, and other Google Ads performance metrics
* Conversions generated through your campaigns
* Conversion sources, such as phone calls and form submissions
* Target location maps
* Overall campaign trends and performance data

### Understanding Conversion Data

The conversion data displayed in your report comes directly from Google Ads. In some cases, conversion numbers may differ slightly from the leads shown within your website admin dashboard or our internal systems.

This can occur for several reasons:

* A user may call multiple times, but only be counted once in certain reporting systems.
* A visitor may click an ad and return later to complete a form submission.
* In some cases, Google may assign partial credit for a conversion if a user initially visited through a paid ad and later returned through another channel.

Because of these attribution methods, small differences between Google Ads reporting and website reporting are normal and expected.

### Historical Reporting Access

If PPC services are canceled, access to the live reporting dashboard will no longer be available. However, historical campaign data remains accessible within Google Ads, and our team can provide historical performance information upon request before cancellation.

\ <br>


---

# 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.doctorlogic.com/docs/add-ons/paid-search-ppc/reporting-and-performance-reviews.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.
