Introducing the account-level Agent Preferences - an optional open text field on each account where you can capture account specific details such as brand voice, campaign goals, recurring caveats, and any other account-specific guidance - that are accessible by your Agents when needed. You'll find the field at Account Command Center → More Actions → "Agent Preferences."

When you @-mention an account in AI chat, the preferences you've saved for that account are automatically included in the prompt the assistant sees, so its responses follow that guidance for that account.

This makes your agents far more scalable across accounts. Instead of stuffing every account nuance into the agent itself — creating instruction bloat — the agent can now pull in the account-specific details only when it needs them, straight from that account's Command Center.

A few things to know:

• Preferences only flow in when the account is explicitly @-mentioned in the chat turn.
• Access controls are respected: preferences are only pulled for accounts the user already has access to.
• This is currently behind a feature flag (but not for long). It can be enabled on request in the meantime.

Facebook Ads & Facebook Page Insights: updated for Meta's latest Graph API

We've upgraded both NinjaCat's Facebook Ads and Facebook Page Insights connectors to Meta's Graph API v25. Alongside the Facebook Ads v25 upgrade, this release also restores reporting for Page Impressions (affected by Meta's November 2025 Pages API change) and adds new paid/organic breakdown metrics at both the Page and Post level on the Page Insights side.

What's new — five new metrics (Facebook Page Insights):

• Page Media Views (Paid)
• Page Media Views (Organic)
• Post Media Views (Paid)
• Post Media Views (Organic)
• Post Media Views (Followers)

The Page-level paid/organic split is new capability with no prior equivalent in NinjaCat. The Post-level breakdowns replace previously-deprecated post impressions paid/organic/fan metrics.

What's changed:

• The metric previously labeled Page Impressions is now labeled Page Media Views, matching Meta's naming. Existing saved reports, dashboards, and scheduled deliveries continue to work — the metric's identity is unchanged, only its label and backend API call have moved.
• 11 legacy Page Impressions variants (paid, viral, and the 9 story-type breakdowns) have been deprecated by Meta and are no longer available when building new reports. Saved reports will continue to return data through Meta's current API window; once Meta retires them later in 2026, those reports will stop returning data for those columns. Where Meta has provided a replacement, we've mapped to it. Viral-reach has no equivalent in the new API.

What you don't need to do: Existing reports, dashboards, and scheduled deliveries continue to run on both connectors. No migration step required.

Chart widgets with "Show Metrics as % of Total" enabled now support a new "Auto-Scale Axis" toggle in the Metric Axis options. Instead of locking the y-axis to 0–100%, the axis fits the actual data range with clean tick intervals, so charts dominated by small percentages are much easier to read.

The toggle works with both single and multiple y-axis configurations and accounts for comparison-period data when calculating the range. It's off by default — flip it on per widget when you want the tighter view.

Chart widgets with "Show Metrics as % of Total" enabled now support a new "Auto-Scale Axis" toggle in the Metric Axis options. Instead of locking the y-axis to 0–100%, the axis fits the actual data range with clean tick intervals, so charts dominated by small percentages are much easier to read.

The toggle works with both single and multiple y-axis configurations and accounts for comparison-period data when calculating the range. It's off by default — flip it on per widget when you want the tighter view.

Facebook Ads & Facebook Page Insights: updated for Meta's latest Graph API

We've upgraded both NinjaCat's Facebook Ads and Facebook Page Insights connectors to Meta's Graph API v25. Alongside the Facebook Ads v25 upgrade, this release also restores reporting for Page Impressions (affected by Meta's November 2025 Pages API change) and adds new paid/organic breakdown metrics at both the Page and Post level on the Page Insights side.

What's new — five new metrics (Facebook Page Insights):

• Page Media Views (Paid)
• Page Media Views (Organic)
• Post Media Views (Paid)
• Post Media Views (Organic)
• Post Media Views (Followers)

The Page-level paid/organic split is new capability with no prior equivalent in NinjaCat. The Post-level breakdowns replace previously-deprecated post impressions paid/organic/fan metrics.

What's changed:

• The metric previously labeled Page Impressions is now labeled Page Media Views, matching Meta's naming. Existing saved reports, dashboards, and scheduled deliveries continue to work — the metric's identity is unchanged, only its label and backend API call have moved.
• 11 legacy Page Impressions variants (paid, viral, and the 9 story-type breakdowns) have been deprecated by Meta and are no longer available when building new reports. Saved reports will continue to return data through Meta's current API window; once Meta retires them later in 2026, those reports will stop returning data for those columns. Where Meta has provided a replacement, we've mapped to it. Viral-reach has no equivalent in the new API.

What you don't need to do: Existing reports, dashboards, and scheduled deliveries continue to run on both connectors. No migration step required.

Template Builder now lets you display any metric as a percentage of its column total — so you can see at a glance what share of spend, impressions, clicks, or any other metric each row represents.

Turn on "Show Metrics as % of Total" at the widget level, or override on a per-metric basis from the metric edit modal. The percentage is dynamic: when a viewer applies filters or changes the date range, the denominator recalculates against the visible data. The setting is available across Tables, Pivot Tables, Charts (including stacked and 100% stacked), and Dynamic Text, and works with both standard and custom metrics, including rate metrics like CTR and CPC. Tables and Pivot Tables also support an independent toggle for comparison values.

Template Builder now lets you display any metric as a percentage of its column total — so you can see at a glance what share of spend, impressions, clicks, or any other metric each row represents.

Turn on "Show Metrics as % of Total" at the widget level, or override on a per-metric basis from the metric edit modal. The percentage is dynamic: when a viewer applies filters or changes the date range, the denominator recalculates against the visible data. The setting is available across Tables, Pivot Tables, Charts (including stacked and 100% stacked), and Dynamic Text, and works with both standard and custom metrics, including rate metrics like CTR and CPC. Tables and Pivot Tables also support an independent toggle for comparison values.

Google Ad Manager creatives now render as visual previews directly in your NinjaCat reports and dashboards.

Add the new Creative Preview dimension to any Google Ad Manager report and each row will display the rendered creative alongside its performance metrics.

A couple of things to know:

• The first time a creative is viewed, its preview is generated on demand and may take a few seconds to appear. Every view after that loads instantly from cache.
• Some cells will legitimately appear blank — for example, when a creative has no renderable asset, is paused or archived, is a House Ad or unfilled-inventory placeholder, or is a custom/VAST template with a missing asset. These are expected and not a product issue.

Coming soon: we're rolling out an enhancement so previews are pre-generated as creatives sync from Google Ad Manager, making that very first view instant too.

A new standard dataset, Dataset Export History, is now available in NinjaCat. It surfaces export configurations and run history for dataset exports across an organization, including current status, schedule, destination, and per-run results — rows, bytes, files, errors, and timing. Use it to monitor export health, troubleshoot failed runs, and build reports or agent workflows on top of export activity without leaving the platform.

A new standard dataset, Dataset Export History, is now available in NinjaCat. It surfaces export configurations and run history for dataset exports across an organization, including current status, schedule, destination, and per-run results — rows, bytes, files, errors, and timing. Use it to monitor export health, troubleshoot failed runs, and build reports or agent workflows on top of export activity without leaving the platform.