Integrations and product data
Upsurge can connect to your commerce, advertising, analytics, email, AI, and productivity services. Product data can arrive through a managed commerce sync or a CSV import.
Choose a path
| Goal | Start with |
|---|---|
| Connect a service for workflows, reporting, or event export | Third-party connections |
| Keep Shopify, WooCommerce, or BigCommerce products in sync | Product sync |
| Create or update a catalog from a spreadsheet export | CSV product import |
How connections work
- You select a provider in Dashboard → Integrations.
- Upsurge collects the provider-specific credentials and settings.
- OAuth authorization or credential verification runs server-side.
- Upsurge stores encrypted credentials and returns only connection status and sanitized metadata.
- Syncs and workflow actions run asynchronously with retry and idempotency controls.
Connections belong to one Upsurge workspace. Commerce connections also bind catalog data to one selected site.
Keep secrets out of storefront code
Provider access tokens, API keys, OAuth client secrets, service-account keys, and webhook secrets must be entered in the dashboard or sent from a trusted server. Never embed them alongside the browser SDK.
Product source of truth
Choose one primary ingestion path per site:
- Use commerce sync when the provider catalog should remain authoritative.
- Use CSV import for migrations, periodic batch updates, or catalogs without a supported commerce connection.
- Use manual product editing for small, exceptional corrections.
Both sync and CSV import upsert products rather than replacing the entire site catalog. Review SKU and provider identifiers before combining ingestion methods so that you do not create parallel product records.
Related guides
- Recommendations explains how catalog quality affects eligibility and ranking.
- Workflows explains how integration actions use a connected provider.
- API authentication explains merchant ID tokens and server-side access.