✨New Features

ParcelLab — New Connector

OrderProtection — New Connector

🚀Enhancements

TikTok Ads — New GMV Max Creative Daily Table

• What we improved — Added a new GMV_Max_Creative_Daily table to the TikTok Ads connector, providing creative and video-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? — New table is available to add to your integration. Support for "All Products" campaign types will be added in a future update.

AfterShip — Upgraded Connector to New Version

• What we improved — Upgraded the AfterShip connector to the latest API version (V3), updating all core table endpoints to ensure continued data availability after AfterShip deprecated their older API endpoints.
• How it works — The updated connector uses the latest 2026-01 API endpoints for Couriers, Trackings, and Returns tables. The new version is available as the Aftership_Beta connector. Existing integrations on the older version will be migrated once validation is complete.
• Why this matters — AfterShip deprecated their older API endpoints, which were returning 404 errors and preventing data from syncing. The upgrade ensures your shipment tracking, courier, and returns data continues to flow reliably.
• Do you need to do anything? — Our Support team will coordinate migration to the updated connector if you are currently using AfterShip.

Skio — New CancelFlowV3Sessions Field for Subscriptions

• What we improved — Added the CancelFlowV3Sessions field to the Skio connector's Subscriptions table, providing cancellation flow session data from Skio's latest V3 API alongside the existing V2 field.
• How it works — The connector now fetches the V3 cancel flow session data from Skio's API. The new field automatically populates once data is available from the source via auto column detection.
• Why this matters — If you use Skio for subscription management, you can now access the latest cancellation flow session data, which provides more accurate and complete information compared to the V2 field that was returning null values.
• Do you need to do anything? — To enable the new field, select the new columns in your integration settings. Please take a backup of your existing data before selecting, as it will require a table reload.

Shopify — New Order Fulfillments Table with Estimated Delivery Date

• What we improved — Added a new order_fulfillments table to the Shopify connector, which includes the estimatedDeliveryAt field sourced from Shopify's GraphQL API.
• How it works — The new table fetches fulfillment data including estimated delivery dates via Shopify's GraphQL API. This field is populated when orders are fulfilled using carrier-integrated shipping services that provide delivery ETAs.
• Why this matters — You can now access estimated delivery dates for fulfilled orders directly in your warehouse data, enabling more comprehensive shipping and logistics reporting.
• Do you need to do anything? — The new table is available to add to your Shopify integration. Note that the estimatedDeliveryAt field is only populated for fulfillments processed via carrier-integrated services, not manual fulfillments.

TikTok Shop — Settlement Period Configuration

• What we improved — Added a settlement period dropdown to the TikTok Shop connector's integration configuration, allowing you to specify the correct lookback window for your shop's Order Statement Transactions table.
• How it works — During integration setup, you can now select your TikTok Shop's settlement period (the number of days TikTok takes to settle payments). This setting controls the lookback window for the Order Statement Transactions table, ensuring data syncs capture all settlement updates accurately. Existing integrations have been set to a 10-day default.
• Why this matters — Different TikTok Shops have different settlement periods based on shop performance. Configuring the correct period prevents data discrepancies in your Order Statement Transactions table.
• Do you need to do anything? — Check your TikTok Shop settlement period in the TikTok Shop console and update the setting in your integration configuration if it differs from the 10-day default.

Amazon Seller — Migrated to New Orders API Version

• What we improved — Migrated the Amazon Seller connector from the deprecated Orders API v0 to the new Orders API v2026-01-01, ensuring continued access to order data as Amazon phases out the older version.
• How it works — A new SearchOrders table has been implemented using Amazon's latest Orders API. The new API version uses role-based permissions instead of Restricted Data Tokens, and includes expanded data fields such as buyer, recipient, fulfillment, proceeds, expense, promotion, cancellation, and package information.
• Why this matters — Amazon has officially deprecated the Orders API v0. This migration ensures your order data continues to sync reliably and gives you access to richer order details through the new API.
• Do you need to do anything? — Your Customer Success Manager will coordinate the migration from the legacy Orders table to the new SearchOrders table. A migration timeline will be communicated separately.

Podscribe — Dynamic Attribution Window Configuration

• What we improved — Added a configurable attribution window option to the Podscribe connector UI, allowing you to select the lookback period for data syncs.
• How it works — During integration setup or editing, you can now choose the attribution window (e.g., 7 days) that determines how far back the connector looks for updated data on each sync. This prevents data gaps caused by delayed API responses from Podscribe.
• Why this matters — Previously, Podscribe data syncs could experience gaps when the source API had delayed data availability. The configurable attribution window ensures complete and reliable data flow.
• Do you need to do anything? — Check your Podscribe integration settings to configure the desired attribution window if the default does not suit your needs.

Facebook Ads — Migrated User Segment Reporting to Async API

• What we improved — Migrated the Facebook Ads adinsights_usersegment table from synchronous API requests to Meta's asynchronous reporting flow, resolving persistent rate limit errors that had been preventing data from loading.
• How it works — The connector now submits reporting jobs to Meta's async queue, polls for completion, and then downloads the pre-computed results with cursor-based pagination. Each sync uses single-day date ranges to minimize compute cost and includes intelligent backoff handling for rate limits.
• Why this matters — The user segment breakdown at ad level is one of the most compute-intensive queries in Meta's Insights API. The previous synchronous approach was exhausting the app's compute quota, causing data ingestion to stall. The async migration ensures reliable, uninterrupted data flow for this table.
• Do you need to do anything? — No action required. The improvement has been applied to all Facebook Ads integrations using the adinsights_usersegment table.

