✨New Features

Checkout Champ — New Connector

What's new — Daton now supports a new Checkout Champ connector that enables automated ingestion of orders, customers, transactions, and purchase data from Checkout Champ directly into your data warehouse.  Learn more about Checkout Champ.

How it works — The connector authenticates via Basic Auth with your Checkout Champ API credentials and retrieves data from four endpoints: Orders, Purchases, Transactions, and Customers. Data loads incrementally into BigQuery using date-range filters, with pagination handled automatically.

Why this matters — Teams using Checkout Champ as their CRM or order management system can now automate data ingestion for sales, subscription, and revenue analytics — eliminating manual exports and enabling cross-channel reporting alongside other data sources.

Do you need to do anything? — If you use Checkout Champ, create a new integration in Daton and provide your API username and password (created under Admin > Users in CheckoutChamp).

Reddit Ads — New Connector

What's new — Daton now supports a new Reddit Ads connector, enabling automated ingestion of campaign performance data from Reddit into your data warehouse. Learn more about Reddit Ads.

How it works — The connector authenticates via OAuth 2.0 and retrieves campaigns, ad groups, ads, creatives, and performance report data (impressions, clicks, spend, conversions, CTR, CPC) from Reddit's Ads API. Data loads incrementally at the frequency you configure, with full support for breakdown dimensions such as campaign, country, region, and gender.

Why this matters — Marketing teams can now include Reddit Ads performance data in cross-channel reporting alongside other ad platforms, enabling a unified view of advertising spend and ROI without manual data exports from Reddit's UI.

Do you need to do anything? — If you advertise on Reddit, create a new Reddit Ads integration in Daton. You'll need your Reddit Ads OAuth credentials (Client ID + Client Secret) from an app registered at reddit.com/prefs/apps, along with your ad account ID.

Newsbreak — New Connector

What's new — Daton now supports a new Newsbreak connector, enabling automated ingestion of ad-level and campaign-level performance data from Newsbreak into your data warehouse. Learn more about Newsbreak. 

How it works — The connector authenticates with a static Access Token generated from Newsbreak Ad Manager and retrieves ad listings and custom performance reports — impressions, clicks, spend, CPC, CPA, and conversions — broken out by date, campaign, and ad. Data loads daily into BigQuery.

Why this matters — Teams advertising on Newsbreak can now include its performance data in cross-channel reporting alongside other ad platforms, without manual exports.

Do you need to do anything? — If you advertise on Newsbreak, create a new Newsbreak integration in Daton. You'll need an Access Token, which you can self-generate from Newsbreak Ad Manager under Resources → API Access Tokens.

Retail Next — New Connector
 

What's new — Daton now supports a new Retail Next connector that enables real-time access to your retail operations data, including store inventory, hourly traffic, and conversion metrics. Learn more about Retail Next. 

How it works — The connector integrates with your Retail Next account to retrieve stores data, hourly traffic analytics, and conversion metrics, making retail performance data available directly in your warehouse for analysis and reporting.

Why this matters — Retail operations and analytics teams can now centralize retail performance metrics alongside other business data, enabling unified reporting on store-level performance, traffic patterns, and conversion trends across locations.

Do you need to do anything? — If you use Retail Next for retail operations management, create a new Retail Next integration from Daton. Provide your Retail Next API credentials and account details.

Alerts — Data Not Available Notification

What's new — A new alert that notifies you when a scheduled incremental sync completes successfully but brings in zero new records, so you can catch a stalled or empty upstream data feed early instead of finding out from a stale dashboard. Learn more about Alerts.

How it works — The alert is enabled on a per-table basis. It only fires when the sync succeeds, ran as a regular incremental load, and returned no new rows — it won't trigger on failed syncs or in cases where zero rows is expected.

Why this matters — Previously, you'd have to manually check for a stalled or empty data feed. Now you get proactive visibility when expected data doesn't arrive, so you can react faster.

Do you need to do anything? — This is currently enabled via backend configuration only (no self-serve toggle yet). If you'd like the No Data Alert turned on for specific tables, contact our support team.

🚀Enhancements
 

Amazon Selling Partner — FBA Reserved Inventory Report 

What we improved — Added support for the new reserved_staging column in the Amazon FBA Reserved Inventory Report, reflecting Amazon's API schema update.

How it works — The connector now retrieves the reserved_staging field alongside other reserved inventory metrics, providing complete visibility into inventory reserved for staging operations.

Why this matters — Your FBA inventory data is now complete and aligned with Amazon's current reporting structure, preventing data gaps and ensuring accurate reserved inventory tracking.

Do you need to do anything? — No action required. The new field is automatically for all Amazon Selling Partner integrations.

Taboola — Ad-Level Creatives Endpoint Available

