--- title: "Campaign conflicts and automatic updates" slug: "campaign-conflicts-and-automatic-updates" description: "When you run and publish a campaign, Campaign Manager publishes actions and updates published actions based on action type attributes, campaign attributes, and published actions' statuses to avoid conflicts." updated: 2024-05-03T05:42:53Z published: 2024-05-03T05:42:53Z canonical: "docs.zilliant.com/campaign-conflicts-and-automatic-updates" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.zilliant.com/llms.txt > Use this file to discover all available pages before exploring further. # Campaign conflicts and automatic updates When you [run and publish](/v1/docs/run-a-campaign) a [campaign](/v1/docs/about-campaigns), Campaign Manager publishes [actions](/v1/docs/about-campaigns#actions) and updates published actions based on [action type attributes](/v1/docs/about-action-types#attributes), [campaign attributes](/v1/docs/about-campaigns#attributes), and published actions' statuses to avoid conflicts. ## Campaign conflicts When you run multiple campaigns at the same time, it's possible for multiple records with the same PGA scope to satisfy multiple campaigns’ thresholds and scopes. An [action type’s rank](/v1/docs/about-action-types#attributes) and [campaign’s rank](/v1/docs/about-campaigns#attributes) determine how Campaign Manager handles conflicts. The following images illustrate this process. --- ![Campaigns%20Scopes%20&%20Actions%20Part%201](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/Campaigns%20Scopes%20&%20Actions%20Part%201.png?sv=2026-02-06&spr=https&st=2026-11-20T03%3A28%3A30Z&se=2026-11-20T04%3A28%3A30Z&sr=b&sp=r&sig=xaVaHn4ipOAr6k3rEq%2FKVVEJ%2FRLXEnv0KWY38iZOkXI%3D) --- ![Campaigns%20Scopes%20&%20Actions%20Part%202](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/Campaigns%20Scopes%20&%20Actions%20Part%202.png?sv=2026-02-06&spr=https&st=2026-11-20T03%3A28%3A30Z&se=2026-11-20T04%3A28%3A30Z&sr=b&sp=r&sig=ZfX73LKH1LI5pYPKKoJUfg2Rc%2BSVcmgfnnfwv1opy4E%3D) --- Campaign Manager handles conflict resolution during a campaign's validation. Rows that can’t be published due to a conflict automatically have their **Is Valid** boxes unchecked and a description of the conflict auto-populated in their corresponding cell under the **Validation** column. For more details, read **Existing Action Update** under [Action validation](/v1/docs/validate-campaign-actions#action-validation). If you run a campaign and it experiences PGA scope conflicts with published actions, the following rules apply: - Active, published actions with the *Pursuing* status or a closed status (*Dismissed, Snoozed, Won, Lost, Accepted,* or *Rejected*) will block actions from any campaign with the same PGA scope. - Published actions with the *Identified* status and the same PGA scope and Action Type ID combination will [update](/v1/docs/campaign-conflicts-and-automatic-updates#campaign-updates). - Published actions with the *Identified* status and the same PGA scope, but a different Action Type ID, will remain unchanged. With the same configuration as the preceding image, the following image displays the results when you run and publish campaign *A* followed by campaign *B*. --- ![Run%20Campaign%20A%20then%20Campaign%20B](https://cdn.document360.io/24f960e8-3c1c-4c18-a2c6-83b6ae4aab84/Images/Documentation/Run%20Campaign%20A%20then%20Campaign%20B.png?sv=2026-02-06&spr=https&st=2026-11-20T03%3A28%3A30Z&se=2026-11-20T04%3A28%3A30Z&sr=b&sp=r&sig=NNcXQ9Sta5jhEBKvurmn3DUngb2iB6OmhZna%2FwS4dNo%3D) --- ## Campaign updates If you run and publish a campaign, and then run a campaign with the same published action types, Campaign Manager updates the corresponding actions as needed. Campaign Manager performs three underlying processes when updating actions: - [Updating](/v1/docs/campaign-conflicts-and-automatic-updates#updating-existing-published-actions) existing published actions - [Canceling](/v1/docs/campaign-conflicts-and-automatic-updates#canceling-outdated-campaign-actions) outdated campaign actions - [Inserting](/v1/docs/campaign-conflicts-and-automatic-updates#inserting-new-actions) new campaign actions ### Updating existing published actions During a campaign’s validation process, Campaign Manager identifies any published actions with: - The *Identified* status - The same PGA Scope and Action Type ID combination Campaign Manager then flags them as **Is Valid** and **Is Update** in the **Action Review** worksheet. When you publish a campaign, Campaign Manager also updates its data based on the latest campaign you ran in the **Action Review** worksheet. Campaign Manager updates the following fields for their corresponding published actions: - **Campaign Id**—Campaign Manager updates this to match the latest campaign you ran with the same action - **Campaign Name** - **Action Type Name**—Campaign Manager updates this based on the Action Types worksheet - **Action Impact** - **Current** - **Target** - **Action Priority** - **Talk Track** - **Product Group Description** - **Visibility Period After Closed**—Campaign Manager updates this based on the currently-publishing campaign’s [dropdown actions worksheet](/v1/docs/about-campaigns#actions) - **Reactivation Periods**—Campaign Manager updates this based on the Campaign Settings worksheet This process doesn’t update published actions with the *Pursuing* status or any closed status (*Dismissed, Snoozed, Won, Lost, Accepted,* or *Rejected*). Note If Campaign Manager identifies campaign actions with the same PGA Scope and Action Type ID combination, running and publishing a campaign can update actions that were published as part of a different campaign. ### Canceling outdated campaign actions When you publish a campaign, Campaign Manager automatically cancels any previously-published action if it meets all three conditions: - The previously-published action has the same Campaign ID as an action in the campaign you’re publishing. Campaign Manager can only cancel actions associated with the same campaign you’re publishing. - The previously-published action has the *Identified* status. - There is no action of the same PGA scope and Action Type ID present with the **Is Valid** box checked in the **Action Review** worksheet. Campaign Manager doesn’t cancel any published actions with the *Pursuing* status or any closed status (*Dismissed, Snoozed, Won, Lost, Accepted,* or *Rejected*). These conditions can occur when you change [campaign thresholds](/v1/docs/define-campaign-thresholds), [customer scope](/v1/docs/customer-scope), [product scope](/v1/docs/product-scope), or campaign [limits](/v1/docs/common-questions-campaign-manager#how-do-i-specify-a-limit-for-a-campaign), or when you rerun the underlying [Sales IQ](/v1/docs/about-sales-iq) engines based on updated data. ### Inserting new actions During a campaign’s validation, Campaign Manager identifies an action with the following details as a *new* action: - The action is flagged as **Is Valid** in the **Action Review** worksheet. - The action doesn’t conflict with any published actions. When you publish the campaign, Campaign Manager creates this action as a new action. Combination of action type scope, customer ID, product group ID, and record ID. In Campaign Manager, PGA scope defines unique actions. It specifies how Campaign Manager handles potential duplicate actions in a single publish, as well as how new actions are published against active, published actions. To navigate, go to **Campaign Manager** > **Action Types** > **Action Types**. To navigate, go to **Campaign Manager** > **Campaign Manager** > **Campaign Settings**.