We've made significant improvements to our FTP and S3 data connectors to improve sync reliability, visibility, and data protection.

What's Improved

More Predictable Sync Behavior

• Manual syncs now behave consistently and follow your configured file selection settings.
• Clear visibility into whether new data was ingested or if no updated files were found.

Clearer Sync History

• Sync records are now grouped and easier to interpret.
• Each sync shows the date range of the data that was ingested.
• Improved status messaging ("in progress" vs "completed").

Stronger Data Validation

• If required columns (such as account or date fields) are missing from a file, the sync fails safely with a clear error message.
• Prevents unintended data overwrites or deletions.

Improved Handling of Non-Numeric Values

• Metric columns containing values like empty strings or "NA" will no longer cause ingestion failures.
• These values are now safely treated as null.

More Reliable Data Flow

• Non–account-matched FTP/S3 data now loads correctly into datasets.
• Sync processing has been migrated to a more robust ingestion system designed for improved scalability and monitoring.

What This Means for You

• More reliable FTP/S3 ingestion
• Better visibility into what was processed
• Safer data updates

Whats New? We've added the ability for our system to automatically scale up computing power when needed. If an export starts to time out, the system will automatically retry it using a larger warehouse, giving it more processing capacity to complete successfully.

How does this help you? • Fewer failed exports — Large or complex exports are far less likely to time out • No action needed from you — The system handles retries and scaling automatically • Faster resolution — Exports self-heal in real time instead of requiring a support request

What's New: Two new audio metrics have been added to the Google Campaign Manager 360 connector:

• Audio Completions — The total number of rich media audio completions • Audio Completion Rate — The rate at which audio plays are completed, calculated as Completions ÷ (Plays + Replays).

What's New: We now have a new dimension of "Email Subject Line" now available in our Site Impact API Integration.

What's New?:

New date formats added have been added to our Email Smart Connector within DataCloud: • MM/d/yyyy — (e.g., 12/1/2025) • MMMM d, yyyy — (e.g., December 1, 2025) • MMMM dd, yyyy — (e.g., December 01, 2025) • d/M/yyyy — (e.g., 1/12/2025) • d-MMM-yy — (e.g., 1-Dec-25)

What New: Account ID and Account Number are now available as dimensions for Bing Ads in the NinjaCat. You can find them under the names of External Account ID and External Account Number.

Two new dimensions: Targeting Type and Targeting Value are now available in Pinterest Ads. These fields come from Pinterest's targeting_analytics endpoint, allowing you to break down campaign performance by targeting segment directly within NinjaCat.

As part of bringing in this new endpoint, 90+ existing Pinterest metrics (impressions, clicks, spend, conversions, video views, ROAS, and more) have also been mapped to the targeting-level breakdown, giving you a comprehensive view of how each targeting strategy is performing.

What's New?: The "Search Term" and "Search Term Match Source" dimensions are now available in NinjaCat for Google Ads Performance Max campaigns, allowing you to analyze search term performance data in our reporting interface.

What this means for you: If running Performance Max campaigns can now:

• Select "Search Term" and "Search Term Match Source" as dimensions in Google Ads reports
• View search terms attributed to Performance Max campaigns alongside advertiser-provided keywords

We're excited to announce that we've added support for Local Service Ads (LSA) within our Google Ads API provider integration.

With this update, you can now access and report on Local Service Ads data directly within the platform. As part of this enhancement, we've introduced several new LSA-specific dimensions to provide greater visibility and flexibility in your reporting.

We have introduced a new field "Agent Directions" for Datasets. This enhanced method of getting details to the agent about your dataset should be more scalable than our past method (just the dataset description field at the agent level).

Navigation Path: Data Cloud --> Datasets --> Select Dataset --> Agent Directions field in right hand panel --> Pencil Icon

Information added here should explain what this dataset is, any important information about the fields within the dataset and anything else that will always be applicable to this dataset no matter which Agent its assigned to. This description will basically 'follow' the dataset to any Agents it gets assigned to and will help the Agent understand when and how to use it during user convos.

At the Agent level, you'll see this description pull through, and there's also an "Additional Agent Directions" field where additional directions can be optionally inserted that may only be applicable for this agent.

Note that this is currently only available for the original ingested dataset as well as SQL Transform datasets, but is not yet available for Views (but will be coming soon).