Release Notes - Daton - January 2026
Release Notes - Daton - January 2026
🛠️Fixes
Amazon selling Partner - ListTransactions – Batch Timestamp Edge Case Fix
Â
What was the issue?
In the ListTransactions table, the batch end date was set to 2025-07-31T23:59:59.999999999, which excluded the final nanosecond of the day. Due to this edge case, a small number of order IDs fell just outside the batch window and were missed during processing.
What we fixed
We updated the batch end-date logic to use a computed “safe end date” that ensures continuous timestamp coverage while protecting against time zone and near–real-time data inconsistencies.
Why this matters
This prevents rare edge-case data gaps at nanosecond precision and ensures complete transaction coverage in future runs.
Do you need to do anything?
No immediate action is required. However, if you notice any data discrepancies, please contact support, and we will promptly backfill the affected data.
Amazon selling Partner - CatalogItems – ASIN Extraction Fix, Japan Marketplace
What was the issue?
For the Japan marketplace, the column names in the source reports differ from those in other regions. Because the extraction logic was not aligned with the Japanese column names, the data was processed with 0 records, resulting in missing CatalogItems data.
What we fixed
We updated the column-mapping logic to reference the Japan-specific column names, ensuring proper ASIN extraction and data processing.
Why this matters
This ensures CatalogItems data for the Japan marketplace is correctly detected and loaded, preventing empty loads and downstream reporting gaps.
Do you need to do anything?
No action is required. If you notice any data discrepancies, please reach out, and we will review them promptly.
Amazon selling Partner - Invalid/Corrupted Data in FBAManageInventoryHealthReport
What was the issue?
Amazon generated a malformed report file with shifted columns, resulting in corrupted data (e.g., snapshot_date appearing as 0001-01-01 and SKU column containing date values).
What we fixed
We cleared the pipeline state and requested a fresh report snapshot from Amazon. The new report returned correct data.
Why this matters
The issue was caused by corrupted data generated on Amazon’s side, not by Daton processing. Amazon has since resolved the issue, and current API responses are functioning correctly.
Do you need to do anything?
No action is required. Please let us know if you notice any further discrepancies.
Amazon Sponsored Brands - UnifiedPlacementCampaignReportÂ
What was the issue
The placement column was not populated for data processed between 16 December 2025 and 6 January 2026, including attribution historical loads.
What we fixed
During a migration to the V3 reporting APIs, the placement field mapping was not carried over correctly. We have corrected the mapping and restored the previous API version to ensure data consistency while the V3 transition is revalidated.
Why this Matters
Due to missing placement values during this period, Records with blank placement values may have been treated as distinct rows. This could have led to inflated Sponsored Brands metrics in downstream dashboards and reports.
Do you need to do anything?
To avoid metric inflation, we recommend: Updating your queries to filter out records where the placement column is empty. This will ensure duplicate rows are not included in your reporting.
🚀Enhancements
Neon-Pixel Connector Upgrade - Now Using V3 API Endpoints
What we improved
We’ve upgraded to Neon Pixel’s latest API, which includes newly introduced metrics such as CTV_Blended, TV_Network, Display_Publisher, and Creative. The update also supports user-choice attribution for up to 90 days, helping ensure more accurate and consistent data.
How it works
Neon Pixel unifies campaign data across CTV and digital channels to deliver a complete performance view. The CTV_Blended endpoint aggregates impressions, visits, conversions, spend, ROAS, and ratios at a daily level for any date range. Performance can be segmented by TV_Network to compare results across television channels, by Display_Publisher to evaluate digital sources, and by Creative to measure the impact of individual ad assets. Together, these dimensions let advertisers filter, analyze, and optimize campaigns in one queryable report—supporting smarter budget allocation, creative optimization, and media strategy through consistent, data-driven insights
Why this matters
Having all CTV and digital performance in one place removes guesswork from campaign decisions. Instead of looking at disconnected reports, you can clearly see which networks, publishers, and creatives are driving real business results—not just impressions. This helps you shift budget to what actually works, improve ROAS, reduce wasted spend, and scale high-performing campaigns faster. With consistent, day-level metrics, teams can spot trends early, optimize in near real time, and prove the true impact of CTV on conversions and revenue.
Do you need to do anything?
On your end, you need to set up a new integration or modify the existing one by selecting new KPIs. ReadMoreÂ
Loop Subscription Connector Upgrade - Now Using V2 API Endpoints
What we improved
We’ve upgraded to LoopSubscription's latest API endpoint(V2), which includes newly introduced metrics such as Subscriptions, Orders, Billing_Attempts, Customers, Products & Activity Logs.Â
How it works
Loop Subscription centralizes recurring revenue and customer lifecycle data to give brands a complete view of their subscription business. It unifies subscription, customer, order, and product data into a single, queryable reporting layer, enabling teams to track growth, retention, and churn with clarity.
Loop’s reporting endpoints provide day-level metrics, including active subscriptions, new sign-ups, cancellations, pauses, renewals, revenue, churn rate, and lifetime value, across any selected date range.
Performance can be segmented by Plan to compare different subscription tiers, by Customer to analyze behavior and retention patterns, by Product to evaluate item-level performance, and by Status (active, paused, cancelled) to understand lifecycle movement.
Why this matters
Subscription businesses grow on retention, not just acquisition. Without a clear, unified view of subscriber behavior, revenue trends, and churn drivers, teams are forced to rely on fragmented data and assumptions.
Loop Subscription brings all recurring revenue signals into one place, making it easy to understand what’s driving growth and what’s putting it at risk. By tracking subscription health, customer lifecycle movements, and plan performance in a single reporting layer, teams can quickly spot churn risks, identify high-value customers, and optimize pricing and product strategies.
Do you need to do anything?
On your end, you need to set up a new integration or modify the existing one by selecting new KPIs. ReadMore
Zendesk Connector Upgrade - New Ticket Audit & Satisfaction Tables Added
What we improved
The Zendesk connector has been enhanced with three newly supported tables:
- Ticket Audit
- Ticket Metric Events
- Satisfaction Ratings
This upgrade is designed to provide organizations with deeper operational transparency across the entire ticket lifecycle. The newly added tables enable more granular SLA tracking, clearer performance measurement, and stronger alignment between service operations and customer satisfaction outcomes.
How it works
The Ticket Audit table captures every recorded change made to a ticket. This includes status transitions, assignee updates, group transfers, priority modifications, field-level changes, and tag updates. With this historical visibility, organizations can analyze how tickets evolve over time, understand workflow patterns, and perform detailed audit tracking when required.
The Ticket Metric Events table records time-based metric transitions, such as first-reply-time updates, resolution-time changes, SLA milestone events, and other performance-related changes. Rather than relying solely on final aggregated metrics, teams gain visibility into how performance indicators shift throughout the ticket lifecycle. This supports more accurate SLA analysis and trend monitoring.
The Satisfaction Ratings table stores structured customer feedback submitted after ticket resolution. This includes satisfaction scores, submission timestamps, and customer comments. By incorporating satisfaction data alongside operational metrics, organizations can directly assess the relationship between service performance and customer perception.
Why this matters
With enhanced lifecycle and event-level visibility to:
Monitor SLA compliance with greater precision
Identify response and resolution bottlenecks through event-level analysis
Evaluate agent and group performance using detailed metric transitions
Correlate customer satisfaction outcomes with operational efficiency
Strengthen reporting, governance, and audit readiness
This enhancement supports more advanced analytics, improved accountability, and data-driven service optimization initiatives.
Do you need to do anything?Â
To begin syncing the new tables, you will need to:
Update your existing Zendesk integration to select the newly added tables, or
Create a new integration including these tables; the tables will sync automatically
Mercado Libre - Seller Promotion API Upgrade
What changed
Mercado Libre updated its APIs for the seller promotion data endpoint. We updated our connector to align with the new API structure.
How it works
We upgraded the underlying integration logic to support the updated API. All existing Mercado Libre integrations were automatically updated.Â
There is no change in the downstream data flow.
Why this matters
This ensures continued, uninterrupted data flow for seller promotion data and keeps your integration aligned with Mercado Libre’s latest API standards.
Do you need to do anything?
No action is required. If you notice any discrepancies in seller promotion data, please contact our support team for assistance.
ShipStation Connector Migration
What we improved
We rebuilt the legacy ShipStation connector to align with the latest APIs and implemented incremental sync behavior where supported by the API.
How it works
The new connector uses incremental data fetching, ensuring that only new or updated records are processed after the initial load. This improves efficiency, reliability, and API compliance.
Why this matters
The older connector did not fully support incremental behavior, requiring rework. Migrating ensures better performance, reduced API load, and long-term maintainability.
Do you need to do anything?
If you are still using the legacy ShipStation connector, please migrate to the new connector by configuring a new integration.
✨New Features
Amazon Sponsored Brands, Google Ads & Facebook Ads
Intraday Window for Improved Data Freshness
What’s new
Daton now supports refreshing recent data more frequently across Amazon Sponsored Brands, Google Ads, and Facebook Ads.
How it works
When an Intraday Window is configured:
- Daton automatically refetches data every 2–3 hours.
- Refreshes apply to all days within the selected lookback window (up to the last 7 days), not just the current day.
Why this matters
This update:
- significantly reduces gaps between the ad console and your warehouse
- improves accuracy for reporting and decision-making
- captures late conversions or retroactive adjustments that a once-daily refresh might miss
Do you need to do anything?
If you want intraday refresh:
- Open the integration, create or edit the flow.
- Set Intraday = Yes.
- Select the preferred window.
If Intraday is already enabled, you can review or modify the window at any time.
Note: Intraday configuration from the Daton UI is currently not available for Google Ads and Facebook Ads. Please contact our Support team if you would like this enabled for your integration.
đź”” Important Update
Shopify Custom App Creation Process Updated
What changed
Shopify updated the process for creating custom apps. As a result, we have temporarily updated the Shopify connector setup flow.
How it works
You must now create a custom app directly in the Shopify Admin Dev Dashboard to generate client credentials, then complete the connector setup and share the credentials with our support team.
Follow these guides:
Why this matters
Shopify updated its app creation process, which changes how integrations authenticate. We updated our connector flow to ensure you can continue connecting your store without interruption.
We are actively building and launching our app on the Shopify App Store to simplify this setup process and eliminate the need for manual app creation.
Do you need to do anything?
If you are setting up a new integration in Daton, create a Shopify custom app and share the generated credentials with our support team.