Understanding Platform Data Limitations

Panamplify pulls whatever a platform’s API makes available — but not every platform exposes every field, and that’s true no matter which reporting tool you use. Knowing these limitations up front saves you from building a report section around data that simply isn’t accessible.

Spend Isn’t Always Available Through Every Path

Some campaigns are executed through one platform but managed or reported through another — for example, inventory bought through a demand-side platform but pulled into a campaign manager for reporting. In cases like this, engagement metrics (impressions, clicks, video starts) typically come through cleanly, but spend often does not — it’s a known limitation of how some platforms pass data to third-party reporting tools, not a Panamplify gap. If a report needs spend for one of these campaigns, you may need to pull it directly from the platform actually executing the buy. See Why Is Spend Data Missing for Some Campaigns?

Creative Assets Are Often Filename-Only

Several programmatic and display platforms pass through a creative’s filename via their API, but not a preview image or click-through link. If a client wants a “Top Performing Ads” section with actual creative thumbnails, that content usually has to come from the platform or the client directly — it isn’t something any API-based connector can currently pull automatically.

Distinguishing Similar Campaign Types

Some platforms report multiple campaign formats (for example, standard Display and OTT/CTV) under a single umbrella without a clean label to separate them. When that happens, look for a secondary field that reliably differentiates the two — Video Starts is a common one: OTT/CTV placements register real values, while standard Display placements show zero. Line item and campaign names on these platforms are frequently locked by the client’s naming convention and can’t be renamed for clarity, so building your filter around a data field rather than a name pattern tends to hold up better over time.

Unusual Numbers Aren’t Always Errors

Not every surprising number is a bug. For example, OTT/CTV inventory can occasionally register clicks — that looks wrong at first glance (who clicks a TV ad?) but it’s expected: not all OTT inventory serves exclusively on set-top boxes, and some placements run on click-capable surfaces. Before assuming a number is broken, check whether there’s a legitimate platform-level explanation first.

Manually-Sourced KPIs

A small number of client-requested metrics — particularly custom KPIs some platforms only expose in their own dashboard exports — aren’t yet available through automated API pulls. If a client relies on one of these today, plan to bring it in manually until (or unless) that platform opens the field up.