✨New Features

CIRRO — New Connector for Order and Logistics Data

What's new — New Daton connector for CIRRO, a 3PL order-management and logistics platform.

How it works — Order, shipment, fulfillment, and inventory data is extracted from CIRRO's API and loaded daily into the warehouse, following the standard new-connector modelling pattern.

Why this matters — You can centralize CIRRO data alongside your other warehouse data for unified order and fulfillment analytics.

Do you need to do anything? — If you use CIRRO, create a new CIRRO integration in Daton and provide your CIRRO API credentials and account details.

Prescient AI — New Connector for Marketing Mix Modeling

What's new — New Daton connector for Prescient AI, a marketing mix modeling (MMM) platform.

How it works — Modeled attribution metrics (modeledMetrics) and platform-reported spend (reportedMetrics) are extracted from Prescient's GraphQL API with full pagination and incremental loading, landing daily in warehouse.

Why this matters — You can centralize MMM insights such as channel contribution, halo effects, and reported spend in your warehouse for cross-channel attribution analysis.

Do you need to do anything? — If you use Prescient AI, create a new Prescient AI integration in Daton and provide your Prescient API key (generated in your Prescient account under Settings → API; your account may need API access enabled by Prescient first).

Revcontent — New Connector for Native Advertising

What's new — Daton now supports  a native and content advertising platform. 

How it works — Campaign- and widget-level performance data (impressions, clicks, spend, CPC, conversions) is extracted and loaded daily, and modelled into the same cross-channel advertising view as your other channels.

Why this matters — You can include Revcontent in cross-channel advertising analysis and AdvertisingMaster reporting.

Do you need to do anything? — If you advertise on Revcontent, create a new Revcontent integration in Daton and provide your Revcontent API credentials from your Revcontent account.

Mediago — New Connector for Programmatic and Native Ads
 

What's new — New Daton connector for Mediago, a native and programmatic advertising platform. 

How it works — Campaign- and ad-level performance data (impressions, clicks, spend, CPC, CPA, conversions) is extracted and loaded daily, and modelled into your cross-channel advertising view.

Why this matters — You can track Mediago spend and performance alongside your other advertising channels in AdvertisingMaster.

Do you need to do anything? — If you advertise on Mediago, create a new Mediago integration in Daton and provide your Mediago API credentials.

Mintsoft — New Connector for 3PL Inventory Management

What's new — New Daton connector for Mintsoft, a 3PL inventory and warehouse management system. 

How it works — Daily SKU-level on-hand inventory data is extracted from Mintsoft and loaded into Warehouse.

Why this matters —You can centralize 3PL warehouse inventory alongside your other supply chain and operational data.

Do you need to do anything? — If you use Mintsoft, create a new Mintsoft integration in Daton and provide your Mintsoft API key.

Triple Whale — New Connector for Attribution and Analytics

What's new — New Daton connector for Triple Whale, providing access to pixel attribution and analytics data.. 

How it works — Order-level pixel data (pixel_orders_table), joined conversion metrics (pixel_joined_tvf), and Clicks & Views attribution are extracted from Triple Whale's warehouse export feature and loaded daily into the warehouse, with deduplication and a documented lookback window.

Why this matters —You can centralize Triple Whale attribution insights for cross-channel performance analysis and attribution modeling alongside your other data sources.

Do you need to do anything? — If you use Triple Whale, create a new Triple Whale integration in Daton and provide your Triple Whale API key.

🚀Enhancements
 

Amazon Selling Partner — B2B Traffic Metrics Now Available in Sales & Traffic by SKU 

What we improved — Added six B2B traffic fields to the Amazon Seller SalesAndTrafficReportBySKU table: sessionsB2B, pageViewsB2B, browserSessionsB2B, mobileAppSessionsB2B, browserPageViewsB2B, and mobileAppPageViewsB2B.

