Release Notes - Daton - February 2026
Release Notes - Daton - February 2026
🛠️Fixes
Amazon Selling Partner - PricingForASIN Fix Released
What Was the Issue?
In the PricingForASIN table under the Amazon Selling Partner connector, the
offers field (inside Product) was being replicated in an invalid JSON string format.- The API returns
Offersas a RECORD type. - However, it was stored as a STRING data type.
- This caused formatting inconsistencies and limited the ability to properly query nested offer data.
What We Fixed
- Corrected the data format of the
offersfield to match the API structure (RECORD type). - Resolved the invalid JSON formatting issue.
- Updated the schema in the connector to reflect the correct datatype.
Why This Matters
- Enables proper querying of nested offer-level data.
- Eliminates JSON parsing errors.
- Ensures schema consistency between API and warehouse.
- Improves downstream transformations and reporting accuracy.
Do You Need to Do Anything?
For Existing Integrations
Yes. The PricingForASIN table must be reloaded.
⚠️ Please take a backup before reloading, as the warehouse schema will change to reflect the corrected RECORD datatype.
For New Integrations
No action is required.
The table has already been added with the correct data format, so this issue will not occur moving forward.
Improved Handling of Shopify Server Errors (409)
What was the issue?
Some Shopify integrations experienced temporary sync delays when Shopify returned a 409 server error. This affected the freshness of sources in certain cases.
What we fixed
We updated our connector logic to automatically retry additional Shopify 409 server errors.
The system now retries after one minute, with a maximum threshold of 20 attempts to prevent retry loops.
Why this matters
This improves data freshness and reduces temporary sync interruptions caused by Shopify server-side issues.
Do you need to do anything?
No action is required.
All existing integrations have already been updated.
Resolved Null Byte Ingestion Issue in Postgres Destinations
What was the issue?
Postgres databases configured with UTF-8 encoding do not accept null bytes, which caused ingestion failures in certain cases.
What we fixed
We updated our data formatting logic to automatically filter out null byte characters before loading data into Postgres destinations.
This ensures compatibility across both GC Postgres and RDS Postgres environments.
Why this matters
Data now loads reliably without interruption due to encoding conflicts.
This prevents ingestion failures, improves pipeline stability, and ensures consistent data availability in your warehouse.
Do you need to do anything?
No action is required.
The fix has been applied to all affected integrations.
Monday Board - Incomplete Boards Data
What was the issue?
Next page cursor in the API response was not consistently placed across all board IDs, causing pagination to fail for some boards and resulting in incomplete data.
What we fixed
We enhanced our pagination logic to dynamically detect and retrieve the valid next-page cursor regardless of its position within the group of objects. This ensures that all pages are fetched correctly for every board ID.
Why this matters
This fix ensures complete and reliable data extraction for all Monday boards. You can now trust that all records associated with your boards are fully synced, with no data missing due to pagination inconsistencies.
Do you need to do anything?
No action is required.
The fix has been applied to all affected integrations.
🚀Enhancements
adimages Table Added to Facebook Ads V2 Connector
What We Improved
We’ve added new
adimages table under the Facebook Ads V2 connector to provide direct access to ad creative image data.How It Works
The
adimages table pulls image-level metadata directly from Meta (Facebook) Ads, including image hashes, URLs, and related creative references.This allows you to:
- Map ads to their associated images
- Analyze creative performance at the image level
- Maintain better traceability between ad creatives and campaigns
Why This Matters
- Enables deeper creative performance analysis
- Helps identify top-performing images across campaigns
- Improves reporting accuracy for creative-level insights
- Reduces dependency on manual creative exports
Do You Need to Do Anything?
If you would like to access this data, please add the
adimages Table to your existing Facebook Ads V2 integrationAmazon Selling Partner - FBAManageInventoryHealthReport Column Update
What We Improved
We’ve added new columns to the FBAManageInventoryHealthReport table in the Amazon Selling Partner connector to provide deeper visibility into:
- Inventory aging buckets
- Aged Inventory Surcharge (AIS) calculations
- Low Inventory Level fee indicators
- Historical Days of Supply metrics
- Reserved and FBA inventory breakdowns
- Supplier-level information
New Columns Added
inv_age_366_to_455_daysinv_age_456_plus_daysquantity_to_be_charged_ais_366_455_daysestimated_ais_366_455_daysquantity_to_be_charged_ais_456_plus_daysestimated_ais_456_plus_daysLast_updated_date_for_Historical_Days_of_SupplyExempted_from_Low_Inventory_Level_fee_Low_Inventory_Level_fee_applied_in_current_week_Short_term_historical_days_of_supplyLong_term_historical_days_of_supplyTotal_Days_of_Supply__including_units_from_open_shipments_Inventory_age_snapshot_dateInventory_Supply_at_FBAReserved_FC_TransferReserved_FC_ProcessingReserved_Customer_OrdersupplierHow It Works
These fields are sourced directly from the Amazon Selling Partner report and are now mapped to the warehouse schema.
- The integration will ingest and sync these columns as part of the regular report pull.
- Existing integrations will receive the additional columns in the table schema.
- New integrations will have these columns available automatically at the connector level.
Why This Matters
- Improved tracking of Aged Inventory Surcharge (AIS) exposure
- Better visibility into Low Inventory Level fees
- More accurate Days of Supply forecasting
- Enhanced reporting on reserved and in-transit inventory
- Stronger inventory planning and cost control insights
This update enables more granular inventory health analysis and better financial forecasting.
Do You Need to Do Anything?
For Existing Integrations
No action is required. The new columns will automatically be added to your existing table schema.
For New Integrations
No action is required. The columns are already included at the connector level and will be added automatically during integration setup.
Google Ads API Version Upgrade to v20
What we improved
We’ve upgraded our Google Ads connector to API version v20. This update ensures your integration remains fully compatible with Google’s latest architecture and provides access to enhanced reporting for AI-driven campaigns.
How it works
This upgrade completes the full removal of legacy feed-related resources (such as
FeedService and FeedItem), which have been entirely replaced by the Asset-based framework. Key technical shifts include:- Enhanced Reporting: Introduction of the
campaign_search_term_viewfor Performance Max campaigns, providing deeper visibility into search queries. - Network Segmentation: Demand Gen reporting now provides granular data by splitting the former "Google Owned Networks" into specific categories:
YOUTUBE,GMAIL,DISCOVER, andMAPS. - Compliance & Control: Added support for the
contains_eu_political_advertisingfield and new services to manage automatically generated assets.
Why this matters
You now have more precise attribution for Demand Gen campaigns and better transparency into how Performance Max ads are serving. By aligning with v20, your integrations are optimized for Google’s modern, asset-centric ad delivery system.
What you need to do
- No re-authorization is required.
- Update Custom Queries: If you have custom SQL or GAQL queries, ensure all references to
feed_itemorfeed_mappingare migrated toassetorcampaign_asset. - PMax Logic Check: Ensure your reporting logic for Performance Max uses the
asset_groupresource. - Adjust Network Filters: Update your dashboards to include the new segmented network types for Demand Gen to maintain accurate aggregate totals.
For more details, refer to the official Google Ads v20 release notes.
Facebook Ads API Version Upgrade to v23
What we improved
We’ve upgraded our Facebook Ads connector to API version v23. This ensures your data pipelines are aligned with Meta’s latest privacy standards and provides enhanced support for AI-driven campaign types, including Advantage+ Shopping and Advantage+ Creative sets.
How it works
This upgrade transitions our connector from v22 to v23, introducing more granular insights into how Meta’s AI optimizations are performing across your accounts:
- Advanced Reels Metrics: v23 introduces new breakdowns for Reels Ads, including specific metrics for "Overlay Ads" and "Post-Loop Ads"
- Advantage+ Creative Breakdowns: We’ve added granular reporting for Advantage+ Creative.
Why this matters
Meta’s API ecosystem is moving rapidly toward automated, AI-led advertising. By upgrading to v23, you ensure that your reporting is actually capturing the new data points generated by Meta’s AI optimizations.
What you need to do
- Automated Transition: No action is required. Your integrations will automatically begin using the v23 endpoint with no need for re-authorization.
- Documentation: For a deep dive into the technical changes, you can explore the Meta for Developers v23 Changelog.
Amazon Sponsored Brands: AudienceReport Addition
What we improved
We’ve added a new table: Audience Report to the Amazon Sponsored Brands connector.
This table provides audience-level performance insights, helping you better understand who your ads are reaching and how different audience segments are performing. To learn more about Audience report and the available data, refer to the official documentation here.
How it works
Audience Report table fetches data directly from Amazon Advertising Reporting API (v3) and captures audience-segment performance metrics such as:
- Audience segment details
- Impressions
- Clicks
- Spend
- Sales and other performance metrics
Why this matters
This enhancement enables you to:
- Analyze performance by audience segments
- Identify high-performing and underperforming audience groups
- Optimize targeting strategies
It gives marketing and growth teams better visibility into audience effectiveness, leading to more data-driven campaign decisions.
What you need to do
Edit your Sponsored Brands integration and add Audience report to start syncing this data.
Facebook Pages: Published Post Addition
What we improved
 We’ve added a new table: Published Posts, allowing you to extract all published posts from your connected Facebook Pages. To learn more about Published Post and the available data, refer to the official documentation here.
