🛠️Fixes

Amazon Selling Partner — PricingForASIN Data Load Failure

• What was the issue — The PricingForASIN table in the Amazon Seller connector was failing to load data into BigQuery. The error occurred because the Product.Offers field was defined as a non-repeated (single value) field in the schema, but the API sometimes returns it as an array.
• What we fixed — We updated the warehouse schema to correctly support array (repeated) structures for the Product.Offers field, ensuring data loads succeed regardless of whether the API returns a single value or an array.
• Why this matters — If you use the PricingForASIN table, your data syncs will now complete reliably without schema-related errors.
• Do you need to do anything? — The schema fix has been applied automatically. Affected Table should be reloaded to adopt the updated schema — please take a backup of your existing table first, then reload via the integration settings. Contact support if you need assistance.

Amazon Selling Partner — FBAInventorySummary_full Table Auto-Creation

• What was the issue — The FBAInventorySummary_full table was being automatically created in BigQuery for Amazon Seller Partner and Vendor Central integrations, even when users had not explicitly selected it. This created an unintended table in customer warehouses.
• What we fixed — We removed the auto-creation logic so that the FBAInventorySummary_full table is only created when explicitly selected by the user during integration setup. Existing integrations that already have this table are not affected.
• Why this matters — Your Amazon integrations will no longer generate unexpected tables in your warehouse. Only the tables you explicitly select will be created.
• Do you need to do anything? — If you see an FBAInventorySummary_full table that you did not request, you can safely delete it from your warehouse. Contact support if you need assistance.

Roadshow (Zenshows) — Lookback Window Addition

• What was the issue — The Roadshow (Zenshow) connector did not have a lookback (attribution) window, which meant that any data updates or changes made retroactively in Roadshow were not being captured in your warehouse after the initial sync.
• What we fixed — We added a lookback (attribution) window to the Roadshow connector. The connector now re-syncs recent historical data during each run, ensuring that any retroactive updates — such as delayed order attributions, status changes, or revised metrics — are captured accurately in your warehouse.
• Why this matters — Your Roadshow data will now stay in sync with source changes, even when updates are applied retroactively. This gives you more accurate and complete reporting without needing manual reloads.
• Do you need to do anything? — Yes, you need to configure this lookback window while setting up your integration.

Gorgias — Events Table Data Load Failure

• What was the issue — The Events table in the Gorgias connector was failing to load data into your warehouse. This was caused by the connector generating duplicate column definitions when processing nested customer integration records, which led to JSON parsing errors during the data load.
• What we fixed — We updated the Gorgias connector's data extraction logic to properly handle nested integration metadata. Instead of creating separate columns for each nested record (which caused naming conflicts), the connector now transforms this data into clean key-value pairs. All affected Gorgias integrations are being updated with this fix.
• Why this matters — If you use the Gorgias Events table, your data syncs should now complete reliably without interruption. The underlying data structure is also cleaner, making it easier to query integration-related fields.
• Do you need to do anything? — No action required. The fix is being rolled out to all Gorgias integrations automatically.

KnoCommerce — Missing Survey Responses in Warehouse

• What was the issue — Survey response data from KnoCommerce was not appearing in your warehouse. While responses were visible in the KnoCommerce dashboard, the corresponding response fields in the warehouse table were empty.
• What we fixed — We identified that the KnoCommerce API has a delay in making newly submitted survey responses available. To account for this, we added a lookback window to the KnoCommerce connector's sync process, ensuring that recently submitted responses are captured even if they aren't immediately available from the API.
• Why this matters — If you use KnoCommerce survey data for attribution or customer insights, your response data will now sync completely and reliably to your warehouse.
• Do you need to do anything? — No action required. The fix has been applied to all KnoCommerce integrations automatically.

Criteo — Retail Media Report Tables Failing

• What was the issue — Several Retail Media report tables in the Criteo connector were failing for existing integrations. The issue was discovered during onboarding of a new client and affected report data ingestion across Criteo Retail Media integrations.
• What we fixed — We updated the connector to the latest supported API and resolved the table failures, restoring reliable data syncs for all affected Criteo Retail Media report tables.
• Why this matters — If you use Criteo Retail Media data, your report tables are now syncing reliably again.
• Do you need to do anything? — No action required. The fix has been applied to all affected Criteo integrations automatically.

Unicommerce — Facilities Pagination Limit

• What was the issue — The Unicommerce connector was only returning a maximum of 200 facilities, even for accounts with more than 200 facilities configured. This meant some facilities were missing from your warehouse data.
• What we fixed — We increased the default pagination limit in the Unicommerce connector to ensure all facilities are fetched during data syncs, regardless of how many are configured in your account.
• Why this matters — If you have more than 200 facilities in Unicommerce, all of them will now appear correctly in your warehouse data.
• Do you need to do anything? — The fix applies automatically to all Unicommerce integrations. You can modify the integration and select more facilities if required.

TikTok Ads — Variable Resolution Failure for GMV Max Tables

• What was the issue — The TikTok Ads connector was throwing errors when processing GMV Max tables for certain integrations. The issue was caused by an incorrect variable handling which expected a list format but received a single value for the item_group_ids parameter.
• What we fixed — We corrected the settings to properly handle single-value parameters in the GMV Max table configuration. The fix has been applied to all affected integrations.
• Why this matters — If you use TikTok Ads GMV Max tables, your data syncs will no longer fail due to this variable resolution error.
• Do you need to do anything? — No action required. The fix has been applied automatically.

