Disconnect a tool
Disconnecting deletes the credential MarqIQ holds and stops syncing, while keeping the records already pulled in and every field mapping you set up. It frees the tool slot on your plan, so it is also how you make room for a different tool. If the connection has lapsed rather than being one you want gone, reconnect instead — you do not need to disconnect first, and you should not.
Before you start
Take care
Disconnecting inside MarqIQ does not revoke anything inside your own tool. The credential is deleted here, and the private app, API token, Self Client or app registration you created is still live where you made it. Remove it there as well if the point is to revoke access.
Note
AI engine keys and enrichment provider keys are not disconnected from here. Asking to disconnect one answers "This connection is managed on its own settings page", because each has its own screen with its own admin check.
Disconnect from the tool list
Open Connected Tools in the sidebar.
The page itself is headed Integrations.
Find the tool’s card.
A connected card carries a green Connected pill, and Disconnect sits beside Sync at the bottom right of it.
Click Disconnect.
Read the confirmation and click OK.
It spells out all three consequences before anything happens: the stored credentials are deleted immediately and syncing stops, already-synced data and your field mappings are kept, and you can reconnect at any time and pick up where you left off.
The button reads Disconnecting… while it works, then the page refreshes and the card loses its green pill.
Tip
Every tool also carries the same Disconnect button on its own page, at the top right. On an early-access data source it sits inside the Connection active card instead. All three run the same disconnect.
What happens the moment you confirm
| What | What happens |
|---|---|
| The stored credential | Deleted from MarqIQ’s database straight away. Nothing is kept to be restored later. |
| The connection’s status | Marked disconnected, so every screen shows the same thing: the tool list, Data sources, and the sync status the dashboard reads. |
| Records already synced | Kept. They still power reports, analyses and the data audit. |
| Your field mappings | Kept, so a reconnect needs no remapping. |
| Your plan’s tool allowance | The slot is freed at once. Google Tag Manager never held one. |
| Your activity log | A line is written naming who disconnected what and when. |
Disconnecting a tool that is already disconnected answers "Already disconnected." and changes nothing.
What stops working
Everything that needs a live call to that tool stops. Everything built on records already held carries on.
- Syncing. The Sync button goes, and the scheduled run skips the tool.
- Creating fields in that tool, and writing hidden fields onto its forms.
- Reading field change history, which is what Field discipline judges — so that analysis has nothing new to read.
- Applying a change set, or any other write-back.
- Anything that resolves a name live, such as Salesforce campaign names or HubSpot owner names for values it has not already stored.
Reports and analyses built on the records already held keep working and keep showing the date they were last refreshed. On Data sources the tool stays listed with its record count and the words Disconnected, data kept, and the Analysis, Data audit and Report templates links stay open beside it.
Note
An early-access source behaves differently for one reason: it never synced anything. Its card disappears from Data sources entirely rather than reading Disconnected, data kept, because there are no records to keep.
What stays in your own tool
Everything MarqIQ created inside your tool is yours and stays exactly where it is. Disconnecting removes none of it.
- Tracking properties or custom fields MarqIQ created, in HubSpot, Marketo, Zoho CRM or Pipedrive.
- Hidden tracking fields added to your HubSpot or Marketo forms.
- The Source Tracking workflow or smart campaign, if you asked for one.
- Drafts built in Template Studio.
- The MP Unified Tracking tag in your Google Tag Manager container. Taking it out is a manual step in Tag Manager.
Take care
Hidden form fields are worth a second thought. They are what carries the source into your tool when somebody fills a form. Disconnecting stops MarqIQ reading the results; it does not stop the fields being filled, and removing them by hand stops the capture.
Reconnecting later
Open the tool’s page from Integrations.
Paste the new credential into the same fields you used before.
Click Connect.
MarqIQ checks the credential against your tool before it saves anything, and checks your plan’s allowance first of all. Reconnecting a tool you already have is always allowed, so a workspace at its limit can still replace a credential.
Click Sync now.
The run carries on from the position saved before you disconnected rather than reading your whole store again. Your field mappings are still there.
Removing the records that tool brought in
Disconnecting deliberately keeps them. There is no button that deletes one tool’s synced records, and asking support to remove them is how it is done today.
One deletion path does exist, and it is a data-subject erasure rather than a tool cleanup. A workspace admin can erase one person by email address, which deletes that person’s form submissions and every synced CRM record carrying that address across every source in the workspace. The erasure is written to your activity log with the counts it deleted, and it cannot be undone.
Note
That erasure is by person, not by tool. It cannot be pointed at "everything from Pipedrive", and it removes the record from every source at once.
If it did not work
"Could not disconnect" followed by the tool’s name
Why: The request did not reach MarqIQ, or came back with nothing readable. Nothing was changed.
Fix: Reload the page and click Disconnect again. The card still shows Connected if nothing happened.
"This connection is managed on its own settings page."
Why: You asked to disconnect an AI engine key or an enrichment provider key. Those are stored as connections but are not tools, and each has its own screen with an admin check and its own guardrails.
Fix: Remove the key from its own settings page. MarqIQ refuses to remove the last of your own AI keys while the workspace is set to use your keys only.
The tool still appears on Data sources after you disconnected it
Why: It holds records, and those records still power your reports, so the row stays on purpose.
Fix: Read the card: it says Disconnected, data kept beside the record count, and the action beside it reads Reconnect rather than Sync.
You disconnected to free a slot and the new tool is still refused
Why: The refusal is about the category rather than the count. Starter, Free Trial and Pro allow one tool from any single category, so on Free Trial and Pro a second CRM is refused even with a slot free. Starter allows one tool in total, so there is never a free slot to argue about.
Fix: Read the message — it names the tool already holding that category. Disconnect that one, or move to Business, where four tools are allowed and the per-category limit is lifted.
Syncing carried on for a minute after you disconnected
Why: A run already in flight holds its lease for up to two minutes and finishes the chunk it is on. It cannot start another, because the credential is gone.
Fix: Nothing to fix. Wait for the status line to settle and reload the page.
You disconnected but your security team can still see the credential in your tool
Why: Disconnecting deletes MarqIQ’s copy. It sends nothing to your tool, so the private app, token or app registration you created is untouched.
Fix: Delete it in your own tool as well. The table in What permissions MarqIQ asks for names what to remove, tool by tool.
Next steps
Related articles
Was this article helpful?