February 2026
New features
Redshift data warehouse support
Weld now supports Amazon Redshift as a destination data warehouse, including both Serverless and Provisioned Cluster deployments. You can now land your synced data directly into Redshift alongside BigQuery, Snowflake, and Postgres.
Primary Key visibility on incremental syncs
Primary key columns are now displayed in the UI for most incremental sync streams. Primary key columns are locked to prevent accidental filtering or hashing transformations, protecting downstream data integrity.
Multi Account Backfill
A new backfill feature for connectors that support multi-account selection, including Google Ads, Google Analytics, and Microsoft Ads. This enables syncing historical data across multiple selected accounts or properties simultaneously.
Zero-config integrations
Integrations that require no authentication (such as Weld Data and Forex) can now be set up instantly with no blank configuration forms.
Amazon Selling Partner: New authentication method
We are updating the authentication method for the Amazon Selling Partner connector.
Previously, connections authenticated through Weld's shared OAuth application. Going forward, each connection must authenticate using credentials from your own Selling Partner API (SP-API) application.
New required fields:
- Refresh Token -- generated during the authorization flow
- Client ID -- from your SP-API application
- Client Secret -- from your SP-API application
Rollout timeline
Action required by April 30, 2026. Existing connections that have not been migrated to the new authentication method by this date will experience sync failures. Please migrate as soon as possible to avoid disruptions.
- Effective now -- all new Amazon Selling Partner connections use the new authentication method.
- By April 30, 2026 -- all existing connections must be migrated.
Prefer not to manage your own SP-API application? Authentication with Weld's shared OAuth is still available on a custom quote plan. to learn more.
Who needs to migrate
You must migrate if your existing Amazon Selling Partner connection authenticates using Weld's shared OAuth.
Connections that already authenticate using a private SP-API application do not require migration.
Prerequisites
Before starting the migration, make sure you have:
- A registered SP-API application -- Register a private application in Amazon Seller Central if you don't already have one.
- Client ID and Client Secret -- Available from your SP-API application's credentials page.
- Refresh Token -- Generated by completing the self-authorization flow for your application.
How to migrate
- Log in to your Weld workspace and go to Settings โ Connectors.
- Select the Amazon Selling Partner connection.
- Click Configuration.
- Select Authenticate with Private app as the authentication method.
- Enter the Refresh Token, App Client ID, and App Client Secret from your SP-API application.
- Select the Region your Amazon account is registered in.
- Click Authorize to reauthenticate the connection.
- Trigger a test sync to confirm everything is working correctly.
For full setup instructions and data schema details, see the Amazon Selling Partner connector documentation.
New connectors
Reddit Ads
Full ELT support for Reddit advertising data including campaigns, ad groups, ads, and performance reporting.
Connector updates
Google Ads
Major reliability and scalability improvements for Google Ads syncing.
- Universal Soft Deletes: Soft deletes are now enabled for all time-based reports across all accounts. If records are modified or disappear within a synced date range, Weld will reconcile and soft-delete stale rows in your warehouse.
- Multi-Account Syncing: Completely refactored to support per-account incremental pointers, massively improving scalability for agencies or teams syncing multiple Google Ads accounts.
- Smart Notifications: Targeted warning notifications if Weld loses access to a specific Google Ads customer account, while allowing the rest of your accessible accounts to continue syncing normally.
Google Analytics 4
You can now select and sync data across multiple GA4 properties simultaneously. We also added multi-account backfill streaming and improved caching to drastically reduce Google API quota consumption.
Shopify & Shopify Plus
2 total changes
| Table/column | Change type | New name | Notes |
|---|---|---|---|
abandoned_checkouts | Updated | Chunked mode for faster, more reliable syncing | |
transactions | |||
column | New Column | payment_id | |
Additional fixes: fixed logic for parsing staffMembers and updated OAuth token refresh handling to prevent disconnects.
Amazon Selling Partner
1 total change
| Table/column | Change type | Notes |
|---|---|---|
fba_inventory_summary | New stream | History-mode stream for FBA Inventory Summary |
Improved error handling so that Amazon's "Data Not Ready" errors on Search Query Performance reports will no longer quarantine your entire sync.
AppLovin
1 total change
| Table/column | Change type | Notes |
|---|---|---|
hourly_advertisement_report | New stream | Hourly granularity for advertisement reporting |
Microsoft Ads
Fixed an issue with max retention dates on reports. Corrected the MS Ads number parser.
TikTok Ads
Optimized syncs to run lookbacks only once a day to save resources. Fixed reporting metrics.
Google Sheets
Upgraded error handling to provide clear, actionable messages in the UI when Google service accounts encounter "Invalid Grant" or permission issues.
Facebook & Instagram
Added a delay to Facebook post comment fetching to protect your app from hitting API rate limits. Fixed a bug where missing expiresIn tokens from Instagram caused sync failures.
Chargebee
1 total change
| Table/column | Change type | New name | Notes |
|---|---|---|---|
subscriptions | |||
column | New Column | plan_id | |
AWS S3
Added more graceful error handling and detailed logs when an S3 source stream fails.
Core ELT & CDC improvements
- CDC parser upgrades: Automatic conversion of nanosecond timestamps to milliseconds. Intelligent boolean-to-integer mapping to match Avro schemas.
- CDC UI safeguards: Improved state management to prevent manual triggers while a large initial CDC snapshot is still running.
- CSV download optimization: Refactored the CSV download engine to handle massive queries from BigQuery, Snowflake, and Postgres with drastically lower memory usage.
Platform fixes
- Data warehouse migrator: Fixed a race condition to ensure failed migrations retry seamlessly. Added safeguards to prevent accidental BigQuery migrations within the same project.
- User management: Fixed an edge-case bug where the system would attempt to create duplicate user profiles during authorization.
- Schema validation: Fixed an issue where integrations with extremely large dropdown menus (2000+ options) would cause validation timeouts.