What we improved — Launched the Ads table for Taboola connector, exposing the ad-level creatives endpoint which provides visibility into individual campaign items (ads) across your Taboola network.

How it works — The connector now retrieves all campaign items (thumbnails, headlines, destination URLs, status, and approval state) from Taboola's API, making creative-level data available in your warehouse without manual exports.

Why this matters — You can now automate creative audits, monitor performance at the item level, detect creative fatigue, and build compliance checks programmatically across all your Taboola campaigns at scale.

Do you need to do anything? — The Ads table is available for new and existing Taboola integrations. Select it in your connector configuration to start receiving creative-level data.

TikTok Ads — Multiple OAuth Apps for Improved Reliability

What we improved — TikTok Ads enforces API rate limits at the app level, and having all integrations share a single OAuth app was causing rate-limit errors and delayed data delivery. We've introduced support for multiple OAuth apps for TikTok Ads.

How it works — When an integration is created, it's deterministically assigned to one of several available OAuth apps based on the integration name, spreading API requests across apps instead of funneling them through one. The assignment stays consistent unless you re-authenticate.

Why this matters — Distributing requests across multiple apps reduces the likelihood of hitting TikTok's app-level rate limits, meaning fewer job failures and more reliable, timely data delivery for all TikTok Ads customers.

Do you need to do anything? — No action required. Existing integrations pick up the change automatically after your next re-authentication.

Postscript — Cursor Pagination and Clearer Error Messages

What we improved — Upgraded the Postscript connector to use cursor-based pagination and replaced raw API error codes with clear, source-provided error messages.

How it works — Cursor pagination lets the connector move past Postscript's 1,000-page API limit and reliably sync large datasets without interruption. When the source returns an error, you now see the actual message from Postscript instead of an ambiguous code.

Why this matters — High-volume Postscript syncs complete without hitting page limits, and when something needs your attention (such as an account or plan setting on your Postscript side), the message tells you exactly what to do — no need to contact support to decode it.

Do you need to do anything? — No action required. The pagination upgrade has been applied to all existing Postscript integrations.

EasyEcom — Updated to Latest Authentication and v2.1 APIs

What we improved — Migrated the EasyEcom (EASYECOM_V2) connector to EasyEcom's current authentication flow and v2.1 API endpoints, resolving authentication failures caused by EasyEcom deprecating its old authentication endpoint.

How it works — The connector now authenticates using an x-api-key and location key as required by EasyEcom's latest API, and retrieves data through the updated v2.1 endpoints.

Why this matters — EasyEcom integrations that were failing with authentication errors now sync reliably on the supported API, keeping your order and inventory data flowing.

Do you need to do anything? — To move to the new authentication flow, edit your EasyEcom integration and provide your Location ID and x-api-key. If you manage multiple EasyEcom locations and need strict location-level separation, you can create a separate integration per location.

Zoho CRM — Rebuilt Connector 

What we improved — Rebuilt the Zoho CRM connector on our latest platform and launched it in production as ZOHO_CRMV2 using Zoho's current APIs for reliable record processing.

How it works — The rebuilt connector supports Zoho CRM's core modules — Leads, Contacts, Accounts, Deals, Campaigns, Tasks, Events, Calls, and Invoices — giving you a connected view of the full customer lifecycle in your warehouse. You select your marketplace/region (for example, India) at setup so authentication matches your Zoho account.

Why this matters — Zoho CRM data now processes successfully into your warehouse, replacing the previous setup where jobs completed but no records were captured.

Do you need to do anything? — Set up a new integration using the ZOHO_CRMV2 connector and select the marketplace/region that matches your Zoho account credentials.

Amazon Selling Partner — New expirationDetails Field in AWDListInventory Table

What we improved — Added the expirationDetails field to the Amazon Seller AWDListInventory table, making expiration data from Amazon's AWD (Amazon Warehousing and Distribution) API available in your warehouse.

How it works — The connector now passes the details=SHOW query parameter when fetching AWD inventory data, which causes Amazon's API to return the expiration details nested within each inventory record. The new field is included in the table schema for all integrations.

Why this matters — Operations teams can now track SKU-level expiration dates for inventory stored in Amazon AWD directly from their data warehouse, enabling proactive expiration management, compliance reporting, and reducing waste from expired stock.

Do you need to do anything? — No action required. The new field has been added to all existing and new AWDListInventory integrations.

Criteo — Connector Updated to Latest API Version

What we improved — Rebuilt the Criteo connector to use Criteo's latest API versions, migrating away from older deprecated endpoints to the current API.

How it works — The updated connector authenticates and retrieves campaign performance data using Criteo's current API infrastructure, ensuring full compatibility with Criteo's live platform.

