MarqIQ
Browse all help topics
How to9 min read

Connect Snowflake

Last updated 25 September 2026Available onProBusinessEnterpriseSnowflake needs Pro or above, and a Free Trial workspace counts as Pro for this. It uses one of your plan’s connected-tool slots. Data sync is in early access: connecting stores and checks your credentials, and no Snowflake data reaches your reports yet.

Connecting Snowflake stores the account, user and warehouse details MarqIQ will use when warehouse sync ships. Nothing is read from your warehouse today, so connect it to hold the setup rather than to fill a report this week. If you want numbers on screen now, connect a CRM instead and read How connecting a tool works first.

Before you start

Warehouse sync is not live yet

Snowflake is an early-access source. The Snowflake page carries an amber notice headed "Data sync for Snowflake is in early access", which reads: "Connecting stores and validates your credentials, but automated data sync for this source isn’t live yet — Snowflake data won’t appear in your reports until it ships. We’ll enable your connection automatically when it does." Plan no reporting around Snowflake until that changes.

Plan required

Snowflake is a Pro-and-above tool. On Explore Integrations the Snowflake card carries a Pro+ badge, and where your plan or your tool allowance will not take it the button reads Upgrade to connect rather than Connect, with the reason printed under the card. Pro includes two tools besides Google Tag Manager and allows one tool per category, so Snowflake, Google BigQuery and Custom API compete for the same slot — all three sit under Data Warehouses. Business allows four tools and lifts the per-category limit. A workspace whose subscription has lapsed is read-only and cannot connect anything.

Permissions required

You need a MarqIQ workspace that is not read-only; MarqIQ does not ask for a particular role to connect a data source. In Snowflake you need an account administrator willing to create a user for a third party. Ask for read access only — MarqIQ never writes to your warehouse.

  • Your Snowflake account identifier, in the form the field’s placeholder shows: `xy12345.us-east-1`, the account locator followed by its region.
  • The username of the Snowflake user MarqIQ will sign in as.
  • That user’s password, or a programmatic access token for it.
  • Optionally the warehouse it should run on, for example `COMPUTE_WH`.
  • Optionally the database it should read, for example `ANALYTICS`.

Get the details from Snowflake

MarqIQ runs no sign-in flow with Snowflake. You collect the values yourself and paste them in. Snowflake’s own documentation is linked from the top of the MarqIQ page as API docs, at docs.snowflake.com

  1. Ask your Snowflake account administrator to create a user for MarqIQ.

    A dedicated user keeps this credential separate from a person’s login, so you can replace it later without changing anybody’s access.

  2. Ask for read access only on the data you want reported.

    MarqIQ issues no writes to Snowflake. Nothing in the product creates a table, a schema or a role in your warehouse.

  3. Copy the account identifier for that Snowflake account.

    MarqIQ stores this string exactly as you type it and shows it back in full on the connection, so check it against Snowflake before you save.

  4. Copy the username.

  5. Copy the password, or generate a programmatic access token for that user.

    MarqIQ accepts either in the same field. A token you can revoke on its own is the safer of the two.

  6. Note the warehouse and database names you want MarqIQ to use.

    Both are optional on the form. Leave one blank and MarqIQ stores nothing for it.

Connect it in MarqIQ

  1. Open Integrations in the sidebar.

  2. Click Add more.

    Snowflake is not on the Integrations page until you connect it, so you reach it through the marketplace.

  3. Type Snowflake into Search integrations…

    It also sits under the Data Warehouses heading, beside Google BigQuery and Custom API.

  4. Click Connect on the Snowflake card.

    The page is headed Snowflake, with an Early access pill beside the name and the panel Connect Snowflake below it.

  5. Enter your account identifier in Account Identifier.

    The field is marked required with a red asterisk, and the placeholder shows the shape MarqIQ expects.

  6. Enter the username in Username.

  7. Paste the password or the token into Password / PAT.

    The field masks what you type.

  8. Enter the warehouse name in Warehouse, or leave it blank.

  9. Enter the database name in Database, or leave it blank.

  10. Click Connect.

    The button reads Connecting… while MarqIQ checks your plan and the three required fields. It then encrypts the values you entered and saves the connection. On success the form is replaced by a Connection active card and the header gains a green Connected pill.

    MarqIQ opens no session against Snowflake at this point. A wrong password, a wrong account identifier or a warehouse that does not exist is accepted here and stays wrong until warehouse sync ships.

What the saved connection shows

The Connection active card lists Account Identifier, Username, Warehouse and Database in full so you can check them, and Password / PAT as four dots and the last four characters. There is no Connected date on this card, because nothing has synced.

MarqIQ names the connection Snowflake followed by your account identifier — Snowflake — xy12345.us-east-1 — so two Snowflake accounts are told apart in the integrations list.

What MarqIQ checks when you click Connect

  • That your plan allows Snowflake, that your tool allowance has room, and that no other Data Warehouses tool holds the per-category slot. This runs before anything you typed is read.
  • That Account Identifier, Username and Password / PAT are filled in. A value of only spaces counts as empty.
  • Nothing else. Warehouse and Database are optional, and no value is tested against Snowflake.

