> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/crm-marketing/campaign-report.md).

# Campaign Report

A Campaign Report is a feature that provides comprehensive performance analysis showing how much various CRM campaigns — such as Push Messages, Kakao Messages, and SMS — have contributed to actual business goals.

Beyond simple open rates or click rates, you can verify the tangible value of a campaign with data: **'which message actually led to a customer's final purchase'** and **'whether a message influenced a purchase even if it wasn't clicked'**. Use CRM performance analysis to improve your campaign strategy based on data and prove results.

![](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-a08d0a8ec49c20abb2226f81955fa62a1db62217%2Fbfd5ed417c95b3e16a8025129071fc9bfc3952df_511df95e4b6bb63e.jpg?alt=media)

* **Customized Performance Measurement** You can set the key actions that match your business and campaign goals — not just 'purchase completed', but also 'sign-up', 'add to cart', 'event participation', and more — as 'conversion goals' to measure performance.
* **Analyzing Hidden Contribution of Messages** Measure not only 'direct conversions' where a user clicked the message and converted immediately, but also 'indirect conversions' where a user viewed the message and then visited the app/web and converted later. This lets you capture the hidden influence of messages that you may have been missing.
* **Clear Data-driven Decision Making** Compare campaign performance using the same criteria to clearly identify which message was most effective. Data-driven decision making becomes possible — reinforce successful strategies and improve inefficient ones.
* **Funnel Data at a Glance** Performance data based on your configured criteria is provided as a table chart showing step-by-step figures from 'send → click → ... → final conversion'. Intuitively identify at which stage users primarily drop off and find areas for improvement.


---

# 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://docs.hackle.io/en/crm-marketing/campaign-report.md?ask=<question>&goal=<user_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.
