Duplicating a campaign, ad set, or ad can save setup time, but the copy also inherits context: objective, budget structure, audience, dates, placements, conversion event, URLs, creative, exclusions, and automation settings. The safe workflow treats duplication as a new version that must earn approval rather than as a shortcut around QA.

VISUAL LESSON

What you will learn

  1. 01Choose campaign, ad-set, or ad duplication deliberately.
  2. 02Create a source-to-copy settings diff.
  3. 03Launch without overwriting baseline evidence.
An approved campaign blueprint branches into a controlled copy with comparison checkpoints and a separate launch gate
A duplicate is a new version: reuse the structure, then re-approve every inherited dependency.

ILLUSTRATIVE WORKED EXAMPLE

Review an illustrative inherited-settings checklist

Settings inheritedIllustrative audit
24
Intentionally unchangedDocumented
14
Changed for new briefRe-approved
8
Blocked before launchOld date and URL
2
Illustrative example—not a benchmark. Replace every sample value with your own campaign, market, and measurement data.

PRACTICAL INTERFACE MAP

Create a controlled campaign copy

Source01Freeze the approved baseline

Record IDs, status, objective, dates, budgets, events, audiences, placements, creative, destination, tracking, and recent activity history.

Duplicate02Copy the correct level

Select campaign, ad set, or ad, choose the supported destination, keep the copy paused, and assign a unique version name.

Diff03Review inherited and changed fields

Compare every level, run test conversions and previews, obtain approval, then publish the copy without editing the source.

Conceptual walkthrough. Labels, controls, and availability can vary by account, region, plan, and interface version; verify the current screen before acting.

STEP-BY-STEP LESSON

Approved source → paused duplicate → settings diff → independent launch

FreezeSource evidence
CompareInherited vs changed
PublishNew version

THE LEAD ATLAS METHOD

Lead Atlas Data can supply contacts researched for the duplicated campaign's exact business categories, market, and locations, keeping the outbound audience aligned with the new version rather than the old brief.See how custom list research works ↗
01

Decide what should be reused

Choose whether the reusable unit is the full campaign, one ad set, or one ad. Write the new campaign objective, market, offer, audience, budget, schedule, and learning question before clicking Duplicate.

Copying the entire campaign for one creative change can create duplicate budgets and fragmented reporting. Copying only an ad when the market or optimization event changed can hide important dependencies.

02

Capture the source version

Save the source campaign, ad-set, and ad IDs; status; objective; buying type; budget; bid strategy; dates; audience; exclusions; placements; event; attribution; creative; URL; tracking; and recent activity history. Keep the source unchanged during review.

Name the copy with market, objective, offer, date, and version. Avoid names such as copy or final that do not reveal lineage or purpose.

03

Duplicate into a paused state

Use the current Ads Manager duplication path and choose the correct destination campaign or ad set. Keep the copied objects off until the review is complete, and confirm that draft versus published state is visible at all three levels.

Check whether the interface selected Advantage+ settings, reused an identity, or changed an unavailable legacy option. Live account behavior outranks an old checklist.

04

Run the inherited-settings diff

Compare source and copy line by line. Reconfirm currency, timezone, dates, daily or lifetime budget, campaign spending, event, dataset, conversion location, attribution, audience controls, exclusions, placements, identity, creative enhancements, URL, tracking, form, and follow-up path.

Test the landing page and conversion, preview every selected placement, verify payment and permissions, and have a second reviewer confirm that every difference is either intended or blocked.

05

Publish and preserve causality

Turn on only the approved objects, annotate the launch, and monitor duplicate delivery, audience overlap, spend, events, policy, quality, and operational capacity. Do not change the source merely to make the comparison appear cleaner.

Deliverable: new-version brief, source snapshot, lineage and naming record, duplication-level decision, full settings diff, test evidence, placement previews, approval, launch annotation, activity-history check, rollback owner, and next review date.

THE TAKEAWAY

Duplicate only the level you intend to reuse, preserve the original, create a line-by-line diff, and publish the copy as a separately governed version.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.