> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/marketing-intelligence/settings/auto-merging-campaigns-by-id.md).

# Auto-merging campaigns by ID

If you're frequently updating the names of your campaigns, we recommend enabling the **"Auto-merge Campaigns by ID"** feature in your settings. This option allows us to look at the historical data for each integration and reprocess it, ensuring that older campaign names are updated based on their unique campaign IDs. We sync that data weekly.

This functionality is currently supported for **Google Ads**, **LinkedIn Ads**, and **Reddit Ads**.

**Note:** This does not impact LinkedIn **goal impressions**, as they are retrieved via a separate API endpoint.


---

# 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://docs.hockeystack.com/marketing-intelligence/settings/auto-merging-campaigns-by-id.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.