How it works — These fields were already being returned by Amazon's SP-API but were missing from the Daton table schema. The schema now includes them, so all new and existing integrations receive the data automatically.

Why this matters — B2B sessions and page views are now available alongside B2B sales metrics at the SKU level, giving you a complete picture of B2B engagement in your warehouse without manual exports from Seller Central.

Do you need to do anything? — Edit your Amazon Selling Partner Integration and add these fields. Contact our support team for any help.

ShipBob — Updated API Version

What we improved — Migrated the ShipBob connector from the deprecated v1.0 API to ShipBob's current API version, ahead of ShipBob's August 29 deprecation deadline.

How it works — The upgrade happens within your existing connector, with no new version to set up. Several tables gained fields (richer tracking detail on Orders, a fuller product catalog on Products, a true transaction ID on Transactions_By_InvoiceID). Two changes need attention: box_status on Receiving_Order_Boxes now returns a word (e.g. "Completed") instead of a number, and per-fulfillment-center/per-lot inventory detail is no longer provided by ShipBob and has been removed.

Why this matters — Your ShipBob data keeps flowing without interruption once the old API is retired, and several tables now carry more detail.

Do you need to do anything? — If you use ShipBob, review the box_status and inventory changes with your team, and contact our support team if you any questions.

AppLovin — New Audience, Bidding, and Revenue Fields

What we improved — Added six fields to the AppLovin connector: audience_strategy, bidding_and_billing_method, total_rev_0d, total_rev_7d, ad_rev_0d, and ad_rev_7d.

How it works — These surface which audience targeting and bidding/billing approach a campaign used, plus day-0 and day-7 revenue from both purchases and ads, so you can assess user quality and monetization shortly after acquisition.

Why this matters — You can segment performance by audience strategy and bidding method, and compare early revenue signals across campaigns to make faster budget decisions.

Do you need to do anything? — No action required for new integrations. For existing AppLovin integrations, edit the integration to add the new columns and reload the table (keep a backup of your existing data first).

LiveIntent — Campaign and Creative-Level Identifiers Now Available

What we improved — Enhanced the LiveIntent Advertiser table to include campaign- and creative-level identifiers that were previously always null: CampaignID, CreativeID, campaign names, and advertiser names.

How it works — These dimensions are now populated in the raw table, so downstream reporting can distinguish between campaigns and creatives within the same advertiser account rather than only reporting at account level.

Why this matters — You can now report on campaign and creative performance, enabling granular campaign ROI analysis and creative benchmarking that was blocked when only account-level metrics were available.

Do you need to do anything? — No action required. Edit existing integrations to include these fields in the raw table.

Outbrain — Campaign Metadata Now Available

What we improved — Added campaign-level metadata (campaign name, status, and budget) to the Outbrain connector, making it joinable to campaign performance data on campaign ID.

How it works — Campaign metadata is now extracted into the raw table alongside performance metrics, where previously only campaign IDs were available for mapping.

Why this matters — Reporting can now show Outbrain campaign name, status, and budget utilization instead of just IDs, improving campaign-level visibility and ROI analysis.

Do you need to do anything? — No action required.

Outbrain — Historical Daily Campaign Data Now Complete

What we improved — Backfilled missing historical daily campaign performance data for Outbrain, which previously only started July 21, 2026, and undercounted spend/impressions/clicks by up to ~22% on some overlapping days versus the Outbrain UI.

How it works — Daily campaign-level metrics are now complete across the full date range and reconcile to the UI, with an explicit report date in the payload.

Why this matters — You can perform accurate month-over-month and period-over-period analysis with complete, UI-matching Outbrain campaign data.

Do you need to do anything? — No action required.

Fairing — Survey Response Data Now Fully Ingested

What we improved — Fixed an issue where Fairing survey responses — including free-text "Other" responses — were only partially ingested and did not match the Fairing UI export.

How it works — The connector now captures all response types at the raw layer without filtering or truncation.