Why this matters — The previous Criteo connector relied on API versions that Criteo had deprecated, which was causing authentication failures for some integrations. The rebuilt connector works reliably and ensures continued access to your Criteo advertising data.

Do you need to do anything? — No action required. The updated connector has been deployed automatically to all Criteo integrations.

🛠️Fixes

Amazon Selling Partner — Add Columns Utility Now Functioning

What was the issue — The Add Columns utility in the Amazon Selling Partner connector configuration was not functioning properly. When users added new columns to their tables through the utility, the columns were marked as updated but the configuration changes were not being persisted to the data pipeline.

What we fixed — Corrected the utility's backend logic to properly save column configuration changes, allowing newly added columns to load data correctly into the warehouse.

Why this matters — You can now use the Add Columns utility to expand your Amazon Seller tables with additional fields without encountering configuration errors.

Do you need to do anything? — No action required. If you previously had issues adding columns, try again now — the utility is fully functional.

Amazon Selling Partner — MongoDB Timeout Resolution

What was the issue — MongoDB operations in the Amazon Selling Partner source were timing out frequently, causing syncs to fail. The root cause was missing database indexes on critical lookup fields, forcing MongoDB to perform expensive collection scans on large datasets.

What we fixed — Increased MongoDB connection and server selection timeouts from 10 to 30 seconds, and added retry logic for transient MongoDB connection issues in read operations. Additionally, optimized database operations by enabling index-driven queries instead of collection scans.

Why this matters — Amazon Seller Partner syncs are now significantly more resilient, reducing timeout failures and improving overall data ingestion reliability for all customers using this connector.

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

Amazon Sales & Traffic Report — Improved Reliability Under New Rate Limits

What was the issue — Some Amazon Sales & Traffic reports (Sales and Traffic by Child ASIN) were delayed or missing historical dates. This was driven by new Amazon rate limits (one report request every 15 minutes, up to 96 per day per seller account) combined with an Amazon-side report processing delay in North America — recent dates loaded fine while some historical dates stayed queued.

What we fixed — We aligned our request configuration to Amazon's confirmed limits and made several reliability improvements: an updated attribution schedule that re-pulls data at 2, 4, 7, 14, and 35 days to capture late-arriving and revised figures; more efficient incremental data retrieval; run limits matched to each table's sync frequency; and staggered scheduling so integrations under the same seller account no longer compete for the same request quota.

Why this matters — Your Amazon Sales & Traffic data syncs more reliably within Amazon's limits, with fewer rate-limit errors and better recovery of delayed or restated historical dates.

Do you need to do anything? — No action required. Some historical dates may still depend on Amazon making the data available; those are retried automatically.

Amazon Selling Partner — Catalog Items No Longer Skips Valid ASINs

What was the issue — In the Amazon Seller Catalog Items table, ASINs are requested in batches. If a batch contained even one invalid ASIN, the entire batch could fail, causing valid ASINs to silently stop loading into the warehouse.

What we fixed — When a batch fails, the connector now retries each ASIN in that batch individually, so valid ASINs load successfully and only genuinely invalid ASINs are skipped.

Why this matters — Your Catalog Items data is more complete — a single problem ASIN no longer blocks others in the same batch from syncing.

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

Amazon Selling Partner — Fixed Excessive Job Retriggering

What was the issue — An issue in the Amazon Seller report retry logic caused jobs to retrigger far too often (hundreds of jobs per source within a few hours), which led to rate-limit and quota errors and could delay data.

What we fixed — Corrected the automatic re-run ("run immediately") logic so it stops retriggering after a small number of consecutive rate-limit errors, and fixed the report status and retry counters that were driving the loops.

Why this matters — Amazon Selling partner job volume is back to normal levels, reducing quota errors and keeping data delivery stable and timely.

Do you need to do anything? — No action required. The fix has been deployed.

Integration Cloning Fixed 

What was the issue — Cloning an existing integration failed with an "Integration not found" error, preventing you from quickly duplicating an existing configuration.

What we fixed — Corrected the routing logic used when cloning integrations so it identifies the integration type correctly and allow cloning.

Why this matters — You can now clone any integrations without errors, making it faster to set up similar configurations.

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

TikTok Shop — Packages Table Empty API Response Error

What was the issue — The Packages table sync failed with a pagination error whenever TikTok Shop's API returned an empty response, since the connector's pagination logic didn't account for a null result.

What we fixed — Updated the connector's schema-level pagination handling so it recognizes an empty response and ends pagination cleanly instead of throwing an error.

Why this matters — TikTok Shop Packages table syncs are now more resilient to empty API responses, reducing sync failures across all TikTok Shop integrations, not just the one that reported it.

Do you need to do anything? — No action required. The fix has been deployed at the connector level.