What comes across once it is connected

  • No rows, no tables and no columns. Snowflake has no sync engine in MarqIQ today, so nothing is pulled on a schedule or on demand.
  • No Sync button. On Data Sources, a connected Snowflake reads Mapping only · no record sync yet where the syncing tools show Sync.
  • Nothing dated. MarqIQ leaves the connection’s last-sync stamp empty rather than stamping the moment you connected, so the card cannot read "Connected · today" as though records had arrived.
  • An empty Available in Reporting panel, with the line "This source exposes fields from your queries/tables once a model is defined." Snowflake declares no fixed dimensions or metrics, unlike Google Ads or GA4.

What MarqIQ writes back to Snowflake

Nothing. MarqIQ runs no query, creates no table and changes no grant. The connection is five encrypted values in MarqIQ and no traffic to your warehouse.

What connecting Snowflake does not unlock

The nine analyses read the record store, and only a tool with a sync engine fills it. Snowflake has none, so none of them gain anything from this connection:

  • Source truth, Field discipline, Forecast accuracy, Audience health, Lead scoring, Funnel, Form fills, Email and Automations. Those read records synced by HubSpot, Salesforce, Marketo, Pipedrive, Zoho CRM, Microsoft Dynamics, Pardot, Mailchimp, Salesforce Marketing Cloud, Adobe Campaign or Adobe Journey Optimizer.
  • The Analysis, Data audit and Report templates links on a source card, which appear only once that source has records.
  • Field mapping. MarqIQ maps its tracking fields onto CRM and marketing-automation tools only, so Snowflake has no Field Mapping operation and no Create N missing button.
  • Change sets. A change set is proposed from an analysis and applied through a writer for that tool, and Snowflake has neither.

Tip

Connect Snowflake now if you want the slot held and the credentials in place for the day the sync ships. If you need findings this quarter, spend the slot on a tool MarqIQ already pulls records from and add Snowflake on Business, where four tools are allowed and two may share a category.

Disconnect Snowflake

  1. Open the Snowflake page from Integrations.

  2. Click Disconnect.

  3. Confirm the prompt that asks "Disconnect Snowflake?"

    MarqIQ erases the stored credentials straight away and marks the connection disconnected. The slot is freed, field mappings and anything already synced for other tools are untouched, and the disconnect is written to your activity log.

    The Snowflake card disappears from Data Sources rather than reading "Disconnected, data kept", because there are no records to keep.

If it did not work

"Missing required field: Account Identifier" — or several fields named at once

Why: One of the three required fields is blank, or holds only spaces. MarqIQ names every one it is missing in a single message, so "Missing required fields: Account Identifier, Username, Password / PAT" means all three are empty.

Fix: Fill the named fields and click Connect again. Warehouse and Database are never named here, because neither is required.

"Snowflake is part of the Pro plan — this workspace is on Starter."

Why: Snowflake sets Pro as its minimum plan, and the check runs before anything you typed is read, so this comes back however correct your credentials are.

Fix: Move to Pro or above. A Free Trial workspace already qualifies and needs no change. On Starter, connect Google Analytics 4 instead, which is the one analytics source that plan can add.

"Pro includes 2 tools besides Google Tag Manager, and this workspace has connected 2 (HubSpot, Google Ads). Disconnect one, or move up a plan."

Why: Your plan’s tool allowance is used up. The message lists the tools currently holding your slots, by name.

Fix: Disconnect one of the named tools, or move to Business, which allows four. Google Tag Manager, your AI engine keys and your enrichment provider keys never count against this.

"Pro allows 1 tool from this category, and Google BigQuery is already connected. Business and above allow more than one from the same category."

Why: Snowflake, Google BigQuery and Custom API all sit in Data Warehouses, and Pro allows one tool from any single category. The second of the three is refused even when you have a slot free.

Fix: Disconnect the warehouse you are not using, or move to Business, where the per-category limit is lifted.

"This workspace is read-only. Renew the subscription to connect tools."

Why: The subscription has lapsed. A read-only workspace can be looked at and cannot connect anything.

Fix: Renew the subscription from Billing, then connect again. Nothing already connected was removed.

"Unauthorized"

Why: Your MarqIQ session has expired, so the connect request arrived without one. Nothing you typed was read and nothing was saved.

Fix: Reload the page, sign in again, and enter the credentials once more. Start the form from the top.

"Could not connect", with nothing after it

Why: The request failed without a message MarqIQ could read back — usually a dropped network connection between your browser and MarqIQ, rather than anything wrong with your Snowflake details.

Fix: Click Connect again. If it repeats, reload the page and start the form from the top.

The button stays on Connecting… and never comes back

Why: MarqIQ answered with something that was not a readable reply, so the form never returned to its normal state. Nothing was saved.

Fix: Reload the page. The form comes back empty, so enter all five values again.

Snowflake says Connected and every report built on it is empty

Why: Warehouse sync is early access and not live. Connecting stores credentials; it starts no import, and there is no Sync button to press.

Fix: Nothing to fix. Build reports on a connected CRM meanwhile. MarqIQ enables your Snowflake connection on its own when warehouse sync ships, and the amber notice on the Snowflake page is the current state.

You mistyped the account identifier and want to correct it

Why: MarqIQ never tested the value against Snowflake, so a typo is stored exactly as a correct identifier would be.

Fix: Click Disconnect, confirm, then enter all five values again. There is no edit-in-place form for a stored data-source credential.

Next steps

Related articles

Was this article helpful?