Why this matters — Your Fairing survey data is now complete and accurate, reflecting every response captured in the Fairing UI for reliable post-purchase survey analysis.

Do you need to do anything? — No action required. Historical data has been reloaded.

NetSuite — Fixed Pagination Error for API Integrations

What we improved — Corrected a pagination bug in the NetSuite connector where an out-of-bounds offset parameter caused syncs to fail with a 404 "offset is out of bounds" error.

How it works — The connector now handles offset bounds correctly, either resetting or stopping pagination when no more records are available rather than requesting an invalid offset.

Why this matters — NetSuite API integrations now sync reliably without pagination errors that previously blocked customer data from loading.

Do you need to do anything? — No action required. Affected integrations will resume syncing.

Walmart — Upgraded to OAuth 2.0 Authentication

What we improved — Migrated the Walmart connector from Walmart's legacy delegated-access authentication to OAuth 2.0, ahead of Walmart's deprecation of the old method.

How it works — The connector now uses industry-standard OAuth 2.0 for secure authorization, and existing integrations have been upgraded transparently.

Why this matters — Your Walmart data flow is future-proofed and compliant with Walmart's new security standards (GDPR, SOC2, CCPA), avoiding an interruption when the legacy method is retired.

Do you need to do anything? — No action required for most users. If your integration requires re-authentication, you'll be notified.

Pinterest — Ad Analytics API Upgraded to V5

What we improved — Upgraded the Pinterest connector to use the latest Ad Analytics API version (V5), and resolved an edit-flow issue that prevented some integrations from working after authentication.

How it works — The connector now pulls data using the V5 endpoints and data structure.

Why this matters — Your Pinterest data stays current and benefits from the latest API features and performance improvements.

Do you need to do anything? — No action required.

X Ads (Twitter Ads) — Enhanced to Support Ad-Level Granularity

What we improved — Extended the X Ads connector to support ad-level, line-item-level, and device/geo-level performance data, where previously only campaign-level stats were available.

How it works — New tables provide daily performance metrics at the ad × line item × date grain, with optional device and geo dimensions, plus supporting campaign, line item, promoted tweet, and targeting detail.

Why this matters — You can analyze ad and line-item performance individually, enabling creative-level optimization and benchmarking for channel onboarding and ad performance reporting.

Do you need to do anything? — No action required for new integrations. Existing integrations can opt in to add the new tables.

Taboola — New Ad-Level Performance Report Table

What we improved — Added an ad-level performance report table to the Taboola connector, complementing the existing campaign-level metrics and ad metadata that previously left ad ID and ad name unpopulated in reporting.

How it works — A new raw table contains daily ad performance (spend, clicks, impressions, conversions) at the ad × day grain, sourced from Taboola's Top Campaign Content report.

Why this matters — You can now see which individual ads perform best and optimize creative spend at the ad level, not just the campaign level.

Do you need to do anything? — No action required for new integrations. Existing integrations can add this table.

Google Ads — Upgraded to API Version V22

What we improved — Upgraded the Google Ads connector from API v21 to v22, ahead of the v21 deprecation cycle.

How it works — The upgrade is automatic for all integrations. Deprecated columns have been removed per the v22 specification, and new v22 fields and nodes are now available for integration.

Why this matters — Your Google Ads data keeps flowing reliably with the latest API features, and you gain access to new reporting fields introduced in v22.

Do you need to do anything? — No action required. The upgrade has been applied to all existing and new Google Ads integrations, and editing existing integrations continues to work normally.

ZenShows — Assignment Attributes and Enhanced API Support
 

What we improved — Extended the ZenShows connector with two new API endpoints: getChangedAssignmentAttributesShowIds for incremental tracking and getAssignmentAttributes for assignment records including travel costs (hotel and flight).

How it works — New tables track which shows had assignment attribute changes on a given date and retrieve the full assignment records in batches, landing them in your warehouse alongside the existing ZenShows event, RMA, and sales data.

