All Integrations - MerchantFlow

Integrations Overview

MerchantFlow integrations connect your commerce platform, advertising channels, Google services, fulfillment providers, and AI clients into a single profitability and analytics workspace. Most data-source integrations are managed from the onboarding flow or Settings > Integrations within your MerchantFlow dashboard. MerchantFlow's MCP server is configured separately from Settings > Developer > MCP.

This page lists every supported integration, explains the shared connection model for Google services, and covers the permissions required to manage integrations.

Who Can Manage Integrations

Integration changes require the integrations:manage permission. In the current role model:

• Owner -- full integration management
• Admin -- can connect, reconnect, disconnect, and configure integrations
• Analyst and Viewer -- can inspect integration state but cannot manage connections

For more on roles, see Roles and Permissions.

Core Integration Rules

• Each merchant tenant uses one primary commerce platform at a time (either Shopify or WooCommerce)
• Google services share a single OAuth connection, then use a configuration modal to choose the exact property, account, and site
• Manual sync is available after onboarding is complete and live billing access is valid
• If no supported 3PL is connected, MerchantFlow can fall back to a manual fulfillment percentage
• MerchantFlow's MCP Server is a separate AI access surface managed from Settings > Developer > MCP, not Settings > Integrations

OAuth Prerequisites

For OAuth-based integrations such as Google, Shopify, Meta, Snapchat, TikTok, Pinterest, and Klaviyo, MerchantFlow checks:

• Verified email on your MerchantFlow account
• Two-factor authentication, when it applies to your login

The 2FA check is satisfied automatically for accounts that sign in only through a social provider (Google sign-in, Shopify), because those logins have no MerchantFlow password to protect. Accounts with an email-and-password login must have 2FA enabled before the connect flow will start.

If either requirement is missing, MerchantFlow blocks the connect flow until the account is secured. See Security Settings for setup instructions.

These same checks also apply to the fulfillment providers, which are connected by pasting API credentials rather than through an OAuth redirect. WooCommerce is the only connect path that skips them -- it checks the integrations:manage permission alone.

Commerce Integrations

Google Services (Shared OAuth)

MerchantFlow uses a shared Google OAuth connection for all Google services. One authorization requests four scopes -- analytics.readonly, webmasters.readonly, content (Merchant Center), and adwords -- and then you open Configure Google Services to choose the exact property, site, merchant account, and Google Ads customer accounts to sync.

• Google Analytics 4 -- traffic, sessions, and revenue data
• Google Ads -- campaign spend and paid performance
• Search Console -- organic search queries, clicks, and impressions (gated -- off by default)
• Merchant Center -- product feed diagnostics and approval status (gated -- off by default)

Search Console and Merchant Center sit behind per-workspace feature flags (search_console_enabled and merchant_center_enabled) while their data pipelines are being stabilized. When the flag is off for your workspace, the service row is hidden from the Google card and from Configure Google Services entirely -- it is not a bug, and any credentials you connected earlier are left untouched until the flag is turned back on.

Advertising Integrations

• Meta Ads -- Facebook and Instagram ad spend and campaign performance
• Google Ads -- paid search and Shopping spend, via the shared Google connection
• Snapchat Ads -- Snapchat campaign data (environment-gated)
• TikTok Ads -- TikTok campaign data (environment-gated)
• Pinterest Ads -- Pinterest campaign data, behind the pinterest_ads_enabled flag while the Pinterest app awaits Standard API access. The card shows Coming Soon unless an admin has enabled it for your workspace.

Meta, Snapchat, TikTok, and Pinterest each support multiple ad accounts per workspace. Google Ads supports multiple customer IDs on the single Google connection. For Meta you can also exclude individual campaigns from a store's profit, for example when one ad account advertises for two stores.

Email and SMS Integrations

• Klaviyo -- email and SMS campaign performance and attributed revenue

Fulfillment Integrations

• Speedfulfill 3PL -- warehouse shipping costs and tracking numbers
• CJ Dropshipping -- per-order product and shipping cost sync (available to all workspaces)
• Gooten -- print-on-demand per-order COGS and shipping (available to all workspaces)
• ShipMonk -- 3PL fulfillment data (API key plus store ID), behind the shipmonk_enabled flag
• Printful -- print-on-demand per-order COGS, shipping, and tax (a private bearer token), behind the printful_enabled flag
• Percentage-of-product-cost or per-product fulfillment rates if you do not use a supported 3PL

All five fulfillment providers are connected with API credentials entered in MerchantFlow, not a browser OAuth redirect. See Fulfillment Costs for the non-3PL methods.

AI and Developer Integrations

• MCP Server -- connect Claude, Cursor, Windsurf, and VS Code to MerchantFlow over OAuth 2.1 with PKCE so AI clients can read your store data safely

Tracking and Troubleshooting

• UTM Tracking -- campaign attribution via URL parameters
• Troubleshooting Integrations -- fix common connection issues
• Manual Sync -- trigger syncs on demand

Frequently Asked Questions

How many integrations can I connect at once?

You can connect one commerce platform (Shopify or WooCommerce), all available Google services, every advertising channel enabled for your workspace, Klaviyo, and one or more fulfillment providers simultaneously. Meta, Snapchat, TikTok, and Pinterest each hold multiple ad accounts, and Google Ads holds multiple customer IDs -- MerchantFlow does not impose a fixed cap on the number of ad accounts. MCP client connections are managed separately from Settings > Developer > MCP.

Do I need separate logins for each Google service?

No. MerchantFlow uses a shared Google OAuth connection for GA4, Search Console, Merchant Center, and Google Ads. You authorize once and then select the specific properties and accounts to sync. Search Console and Merchant Center only appear in that picker when they are enabled for your workspace.

What happens if an integration disconnects?

MerchantFlow retains your historical data. Reconnect the integration from Settings > Integrations to resume syncing. See Troubleshooting Integrations for common fixes.

Related Guides

• Sync Overview -- understand how data syncing works
• First Sync -- what to expect after connecting
• MCP Server -- connect MerchantFlow to Claude, Cursor, Windsurf, and VS Code
• Shopify Billing -- billing for App Store installs
• Data Security -- how MerchantFlow protects your data

---

Last updated: August 26, 2026