MerchantFlowMerchantFlow Docs
Data Sync

Selective Sync - Sync One Provider

Choose a specific MerchantFlow integration to sync instead of refreshing all providers. Target Shopify, Google, Meta, or other platforms individually.

Selective Sync

Selective sync in MerchantFlow lets you rerun data synchronization for a single integration provider instead of refreshing your entire workspace. This is useful when only one data source appears stale while others are current, or when you have reconfigured a specific integration and need a targeted refresh.

Where to Use Selective Sync

Open Settings > Integrations, click Manual Sync Runner in the Control Panel, and use the Sync Scope selector at the top of the modal.

Available Sync Scopes

The runner only shows scope buttons for providers you have connected. The full set is:

  • All Integrations - syncs every connected provider
  • Google Services - Google Analytics 4, Search Console, Merchant Center, and Google Ads
  • Shopify Store - Shopify products and orders
  • WooCommerce - WooCommerce products and orders
  • Meta Ads - Meta (Facebook/Instagram) Ads
  • Snapchat Ads - Snapchat Ads
  • TikTok Ads - TikTok Ads
  • Pinterest - Pinterest Ads
  • Klaviyo - Klaviyo email and SMS data
  • Speedfulfill - Speedfulfill 3PL fulfillment data
  • CJ Dropshipping - CJ Dropshipping fulfillment data
  • Gooten - Gooten fulfillment data
  • Printful - Printful fulfillment data

Pinterest and Printful ship disabled by default. Each sits behind a feature flag MerchantFlow controls, so most workspaces cannot connect them and never see those two scopes.

MerchantFlow resolves those scopes into the underlying sync categories it needs to run in the background. Commerce scopes map to products and orders; ad platform scopes map to ad spend; the Google scope maps to analytics and ads. Fulfilment providers run through a separate fulfilment sync endpoint.

When to Choose Each Scope

  • All Integrations - use when the whole workspace needs a fresh pass
  • Google Services - use after changing a Google property, site, merchant account, or ads selection
  • Shopify Store or WooCommerce - use when commerce data looks stale but marketing data is fine
  • Meta Ads, Snapchat Ads, TikTok Ads, or Pinterest - use when paid-media data is the only stale area
  • Speedfulfill, CJ Dropshipping, Gooten, or Printful - use when fulfillment and shipment data needs to catch up

Normal vs Full History Sync Depth

  • Normal Sync is the default incremental option: "Incremental updates from last sync point."
  • Full History is a forced reprocessing pass: "Force re-fetch 5 years of historical data."

Use Full History carefully, especially on large live workspaces, because it can take up to 30 minutes depending on catalog size.

If you are unsure which mode to use:

  • start with Normal Sync
  • move to Full History only after fixing the configuration issue or when a normal rerun does not repopulate the expected data

Frequently Asked Questions

Can I sync only Google Analytics without syncing Google Ads?

Not in the current runner. The Google Services scope covers the Google integrations together. A more granular breakdown is not available at this time.

Can I sync only some of my Meta ad accounts?

Yes. When you select the Meta Ads scope and have two or more enabled Meta ad accounts, an account picker appears below the scope selector. Leaving every account selected is the same as syncing all of them.

How long does a selective sync take?

An incremental selective sync for one provider is usually the fastest option available. Full History runs take longer and can reach the 30-minute ceiling the runner warns about, depending on catalog size and order history.

Does a selective sync affect the automatic background schedule?

No. Running a selective sync does not pause or reset the regular 30-minute background cadence for any provider.

When should I use Full History instead of Normal Sync?

Use Full History when you have changed the selected property or account within an integration, when data was accidentally reconfigured, or when a Normal Sync does not repopulate missing data after a fix.


Last updated: August 29, 2026

Last updated on

On this page