Campaign management in the NanoBuzz Platform

The campaign as a single source of truth

When a campaign starts, our team sets it up as a project in the platform: goals, markets, timeline, creator targets, product logistics and reporting scope. Every creator who joins the campaign becomes a record inside that project, carrying their profile, agreed deliverables, shipment status, submitted content and published posts. Nothing about the campaign lives in a side spreadsheet or a private inbox.

This structure is what lets one project manager coordinate hundreds of creators without losing anyone. The system shows exactly who is approved, who is waiting for product, who owes a draft, whose content is in review and who has published. When a creator stalls, the record shows it early enough to fix, replace or reschedule without endangering the flight.

Statuses that drive the work

Each creator moves through a defined pipeline: invited, applied, shortlisted, client approved, contracted, product shipped, product delivered, draft submitted, content approved, published, verified. Every transition is logged with a date, so the campaign timeline is reconstructable at any moment and bottlenecks are visible as they form, not after the deadline passes.

Deadlines attach to statuses. Delivery confirmation starts the content clock, submission triggers review, approval triggers the publication window. Our operations team works from queues generated by these statuses, which is why campaigns with 300 creators do not require 300 separate conversations to stay on track.

• One project per campaign with scope, timeline and creator list
• Per-creator pipeline from invitation to verified publication
• Deadlines derived from real events like delivery confirmation
• Queues for the operations team instead of inbox archaeology

Multi-market coordination without multi-agency chaos

For programs across several countries, each market runs as its own workstream inside the same project: local creators, local language briefs and local publication tracking. The consolidated view rolls markets up into one picture, so a marketing team in one office can follow a program running with creators recruited from a network of 20,000+ across 25+ European countries.

This is the same machinery we used to verify 900+ pieces of NutriBullet content from 500+ creators and to track 170+ ORLEN Paczka publications to 6.2M impressions. Campaign management is not a feature list for us. It is how the numbers on our case study pages became auditable facts.

The same project structure carries over to always-on programs, where the campaign never really ends: waves replace flights, but statuses, queues and consolidated views work identically, and your team keeps one mental model for everything we run together.