Amazon Sponsored Products — Migrated KeywordBidRecommendations to v4 API

• What we improved — Migrated the SponsoredProducts_KeywordBidRecommendations table from Amazon's deprecated v2 keyword-level bid recommendation endpoint to the new v4 theme-based bid recommendation endpoint.
• How it works — The connector now uses Amazon's v4 API, which provides theme-based bid recommendations at the ad group level. The new endpoint uses content-type versioning and includes updated request/response handling with improved error recovery and retry logic for rate limits.
• Why this matters — Amazon has deprecated the v2 Sponsored Products API. This migration ensures your keyword bid recommendation data continues to sync reliably and gives you access to Amazon's improved theme-based recommendation system.
• Do you need to do anything? — No action required. The migration has been applied to all Amazon Sponsored Products integrations.

🛠️Fixes

Amazon Sponsored Products — Missing ASINs in ProductMetadata Table

• What was the issue — The ProductMetadata table in the Amazon Sponsored Products connector was not loading all ASINs. The table used cursor-based pagination, but the Amazon API for this endpoint requires offset-based pagination (page index), causing only the first page of results to be fetched.
• What we fixed — We updated the pagination logic from cursor-based to offset-based (using page size and page index), ensuring all product metadata records are properly fetched across multiple pages.
• Why this matters — All ASINs and their corresponding product metadata are now fully loaded into your warehouse, giving you complete visibility into your sponsored product catalog.
• Do you need to do anything? — No action required. The fix has been deployed and applies to all Amazon Sponsored Products integrations.

Daton Platform — Connector Re-authentication Failure

• What was the issue — When re-authenticating a connector (for example, after a password change or token expiry), the system was reusing expired credentials from the previous session instead of clearing them first. This caused re-authentication to fail repeatedly, preventing data syncs from resuming.
• What we fixed — We updated the re-authentication process to automatically clear all stored credentials before beginning a new authentication flow, ensuring a clean start every time.
• Why this matters — If you ever need to re-authenticate a connector, the process will now complete reliably on the first attempt without errors from stale credentials.
• Do you need to do anything? — No action required. The fix applies automatically to all connectors.

PostgreSQL Database Connector — Item Table Data Load Failure

• What was the issue — The PostgreSQL Database connector's Item table was failing to load data due to an internal type casting error. When the source database contained NaN (Not a Number) values in numeric fields, the connector was unable to properly convert them, causing the data pipeline to fail with no records being processed.
• What we fixed — We corrected the internal type handling logic to properly recognize and convert NaN values from PostgreSQL numeric fields, ensuring they are correctly translated during data ingestion.
• Why this matters — If you use the PostgreSQL Database connector and your source data contains NaN values, your data syncs will now complete reliably without type conversion errors.
• Do you need to do anything? — No action required. The fix has been deployed and applies to all PostgreSQL Database integrations.

Amazon Seller — Column Language Mismatch in European Marketplace Reports

• What was the issue — The PanEuropeanEligibilityFBAASINs table in the Amazon Seller connector was returning null values for some European marketplace integrations (Germany, Spain, and Italy). The root cause was a language mismatch — the Amazon API was returning column headers in a different language than expected (for example, Spanish headers for a German marketplace), causing the data mapping to fail.
• What we fixed — We updated the connector's column mapping logic to correctly handle multilingual API responses across European marketplaces, ensuring data is properly parsed regardless of the response language.
• Why this matters — If you use Amazon Seller with European marketplaces (DE, ES, IT), your PanEuropeanEligibilityFBAASINs data will now sync correctly with all fields populated.
• Do you need to do anything? — No action required. The fix has been applied across all affected European marketplace integrations.

TikTok Ads — GMV Accounts Retrieval

• What was the issue — TikTok Ads integrations failed to retrieve Shop IDs after the deployment of a new auto-fetching API. Legacy integrations that previously used manual Shop name inputs were not updated with the configuration settings required for the new automated ID retrieval, causing data syncs to fail.
• What we fixed — We propagated the updated settings and logic to all existing integrations, ensuring all accounts correctly utilize the auto-fetching API for Shop ID retrieval.
• Why this matters — If you use TikTok Ads with GMV data, your integration syncs are now restored and running reliably with the new automated Shop ID retrieval.
• Do you need to do anything? — No action required. The fix has been applied to all TikTok Ads integrations.

Google Ads — BigQuery Numeric Precision Error in Report Tables

• What was the issue — Google Ads report tables (including search term, search keyword, and campaign details) were failing to load data into BigQuery. The Google Ads API was returning metric values with more than 9 decimal digits, which exceeds BigQuery's NUMERIC type precision limit, causing data ingestion to fail.
• What we fixed — We updated the data processing logic to properly handle high-precision decimal values from the Google Ads API, ensuring they are correctly rounded or cast before loading into BigQuery.
• Why this matters — If you use Google Ads report tables, your data syncs will now complete reliably without precision-related errors, even when the API returns high-precision metric values.
• Do you need to do anything? — No action required. The fix has been deployed and applies to all Google Ads integrations.