> For the complete documentation index, see [llms.txt](https://community.commandersact.com/customer-success/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/customer-success/inspiration/audience-sharing/advertising-campaign-management.md).

# Advertising campaign management

To remedy this, we show you how to leverage the storage and reconciliation capabilities of our solutions.

Without a complex project, you can learn how to unify your online and offline data around a unique identifier to activate enriched audiences for your partners.

#### **Benefits:**

* **Unified Customer View:** Thanks to reconciliation around a unique identifier, you can transform fragmented interactions (web, app, store) into consistent and actionable audience segments.
* **High-definition targeting**: You can overcome the limitations of cookies by sending your partners enriched profiles with their actual purchase history, guaranteeing a much higher ROAS.
* **Agile activation**: You can test new use cases (e.g. excluding offline buyers from your web campaigns) by simply consuming additional event streams.


---

# 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:

```
GET https://community.commandersact.com/customer-success/inspiration/audience-sharing/advertising-campaign-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.