Connect a datasource (OAuth or API key)

Connecting a datasource follows one of three patterns depending on the platform: OAuth, API key, or file upload. All connections start from Settings → Integrations.

After connection, an initial sync runs. Most stores complete the initial sync in 5–15 minutes; stores with extensive history may take longer. The workspace remains usable during the sync.

Which method does each platform use?

Platform	Method
Shopify, BigCommerce, WooCommerce, Amazon Seller	OAuth
Google Ads, Meta, TikTok, Pinterest, Microsoft, Amazon Ads	OAuth
Google Analytics 4	OAuth
Stripe	OAuth
Klaviyo	API key
Recharge	API key
Custom costs	File upload (CSV)

OAuth connection flow

OAuth integrations open the source platform’s own authorization screen. Ignyte IQ never sees the source account’s password.

1. Go to Settings → Integrations and select the platform.
2. Click Connect. The source platform’s authorization screen opens in a new window.
3. Sign in to the source platform (if not already signed in) and approve the requested scopes.
4. The browser returns to Ignyte IQ. The integration shows Connected with status Initial sync in progress.
5. Wait for the initial sync. Track progress in the Data panel.

🖼️ Screenshot

[oauth-connection-flow.png] — Two-panel image: (1) Settings → Integrations with the Shopify card showing the Connect button, (2) Shopify's authorization screen with scopes listed. Annotate each step.

Required source-platform role: documented per platform — for example, Shopify staff role with orders/customers/products permissions; Meta Business Manager admin for the relevant ad account; Google Ads MCC or individual account access.

API key connection flow

API-key integrations require generating a token on the source platform and pasting it into Ignyte IQ.

1. On the source platform, generate an API key (or “private token,” depending on platform terminology). For Klaviyo: Account → Settings → API Keys → Create Private API Key.
2. Copy the key. Keep the source-platform tab open in case the key disappears after the first display.
3. In Ignyte IQ, go to Settings → Integrations and select the platform.
4. Paste the API key into the API key field and click Connect.
5. The integration shows Connected if the key is valid. Initial sync begins.

Store the key securely

API keys grant read access to the source account. Treat them like passwords — do not paste them into chat or commit them to source control. The key only needs to exist on Ignyte IQ’s side once; rotation can be done by generating a new key and reconnecting.

🖼️ Screenshot

[api-key-connection-form.png] — Klaviyo connection form in Settings → Integrations: API key input field, a "where to find this" link, and the Connect button. Annotate the input field.

File upload (custom costs)

The Custom costs CSV upload doesn’t use a credential. Instead, CSV files are uploaded directly to Ignyte IQ on a schedule. See Custom costs (CSV upload) for the file format and upload flow.

After connecting

Once the initial sync completes, verify data is flowing:

1. Open the Data panel (top-right). The new datasource appears with Connected status and a recent last updated timestamp.
2. Open Brand Overview and set the date range to Yesterday. Tiles populate as data syncs.

For the full verification sequence, see Verify your data is flowing.

Troubleshooting

• OAuth fails on the source side — confirm the OAuth account has the required role. Log out of the source platform in another tab and retry.
• OAuth screen reports insufficient permissions — the authorizing user does not have the required source-platform role.
• API key rejected — the key may be invalid, expired, or scoped insufficiently. Regenerate on the source platform.
• Integration shows Disconnected shortly after connecting — the token was revoked or source account permissions changed. Reconnect.
• Authorization completed but no data appears after 15 minutes — see Datasource won’t connect.

Related articles

Integrations overview

Reconnect a datasource

Connect your first datasource

Datasource won't connect