How it works
Published Posts table fetches data directly from the Facebook Graph API’s published posts endpoint and retrieves detailed post-level information, including post metadata and associated attributes.
Why this matters
You now get better visibility into your organic content performance and publishing activity.
This enables:
- Centralized reporting across paid and organic efforts
- Post-level analysis in your data warehouse
- Improved content performance tracking
What you need to do
Edit your Facebook Pages integration and add Published Posts table to start syncing this data.
Added Campaign Type to Bing Ads Campaign Performance Reports
What we improved
We added the Campaign Type field to the following reports:
- campaign_performance_report
- campaign_performance_report_hourly
How it works
The reports now include the campaignType field returned by Bing Ads. This field identifies the campaign category, such as Search or Shopping.
Why this matters
You can now clearly distinguish between different campaign types in your reporting. This improves segmentation, performance analysis, and campaign-level insights.
Do you need to do anything?
Yes.
Please edit your integration to include the new campaignType column if needed.
Enhanced Visibility in Shopify Order Returns Data
What we improved
We added the following fields to the order_returns table:
- createdAt
- requestApprovedAt
- closedAt
- fulfillmentLineItem (nested RECORD within returnLineItems)
How it works
The order_returns table now captures detailed return lifecycle information directly from Shopify’s GraphQL endpoint.
You can now view:
- All returns associated with an order
- Line-item level return details
- When the customer initiated the return
- When the return was approved
- When the return was closed (refund processed)
This enhancement provides visibility into intermediate return stages.
Why this matters
You now gain full transparency into the return lifecycle at the line-item level.
This enables you to:
- Track return timelines more accurately
- Monitor approval and processing delays
- Analyze operational efficiency for returns
- Build more granular return and cancellation reporting
- Distinguish between initiated, approved, and closed returns
This significantly improves reporting beyond what was previously available in refund tables.
Do you need to do anything?
Yes.
If you use the order_returns table in downstream models or dashboards, update your integration to include the newly added fields.
Pipeline Performance and Scheduler Reliability Improvements
What we improved
We strengthened communication between our microservices to ensure scheduling requests are consistently processed.
We also improved the file handling mechanism during source retrieval to make jobs faster and more reliable.
How it works
The scheduler now tracks and processes job triggers more reliably across services.
Additionally, source data retrieval uses a more efficient file handling approach to reduce delays and improve execution stability.
Why this matters
You benefit from:
- More reliable scheduled runs
- Faster data retrieval
- Improved pipeline stability
Over the past three months, missed schedules have remained below 1%, reflecting the improved reliability of our scheduling system.
Do you need to do anything?
No action is required.
These improvements are already live across all pipelines.
Brightpearl: Attribution Window Enhancement
What we improved
We’ve introduced a 1-hour attribution (lookback) window in the Brightpearl connector to improve data consistency and ensure no records are missed during ingestion.
How it works
The connector now applies a 1-hour lookback window while fetching records from Brightpearl. During each sync, the system rechecks records from the previous hour to account for minor delays or minute-level timestamp differences.
This allows the connector to:
- Capture records that may have been updated slightly later than expected
- Handle small timestamp differences between systems
- Ensure more reliable incremental data syncing
Why This Matters
- Reduces the risk of missing recently updated records
- Improves data accuracy and completeness
- Provides more stable and reliable data synchronization
- Helps maintain consistent reporting
Do You Need to Do Anything?
- Existing Integrations: Please update your current Brightpearl integration settings to enable the attribution window and need to perform a rollback for the recent timeframe to ensure any previously missed records are captured.
- New Integrations: The 1-hour attribution window will be automatically applied during integration setup, so no additional action is required.
Typeform: Added FormDetails Table & Changed Responses to Incremental from Full Load
What we improved
We have introduced the FormDetails table, which provides a detailed response for each form ID, including
id, type, created_at, and last_updated_at.Additionally, the Responses table has been changed from a full load to an incremental load to reduce data consumption. It will now provide only incremental data going forward.
How it works
You need to add this new table to your integration. Once added, it will start delivering data with a more detailed response.
Regarding the Responses, please set up a new integration so that the data can be fetched incrementally.
Why This Matters
(a) The FormDetails table provides detailed responses, including complete answers. Without this information, UAT data validation would be difficult. It also contains question metadata (such as text and type), which is essential and useful for accurate data validation.
(b) Using Responses for incremental loads has reduced data consumption.
Do You Need to Do Anything?
Please setup new integration by adding these new tables.
For More Details please go through this doc.
AppLovin Connector Update: New Metrics Added
What we improved
We have added new metrics such as chka_usd_2d, cost_per_chka_0d, roas_0d, device_type, sales_x, and cpp_x to give you deeper insights. These metrics provide details on Revenue (USD) generated from purchases within 2 days, Cost per Purchase (0-day), Return on Ad Spend (0-day), device type breakdown, sales during a specific time period, and cost per purchase within a defined time span.
How it works
You’ll need to add these metrics by editing the integration and selecting them from the Column Selection section in the UI.
If you prefer, you can also create a new integration and configure it with the required metrics.
Why This Matters
These new metrics matter because they provide faster and more precise performance insights. Metrics like chka_usd_2d and roas_0d help you evaluate revenue and ROAS early, enabling quicker optimization decisions. cost_per_chka_0d and cpp_x improve cost efficiency tracking within specific time windows. device_type allows performance analysis by device, helping optimize targeting and creatives. sales_x supports time-based revenue analysis and better attribution understanding. Overall, these metrics help reduce wasted ad spend, improve budget allocation, and drive smarter, data-driven growth decisions.
Do You Need to Do Anything?
No action is required from your end. For more information, please refer to the this document.
Zendesk Chat Connector Upgraded to V2
What we improved
We improved by introducing upgraded version API endpoints of Zendesk chat.
How it works
Set Up a New Integration and Add these Tables
Why This Matters
Enhanced API Endpoints for Detailed Agent Activity and Ticket Resolution Insights
Do You Need to Do Anything?
You need to set up a new integration using the Zendesk Chat access token. For more details, please refer to the documentation.
✨New Features
X Ads Connector Launch
What’s new
The X Ads Connector is now available in Daton, enabling automated extraction of X Ads campaign data directly into your data warehouse for seamless reporting and analytics.
How it works
The connector uses X Ads APIs to fetch campaign, ad group, creative, targeting, and performance data — including impressions, clicks, spend, and conversions — and securely loads it into your Daton warehouse, ready for dashboards and custom analysis.
Why this matters
You can now access up-to-date advertising insights without manual exports, ensuring accurate, near real-time visibility into campaign performance for faster, data-driven optimization and better ROI tracking.
Do you need to do anything?
Log in to Daton and connect the X Ads connector using your API credentials to start syncing data — no additional setup required.
EverFlow Connector Launch
What’s new
The EverFlow Connector is now available in Daton, enabling automated extraction of Network EntityReport data directly into your data warehouse for seamless reporting and analytics.
How it works
The connector leverages Network Entity APIs to retrieve metrics such as total_click, unique_clicks, ctv, cv, cpc, and cpm—covering clicks per user session, cost per unit, and monthly cost. It then securely syncs this data to your Daton warehouse, making it readily available for dashboards and custom analysis.
Why this matters
You can now access up-to-date marketing data without manual exports, ensuring accurate, near real-time visibility into clicks, cpc & cpm data.
Do you need to do anything?
Log in to Daton and connect the EverFlow connector using your API credentials to start syncing data — no additional setup required. For More Details please go through this document.
Levanta Connector Launch
What’s new
The Levanta Connector is now available in Daton, enabling automated extraction of Creator Reports & Seller Reports data directly into your data warehouse for seamless reporting and analytics.
How it works
The connector uses the creator and seller APIs to pull key metrics such as clicks, conversions, and commissions. This helps track how many customers ultimately purchase the product and how much commission the seller earns through Amazon. It then securely syncs this data to your Daton warehouse, making it easily accessible for dashboards, reporting, and custom analysis.
Why this matters
You can now access up-to-date affiliate marketing data without manual exports, ensuring accurate, near real-time visibility into clicks, conversion & commisio data.
Do you need to do anything?
Log in to Daton and connect the Levanta connector using your API credentials to start syncing data — no additional setup required. For More Details please go through this document.