Bilibili Sanlian Ad Management

Problem

Legacy Bilibili Sanlian ads still follow the campaign → unit → creative hierarchy. Many ads were created before an account was allowlisted, or the account is not in the 2.0 allowlist, so they remain manageable only through v3 endpoints. This skill targets those legacy objects for creating, querying, listing, editing, batch operations, and one-click acceleration—not for 2.0 project / media.

How it works

• Read references before requesting: each action maps to a document under references/, reducing invented fields, enum values, and resource IDs.
• Query metadata before saving: promotion purpose, targeting, and bid ranges come from bilibili-sanlian-ads-metadata; creatives require prepared materials.
• Create top-down: campaign first, then unit, then creative, with preview, confirmation, and re-query after each ID.
• Run batch operations asynchronously: one request performs exactly one operation_type, such as pause, budget, bid, or targeting; poll task status and inspect every per-object result.
• Use acceleration cautiously: only eligible ocpc / ocpm units in delivery, check remaining budget first, and limit calls to 20 units.

Boundaries

• No cross-version access: v3 cannot read or write 2.0 project / media; v4 cannot manage legacy campaign/unit/creative objects.
• Legacy cannot be upgraded: new work belongs to delivery 2.0; existing legacy ads are still edited here.
• Business status matters: HTTP success does not imply object success, especially in batch and acceleration responses.
• Writes have real cost: budget, bid, and acceleration changes require confirmed account, objects, before/after values, and batch plan.