The paid amplification workflow: codes, validation, waves

Why amplification fails without a workflow

A Spark Ads code is a string a creator generates in their app, with an expiry window and an authorization scope. Partnership Ads permissions on Meta work differently but create the same dependency: the advertiser can only boost what the creator has correctly authorized. At the scale of one creator this is a favour over chat. At the scale of a nano campaign it is dozens of codes in different states, some expired, some scoped wrong, some never sent, and a media plan waiting on all of them.

Campaigns lose their best amplification window in exactly this gap: the organic post peaks while someone chases codes in private messages. We built the workflow because we run campaigns where the strongest content must be boostable within days, reliably, in several markets at once.

How the code registry works

Creators whose content is selected for amplification receive step-by-step instructions inside the campaign flow: how to generate the code, with which scope and duration, and where to submit it. Submitted codes land in the campaign's code registry, where each one is a record tied to its creator and publication.

Our team validates every code before it is needed: correct account, correct post, sufficient authorization window. Invalid or expiring codes trigger a follow-up with the creator while there is still time. Valid codes are then activated in planned waves that follow the media plan, prioritising content that earned amplification through organic performance.

• Clear generation instructions sent to each selected creator
• Central registry tying every code to a creator and publication
• Validation of scope, duration and account before launch
• Activation in waves aligned with the media plan
• Follow-ups triggered before codes expire, not after

Visible to clients, treated as secrets

Your team sees the state of amplification in the portal: which publications are selected, which codes are submitted, validated or activated, and which wave is live. What you see is status, not the codes themselves. Authorization codes are credentials, so the platform treats them as secrets: stored restrictively, never exposed in exports or client views, used only for the agreed campaign setup.

That combination, transparent status and confidential handling, is deliberate. It lets a client steer amplification decisions with full information while the sensitive material stays locked down. The same workflow supported programs where boosted creator posts carried national reach, including the ORLEN Paczka campaign that reached 6.2M impressions across 170+ publications.