Why this matters — You can build cost allocation and P&L reporting that includes assignment-level travel expenses, enabling more granular profitability analysis by show and assignment type.

Do you need to do anything? — No action required for new integrations. Existing ZenShows integrations can opt in to add the new tables.

Amazon DSP — Reliability Improved
 

What we improved — Fixed a process that caused the Amazon DSP Reports to table to fail with a syntax error during the report-status polling phase.

How it works — The root cause was   in the report-status polling logic that produced invalid script. We corrected the script and rolled the fix out across all active Amazon DSP integrations.

Why this matters — Amazon DSP Reports data now syncs cleanly from report creation through download without failing, benefiting every customer on this connector.

Do you need to do anything? — No action required.

🛠️Fixes

Amazon Seller Partner — SQS Notification Worker Reliability Improvements

What was the issue — The background worker that listens for Amazon SP-API report completion notifications used blocking thread operations, which could consume thread-pool resources and compete with active data sync jobs, causing delays or instability in Amazon Seller Partner pipelines.

What we fixed — Replaced blocking thread calls with non-blocking coroutines, added configurable polling intervals and per-run message limits to prevent resource spikes, enabled batch processing for SQS deletions and MongoDB updates, and added graceful shutdown handling.

Why this matters — Amazon Seller Partner syncs run more reliably with fewer resource conflicts, and report-completion notifications are processed more efficiently, reducing latency in data delivery for all Amazon Seller Partner customers.

Do you need to do anything? — No action required. The improvement has been deployed automatically to all Amazon Seller Partner integrations.

Amazon FBA Promotions Report — Fixed Integer Overflow for Large Promotion IDs

What was the issue — Some Amazon promotion IDs are larger than a standard integer field can hold. When that happened, the value was silently stored as 0 in the item_promotion_id field of the FBA Promotions Report instead of the correct ID.

What we fixed — Updated the field to a numeric type that supports these larger values, corrected the underlying processing logic, and reloaded historical data for impacted integrations to repopulate the correct promotion IDs.

Why this matters — Your FBA Promotions Report now reflects accurate promotion IDs, including previously affected large values, improving the reliability of promotions-based reporting.

Do you need to do anything? — No action required. If your account was impacted, contact our team and take backup before reloading your data.

Amazon Selling Partner — Catalog Items Now Loading Correctly

What was the issue — The Amazon Selling Partner CatalogItems table was showing zero records from July 24, 2026 onward, despite catalog data being available in both the Amazon API response and the Seller UI.

What we fixed — The connector now persists catalog item data correctly to the CatalogItems table for all active listings.

Why this matters — You again have access to complete Amazon catalog data (ASIN details, product information) that downstream reporting depends on.

Do you need to do anything? — No action required. Historical catalog data has been reloaded.

Amazon Settlement Reports — Duplicate Load Issue Fixed

What was the issue — Amazon Settlement Reports were being loaded multiple times under different batch runtimes, creating duplicate records for the same settlement IDs where only metadata columns differed.

What we fixed — The connector now deduplicates settlement records at the source and prevents re-ingestion of already-processed reports.

Why this matters — Your settlement data is now accurate and clean, without inflated row counts that could affect reconciliation and billing-row-count reviews.

Do you need to do anything? — No action required.

Amazon Replenishment — New Daily-Level Metrics Now Available

What was the issue — The Amazon Replenishment SNS tables only supported coarser aggregation, even though Amazon's SP-API added DAY as a supported aggregation frequency (with additional metrics) for the listOfferMetrics and getSellingPartnerMetrics operations.

What we fixed — Updated the connector to extract daily-level metrics, so replenishment data is now available at the daily grain in addition to the existing aggregations.

Why this matters — You can track replenishment and inventory metrics day by day for more granular operational insight.

Do you need to do anything? — No action required for new integrations. Existing integrations can be reloaded to include daily data.