How to Run the Same Ad Across Multiple Ad Sets Without Copy-Pasting
Run the same Facebook ad across multiple ad sets by reusing one Post ID — so every copy shares one pool of likes and comments, with no copy-pasting per ad set.
To run the same Facebook ad across multiple ad sets without copy-pasting, you reuse one Post ID in every ad set rather than rebuilding the creative each time. Capture the Post ID of your ad once, then point every additional ad set at it with “Use Existing Post.” Because likes and comments are attached to the Post ID (not the ad set), all copies share a single growing pool of social proof — and with the right tool you can push that one ID into dozens of ad sets in a single action.
Key takeaways
- Social proof lives on the Post ID, so the same ID in every ad set = one shared pool of likes and comments.
- Use “Use Existing Post” in each ad set, or distribute one Post ID across all of them in a single step.
- Running one creative across many ad sets is how you test audiences/placements in parallel without changing the creative variable.
- Manual repetition is the risk: one wrong ID silently resets that ad set’s social proof to zero.
Why you’d run one ad across many ad sets
This is the backbone of clean parallel testing. You hold the creative constant and vary one thing per ad set:
- Audience testing — the same ad against five interest stacks, lookalikes, or geos.
- Placement testing — the same concept isolated to feed vs. Reels vs. Stories.
- Budget/bid testing — identical creative at different spend levels.
Keeping the creative identical across ad sets is what makes the test valid. If each ad set has its own separately-built copy of the ad, you’ve introduced a hidden variable (and split your social proof). One shared Post ID removes both problems at once. It’s also the mechanical core of horizontal scaling — replicating a proven winner across more audiences.
The manual way (and why it doesn’t scale)
Native Ads Manager can do this, but it makes you do it one ad set at a time:
- Build the ad in the first ad set and publish.
- Find its Post ID (see how to find a Facebook Post ID).
- In ad set #2, create a new ad, choose Use Existing Post, paste the ID.
- Repeat step 3 for ad set #3, #4, #5…
For two or three ad sets, fine. For twenty, you’re pasting the same ID twenty times — and every paste is a chance to grab the wrong ID and silently start that ad set at zero engagement.
| Manual “Use Existing Post” | Distribute one Post ID | |
|---|---|---|
| Build the ad | Once | Once |
| Add to each ad set | Paste ID, repeat per ad set | Select ad sets, distribute once |
| 20 ad sets | 20 manual repetitions | One action |
| Naming consistency | Manual, easy to drift | Identical automatically |
| Social proof | Shared if you paste correctly every time | Guaranteed shared |
The shortcut: distribute one Post ID
The faster pattern is to select your winning post once and distribute its Post ID across all target ad sets in a single step. Instead of N manual repetitions, it’s one operation that:
- Puts the exact same Post ID in every ad set (no mismatch risk),
- Keeps naming identical across all of them, and
- Guarantees one consolidated pool of likes and comments.
This is the same mechanic behind duplicating an ad without losing its social proof — just applied across many ad sets at once instead of one at a time.
A note on Advantage+ and campaign budget (CBO)
When your budget is set at the campaign level (Advantage+ campaign budget / CBO), running the same post across multiple ad sets still works — and the shared Post ID still consolidates social proof — but Meta decides how budget flows between those ad sets. That’s fine for letting the algorithm find the best audience, but it makes strict apples-to-apples audience testing harder, because spend isn’t evenly split. If your goal is a clean audience test, use ad-set-level budgets so each audience gets a controlled spend; if your goal is to let Meta optimize delivery, campaign-level budget with one shared post is a clean setup.
Common pitfalls
- Accidentally creating new posts. If you choose “Create Ad” instead of “Use Existing Post,” you’ve spawned a new Post ID and split your proof. Always switch to existing post.
- Editing the creative mid-test. Substantive edits can mint a new Post ID. Lock the creative once the test is live.
- Mixing IDs across the test. Half your ad sets on Post A and half on Post B fractures your social proof and muddies the read.
Do it in one step
If you’re testing one creative across many audiences, you shouldn’t be pasting a Post ID into ad set after ad set. Zendux’s Distribute feature takes one post and pushes it across every ad set you choose in a single action — identical naming, one shared pool of likes and comments, zero copy-paste.