Bilibili Sanlian Ads Delivery Reporting

Problem It Solves

When an engineer needs to answer spend, click, and conversion questions for Bilibili Sanlian ads, delivery reporting is the practical source of those metrics, while ad management endpoints do not return spend, impression, or click data. This skill turns a custom report query into an executable workflow: validate access_token and account_id, assemble a POST /open_api/report/v3/custom/query request using official dimension and metric names, then read the returned rows. It is useful for delivery performance, not for account balance, budget, or cash flow.

How It Works And Boundaries

• Rows only exist when spend occurred: a missing date or object is not an API failure and should not trigger blind retries.
• Mode selection determines metrics: account-level queries use account_id; object-level queries switch between legacy mode via campaign_id, unit_id, or creative_id, and creative-driven 2.0 mode via promotion_id or media_id. The metric sets differ and must not be mixed.
• Query one day at a time: start_time and end_time must be the same date; multi-day ranges require sequential day-by-day calls, stopping and inspecting the failed day rather than skipping it or fanning out.
• Choose money precision deliberately: suffix-less fields are yuan and good for display; _milli fields are integer milli-cents, where 1 yuan = 100000, and are better for reconciliation.
• Split filters and page carefully: each filter item accepts at most 100 IDs and non-empty filters[].values; hour granularity increases row count and requires paging.