TikTok Ads — GMV tables failing with "No ad id found" error

• What was the issue — GMV tables fetch ad data linked to a tiktok shop. TikTok Ads data syncs were failing with "No ad id found" errors when the integration had selected advertiser ids without a shop attached to them. The system was not properly filtering out advertiser accounts that lacked a required Store ID before attempting to fetch GMV-related data.
• What we fixed — We updated the connector's data source settings to properly handle exit conditions when the accounts without a Store ID are encountered by skipping such accounts based on API response
• Why this matters — Your GMV tables in TikTok Ads will no longer fail with "No ad id found" error.
• Do you need to do anything? — No action required. The fix has been applied to all TikTok Ads integrations.

TikTok Ads — Retry Limit for Stuck Reports in Queuing/Processing States

• What was the issue — TikTok Ads data syncs could become stalled when reports got stuck in Queuing or Processing states. The system would retry these reports indefinitely, eventually causing the data pipeline to get stuck and stop updating — leading to multi-day data gaps.
• What we fixed — We added a retry limit for reports stuck in intermediate states. After the maximum retry attempts, the system now gracefully recovers by re-creating the report from scratch instead of hibernating. All affected integrations have been updated.
• Why this matters — Your TikTok Ads data will no longer experience extended outages due to reports getting stuck in intermediate states. The connector now self-recovers automatically.
• Do you need to do anything? — No action required. The fix has been applied to all TikTok Ads integrations.

🚀Enhancements

TikTok Shop — Expanded to Germany, Spain, and France Marketplaces

• What we improved — Added support for three new European marketplaces in the TikTok Shop connector: Germany, Spain, and France. You can now sync TikTok Shop data from these regions alongside your existing marketplaces.
• How it works — The TikTok Shop connector now recognizes Germany, Spain, and France as available marketplaces. When setting up your TikTok Shop integration, you can select these new regions to begin syncing order, product, and shop performance data from them.
• Why this matters — If you sell through TikTok Shop in Germany, Spain, or France, you can now bring that data into your warehouse for unified reporting and analytics across all your TikTok Shop regions.
• Do you need to do anything? — To start syncing data from these new marketplaces, create an integration and add the desired region.

ShipHero — New Products_Updated and Warehouse_Products_Updated Tables

• What we improved — Added two new tables to the ShipHero connector: Products_Updated and Warehouse_Products_Updated. These tables use the "updated" date parameter instead of the "created" date parameter, ensuring you capture product changes over time rather than only newly created records.
• How it works — The new tables fetch product data based on when records were last updated, allowing incremental syncs to pick up any modifications to existing products. The original tables (using created date) remain available for historical data.
• Why this matters — You can now track product updates and warehouse product changes in your data warehouse, giving you a more complete and current view of your ShipHero product catalog.
• Do you need to do anything? — The new tables are available to add to your ShipHero integration.

Amazon Sponsored Products & Sponsored Brands — Report Scheduling

• What we improved — We optimized how Amazon Sponsored Display ad report jobs are scheduled and retried. The system now intelligently runs data loads only when report data is actually available from Amazon, reducing unnecessary job attempts and improving overall sync speed.
• How it works — The pipeline now starts after 2:00 AM in your source region's timezone. If Amazon's API indicates data isn't ready yet, the system automatically reschedules rather than marking the job as failed. Once all attribution data is loaded, the next full sync is scheduled for the following day.

If intraday is enabled, reports will continue to refresh data every 2 hours as usual.

• Why this matters — This reduces the number of unnecessary job runs by approximately 40%, leading to faster overall data load times and fewer skipped jobs. Your Amazon Sponsored Products and Brands data will sync more reliably and efficiently.
• Do you need to do anything? — No action required. This improvement has been automatically applied to all Amazon Sponsored Products and Brands integrations across both Daton and Pulse.

TikTok Ads — New GMV Max Campaigns Product metrics Table

• What we improved — Added a new GMV_Max_Campaigns_Productmetrics table to the TikTok Ads connector, providing product creative level performance metrics for Product GMV Max campaigns.
• How it works — The new table captures daily metrics for each video creative used in GMV Max campaigns, including product impressions, product clicks, click-through rates, video view rates, orders, and gross revenue. Data is available for campaigns that promote specific (customized) products.
• Why this matters — You can now analyze which video creatives are driving the most product engagement and revenue in your GMV Max campaigns, helping you optimize your creative strategy.
• Do you need to do anything? — If you need this table, you should edit the integration and add it.

TikTok Ads — Added Cron Scheduling

• What we improved — Added cron-based scheduling support to the TikTok Ads connector, enabling time-based triggering for data syncs independent of the standard integration frequency.
• How it works — The TikTok Ads connector now supports cron scheduling, allowing syncs to be triggered at specific times. This enables scheduled historical backfills and time-sensitive data fetches for TikTok Ads tables
• Why this matters — Your TikTok Ads data syncs can now run on precise schedules, improving reliability for backfills.
• Do you need to do anything? — Cron scheduling is now available for all TikTok Ads integrations. You can modify integrations to set cron frequency.