> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/monetization/merge-duplicate-identities.md).

# Merge duplicate identities

Merge duplicate commercial accounts or brands while keeping old references, history, and evidence.

Podigee Audio Video Ad Server can merge duplicate commercial accounts or brands into one canonical record. After the first mention, this article uses Podigee Ad Server for the product name. The canonical record remains the one your team uses, while old references continue to resolve and the history of each record remains available.

Use this task only when the records represent the same business identity. Do not merge two related companies, two brands with different legal ownership, or records that only have similar names.

## Before you start

* You have permission to merge identities in the selected workspace.
* You have confirmed the legal or business identity outside the duplicate records.
* You know which record is the canonical record.
* You know every duplicate that must resolve to the canonical record.
* You have checked active Campaigns, bookings, delivery evidence, finance records, and external references for each record.

Merging is a durable identity change. It is not a display-only cleanup and it is not a way to delete old history.

## Check for an existing identity first

When you create or link a Commercial account, search the directory before you add another record. If Podigee shows a matching account, review it and use the existing account when it is the same organization.

![A duplicate warning with the matching Cedar and Vale Media account and a Review and use account action.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-f4fa0b8bb424e09875940ee422c742e8e842d0b6%2Fdoc-monetization-014-duplicate-account-warning.png?alt=media)

*Use the matching account when the organization identity is the same.*

If duplicate records already exist, continue with the merge task. Do not create another record to avoid the decision.

## Open the merge task

1. Open **Monetization > Revenue jobs**.
2. Select **Lifecycle and identity**.
3. Select **Merge duplicate records**.

## Choose the canonical record and duplicates

1. In **Canonical record**, select the commercial account or brand your team will keep.
2. Check its current name, type, version, owner, and active work.
3. In **Duplicate records**, select one or more records of the same type.
4. Check every selected duplicate and remove any record that is a separate business identity.

The canonical record and every duplicate must be active, distinct records of the same type. Archived records, identities already used as aliases, and mixed types cannot be merged.

![The Commercial accounts directory filtered to one advertiser named Cedar and Vale Media.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-80b98e39287809ab24a383a2a79f23794657b876%2Fdoc-monetization-014-commercial-account-directory.png?alt=media)

*Search and filter the directory before you create a new account.*

## Review the merge boundary

Podigee shows that the canonical record stays authoritative. Review:

* The canonical record and its exact saved version.
* Every duplicate and its exact saved version.
* The record type for the complete merge set.
* The current owner, brands, Campaigns, bookings, delivery records, and finance references.
* The effect on old references and future work.

Do not continue if the selected records changed while the task was open. Reopen the task and review the current versions.

## Apply the merge

1. Confirm that the canonical record represents the identity your team will continue to use.
2. Confirm that each duplicate is the same identity and not a related organization.
3. Confirm that you reviewed the exact versions and the merge effect.
4. Select **Merge duplicates**.
5. Wait for the result page.

The merge takes effect at the current boundary. Podigee records the canonical identity, every alias, the exact source versions, the merge lineage, and the decision evidence.

## Confirm the result

Check the result page for:

* **Merged** state.
* The canonical record and its identity type.
* Every duplicate listed as an alias.
* The merge lineage reference and result evidence.

Then check one old reference from the Campaign, booking, delivery, or finance area. It must resolve to the canonical record without changing the original event or money record.

The duplicate roots are no longer available as separate active identities. Their exact history, old references, and evidence remain available to permitted users.

## If Podigee blocks the action

* **At least one duplicate is required:** Select one or more duplicate records.
* **The records have different types:** Merge Commercial accounts with Commercial accounts, or brands with brands. Do not mix types.
* **A record is archived:** Archived identities cannot be merged. Review the archive and identity history before you decide what to do.
* **A record is already an alias:** Open the current canonical record and do not merge the alias a second time.
* **The records are the same exact record:** Remove the duplicate selection and choose a distinct record.
* **An exact version is unavailable:** Reopen the task and select the current version for every identity.
* **The lineage check fails:** Stop. Do not retry with a different digest or a different canonical record until the identity set has been reviewed again.

## Expected result

One canonical identity remains authoritative. Old references resolve to it, while the history, delivery evidence, and money records of every merged record remain available and traceable.

## Next useful tasks

Use [Create or link a Commercial account](/documentation/grow-and-monetize/monetization/create-or-link-a-commercial-account.md) when the identity does not yet exist. Use [Reconstruct and export audit evidence](/documentation/grow-and-monetize/monetization/reconstruct-and-export-audit-evidence.md) when you need to show the merge set, exact versions, actor, and result.


---

# 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.podigee.com/documentation/grow-and-monetize/monetization/merge-duplicate-identities.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.