Reading performance

The cross-creative grid

The Performance tab reads from the ad-performance store into a sortable grid, one row per creative you have pushed, each aggregated over a window. Think of it as a leaderboard for your ads: the page opens on a default window, lets you stretch it anywhere from 7 to 90 days, and sorts by spend, clicks, CTR, and ROAS so the creatives carrying the account float to the top.

Background crons pull fresh numbers from the connected platforms, and the grid refreshes live when new data lands. You do not have to reload to see the latest.

Per-creative signal goes a step further. Each creative is tied to its deployment and compared against your organization median, so a row reads as strong or weak relative to your own account rather than against some abstract industry number.

One detail surprises people: money is hidden from some teammates on purpose. Spend and ROAS are blanked out server-side for anyone without the view-spend permission, so a teammate can still see clicks and CTR but not cost. That is a permission, not a bug. If someone needs to see spend, that is a role change, covered under billing permissions.

The honest state of production: the grid is effectively empty. The only rows that exist are a handful of organic YouTube entries with zero impressions, not paid performance. There is nothing paid to read until a Meta ad actually runs. The deeper read-and-react cycle has its own chapter, the Performance Loop. This lesson is only about reading the grid itself.