Amazon customer IDs are generated using buyer email, buyer name, and shipping name. For some Amazon-fulfilled orders, these fields were not always populated in the source data, which could result in customers being identified less accurately. We've updated how this data is sourced to improve match rates.

For Amazon-fulfilled (AFN) orders, buyer email, buyer name, and shipping name are now supplemented with data from Amazon's shipment report when the primary source does not have a value. Merchant-fulfilled (MFN) orders are unaffected and continue to use the existing data source.

Customer identification for Amazon-fulfilled orders will be more accurate. You may see minor shifts in customer counts or customer profiles as previously unmatched records are now correctly attributed. No action is required.

Merchants on BigQuery can now access transformed TikTok and Pinterest paid advertising data through the UMS layer.

Added BigQuery-compatible UMS transformation scripts for TikTok (spend and vendor performance) and Pinterest paid results. Data is now processed through the standard UMS pipeline — including currency conversion, store association, and daily spend rollups into the cross-channel marketing spend table — for merchants whose warehouses run on BigQuery.

TikTok and Pinterest data will now appear in UMS reporting for BigQuery-based merchants. No action is required.

An issue with how Loop Returns data was being processed caused return figures in the Returns dashboard to be under-reported. This fix applies to BigQuery merchants only.

Some return records were being excluded during daily updates, causing the Returns dashboard to display lower numbers than expected.

We corrected the data processing logic so that all return records are accurately captured during each update cycle. Returns dashboard numbers may increase slightly as previously missing records are restored — this is expected and reflects your actual returns data. No action is required.

Subscription counts in the Subscription Monthly Churn Rates explore were appearing higher than what you see in Recharge. We've corrected this and introduced a clearer way to view subscription data at the level that matches Recharge.

The Subscription Monthly Churn Rates explore was reporting subscription counts at the product level rather than the customer level. This meant customers subscribed to multiple products were counted more than once, causing active subscription counts, new subscriptions, and churned subscriptions to appear inflated compared to what you see in Recharge.

We made two changes. First, the existing Subscription Monthly Churn Rates explore has been renamed to Subscription Monthly Churn Rates – Product Level, with the product dimension now visible, clarifying that it reports at the month + product level. Second, we created a new Subscription Monthly Churn Rates – Aggregated explore that reports at the month level, matching the subscription counts you see in Recharge.

Merchants should review the following:

Recharge extractions were hitting API rate limits, triggering throttling errors that caused workflows to run significantly longer than expected.

The Recharge extractor now implements rate limit handling aligned with Recharge's API constraints, including automatic retry logic with backoff when a rate limit is encountered.

Recharge workflows should complete faster with fewer interruptions. No action is required.

GA4 extractions were paginating at 1,000 rows per API call instead of the allowed maximum, generating excessive API requests and causing rate limit issues for high-volume merchants.

The default page size has been increased to 250,000 rows per API call, significantly reducing the number of requests required per extraction. The page size is also now configurable per integration for merchants with specific needs.

GA4 extractions will complete faster and with fewer API calls. No action is required.

A specific NetSuite permission error was not being caught during pre-launch checks, leaving merchants without a clear explanation when their account lacked access to SuiteAnalytics Connect (ODBC). The error is now detected automatically and surfaced with actionable guidance.

The pre-launch validation for NetSuite datasources now detects the SuiteAnalytics Connect permission error and returns a clear message directing merchants to their NetSuite administrator to enable access.

If your NetSuite account does not have SuiteAnalytics Connect enabled, you will now see a specific error message during setup rather than a generic failure. No action is required unless you encounter this error — if you do, contact your NetSuite admin to enable SuiteAnalytics Connect and grant your user the appropriate permissions.

Daasity's Shopify B2B integration was running on a deprecated API version, causing warnings to appear in merchant Shopify dashboards and risking data accuracy ahead of Shopify's April 1st enforcement deadline. The API version has been updated and the integration's version management has been centralized.

The Shopify GraphQL API version has been updated to the current supported release. The version is now managed from a single shared location rather than being hardcoded across individual clients, ensuring future updates require only one change. GraphQL query formatting has also been corrected to align with current Shopify API requirements.

The warning banner previously visible in some merchant Shopify dashboards will be removed. No action is required — the update applies automatically.

Integration setup and edit forms were displaying sensitive credentials — API keys, tokens, passwords, and secrets — in plaintext. We've replaced all exposed credential fields across integrations with a standardized masked input that conceals values by default, with options to reveal or copy to clipboard.

Plain text credential inputs have been replaced with a secure masked field partial across all affected integrations. The new control renders credentials as hidden by default and adds two inline actions: copy to clipboard and a reveal/hide toggle. The toggle displays the value temporarily and auto-hides after 1.5 seconds.

Algolium, App Lovin, Attentive Mobile, Back in Stock, Fairing, Hype Auditor, Impact Radius, KnoCommerce, Loop Returns, Narvar, Northbeam, Okendo, Order Desk, Pepperjam, Retail Next, Roster, Sailthru Mobile, Sailthru, Salesforce Commerce, ShipBob, ShipStation, Skio, Skubana, Social Blade, Stay AI, Survey Gizmo, and Target Plus.

Existing credentials are unaffected — no re-entry required. The fields now appear masked when viewing or editing an integration. No action is required.

We optimized how Vendor Performance data is processed daily. The table was previously being dropped and fully rebuilt every day, which was inefficient and created unnecessary strain on the data pipeline. We've replaced this with a 90-day incremental lookback window, so each daily refresh only reprocesses the last 90 days of data rather than rebuilding from scratch.

Full daily rebuild replaced with 90-day incremental refresh. Instead of dropping and recreating the entire Vendor Performance table each day, the system now incrementally updates the last 90 days of data. The 90-day window aligns with the maximum attribution window supported by major ad platforms, ensuring all platform-attributed conversions are captured within each refresh cycle.

Facebook Ads, Google Ads, Amazon (Sponsored Products, Sponsored Display, Sponsored Brands), TikTok, Pinterest, Snapchat, Bing, AppLovin, Criteo, Criteo Retail, Pepperjam, and marketplace channels including Kohls, Wayfair, Target, and Walmart.

You may see slight adjustments in Vendor Performance metrics during the transition as the new incremental approach takes effect. This is expected. No action is required — the update rolls out automatically.