Post-ID Scaling

Relaunch a proven ad as the same post, so its likes, comments and shares follow it.

Post-ID scaling relaunches a winning ad by pointing every new ad at the same underlying post, so the likes, comments and shares it earned carry into the new campaign instead of resetting to zero. Volume Creatives does this in one click, using the object_story_id field Meta exposes for exactly this purpose.

How Post-ID Scaling works

From your creatives to published Meta ads, step by step.

Find the winner

Analytics ranks your ads by ROAS, CPA and hook rate, so the ad worth scaling is obvious rather than a guess.

Read its post ID

Volume Creatives reads the effective_object_story_id off the winning ad, which is the ID of the post Meta is actually delivering.

Choose the new destinations

Pick the ad sets or campaigns the winner should also run in. Budgets and targeting come from the destination, not the old ad.

Launch, paused

The new ads are created against the same post ID, published paused, and every one carries the original engagement.

Why duplicating an ad normally loses your comments

When you build an ad from raw ingredients, Meta creates a brand new unpublished post behind it. Duplicate that ad five times and you have five separate posts, each starting from zero engagement, each collecting its own trickle of likes. The ad that had 4,000 likes and 200 comments is now six ads with the proof scattered across all of them. Nothing warns you this happened; the copies simply underperform the original and it is not obvious why.

object_story_id versus effective_object_story_id

These two fields cause most of the confusion. object_story_id is the field you set: it tells the ad creative to use a specific existing post. effective_object_story_id is what Meta returns: the post the ad is actually delivering. When you supply object_story_id directly they match. When you supply the raw ingredients instead, Meta generates a post for you and reports its ID back as effective_object_story_id. The practical rule: read effective_object_story_id off your winner, then feed that exact value as object_story_id on every new ad. That is the entire mechanism.

When not to use Post-ID scaling

Post-ID scaling is the right move when the creative is proven and you want its proof to travel. It is the wrong move when you are testing, because every ad sharing one post means you cannot tell the variants apart in reporting. It also locks the creative: editing the post changes every ad pointing at it. Test with separate ads, scale with Post ID.

What you get

Engagement compounds instead of resetting

Every duplicate points at one post, so likes and comments pool on a single ad rather than splitting across copies.

Works across ad sets and campaigns

The same post can run in as many ad sets as you need, all sharing the same social proof.

One click from Analytics

Find a winner in Analytics and relaunch it by Post ID without hunting for IDs by hand.

Bulk Post-ID launches

Scale several proven posts at once rather than one at a time.

Frequently asked questions

Does Post-ID scaling keep likes and comments?+

Yes. Every ad pointing at the same post shares that post's engagement, so likes, comments and shares appear on all of them and continue to accumulate in one place.

Can I use Post-ID scaling across different ad sets?+

Yes, and that is the common case. The same post can run in many ad sets and campaigns at once, each with its own budget and targeting, all sharing the social proof.

How do I find a Facebook ad's post ID?+

In Volume Creatives, Analytics surfaces it on the winning ad and relaunching is one click. Manually, you would query the ad's effective_object_story_id through the Marketing API, or find the post in Page publishing tools.

Does this work with Instagram placements?+

Yes. A post promoted this way runs across the placements you select, and the engagement is shared regardless of where each impression is served.