MarqIQ says my tool cannot provide this
An analysis tab drawn in grey with a dashed edge, and a card reading “Not something this tool can do.”, means exactly that: the tool does not expose what the analysis reads, and MarqIQ will not guess at it. Nothing is hidden on that screen — the tab is still there and still says why — and that is different from an analysis your tool supports but your workspace has not set up. This article tells the two apart and gives the table of what each tool can feed.
Before you start
Open Analysis. It lists one section per connected tool. Click any analysis under a tool to open that tool’s own page on its Analysis tab, where all ten analyses sit as tabs across the top. Each tab’s state is decided by that tool, not by your plan.
Two screens, two lists
The Analysis launcher lists only the analyses a tool can feed, so an analysis the tool cannot do is not offered there. The tool’s own Analysis tab shows all ten, with the ones it cannot do drawn in grey. Read the grey tabs there, not the launcher, when you want to know what a tool cannot do and why.
Three states, not two
Ready means the tool supports it and you have the data. Not set up means the tool supports it and you have not built it yet — the card stays and carries the setup steps for your tool. Not something this tool can do means the tool itself has nothing to read, said once and never dressed up as your failing.
Which analyses every tool can feed
Three read the records themselves, so any tool whose records sync will fill them: Overview, Source truth and Audience health. If one of those is empty, the cause is your data or your sync, not the tool.
Which analyses need something particular, and from which tools
| Analysis | What it has to read | Tools that expose it |
|---|---|---|
| Field discipline | A record’s change history: every value a field held, when, and what wrote it | HubSpot, Marketo Engage, Salesforce, Pipedrive, Zoho CRM, Microsoft Dynamics |
| One row of results per send, with its subject line | HubSpot, Marketo Engage, Mailchimp, Salesforce Marketing Cloud | |
| Automations | The definitions of what is switched on, in the tool’s own words | HubSpot (workflows), Marketo Engage (smart campaigns), Mailchimp (automations), Salesforce Marketing Cloud (journeys), Salesforce (flows) |
| Forecast accuracy | What a deal’s stage, forecast category and close date said before it closed | HubSpot, Salesforce, Pipedrive |
| Form fills | The tool’s own forms and their submissions | HubSpot and Marketo Engage — plus fills MarqIQ’s own tracking script captures, on any workspace |
| Lead scoring | A field on people that scores them, with values in it | Any tool, once such a field exists |
| Funnel | A stage ladder on people, or stage-entry dates | Any tool, once such a ladder exists |
Where the honest boundaries are
Pardot (MCAE), Mailchimp, Salesforce Marketing Cloud, Adobe Campaign and Adobe Journey Optimizer expose no per-field change history, so Field discipline cannot run on them. Pardot has no send-results reader because its v5 API does not total a period. Pipedrive has no Web Forms API, so its own forms cannot be read; Source truth and the tracking script’s captured fills cover the same ground, and the card says so.
The causes, by what the card says
“Not something this tool can do.” with a sentence naming change history
Why: This tool does not expose a record’s change history, so there is nothing to hold a field to. Field discipline checks whether a first-touch field is overwritten, whether a stage went backwards, whether a score was typed by hand — every one of those is a question about the past, and the past has to be readable.
Fix: Run Field discipline on the CRM in your stack rather than the marketing tool. Where the overwriting you want to catch happens in the marketing tool, the change you want is usually visible in the CRM the moment it syncs across.
The Email tab is grey on your CRM
Why: A CRM does not send marketing email, so it reports no send results.
Fix: Switch to the tool that sends your email. MarqIQ reads results from HubSpot, Marketo Engage, Mailchimp and Salesforce Marketing Cloud.
“MarqIQ cannot read this tool’s forecast fields yet”
Why: The forecast check needs a deal’s stage, forecast category and close date as they stood on earlier dates. MarqIQ reads that on HubSpot, Salesforce and Pipedrive only.
Fix: Use the Executive Read tab instead for the same book of deals. It gives win rate on closed deals, days to win, and open pipeline past its close date, none of which needs history.
“MarqIQ cannot read this tool’s own forms yet”
Why: MarqIQ reads a tool’s own forms on HubSpot and Marketo Engage. Elsewhere it cannot say which form brought somebody in, and it states that as its own limitation rather than as a gap in your setup.
Fix: Two things cover the same ground. Source truth reads the fields your records already carry about where each person came from, and fills captured by MarqIQ’s tracking script on your website appear in Form fills as soon as the script is live.
“MarqIQ has not verified how this works in this tool, so it will not guess at the setup”
Why: Lead scoring, the stage ladder, the forecast and forms each have a documented setup per tool, and MarqIQ holds that setup only for the tools it has checked. For Pardot (MCAE), Mailchimp, Marketing Cloud, Adobe Campaign and Adobe Journey Optimizer it holds none.
Fix: Read the sentence carefully: nothing there is a judgement about your data. Where the workspace does hold the data — a score field with values in it, say — the analysis runs anyway.
The card says the analysis is not set up, and gives you steps
Why: This is the second state, not the third. The tool can do it; your workspace has not built it. That is the finding, and the card carries the setup for your tool, your business and what a seasoned RevOps lead would implement.
Fix: Work through the steps on the card. Each one names the menu in your tool’s own words and ends with what you should see on a record when it is working.
“No deals are synced from this tool yet, so there is nothing to forecast”
Why: A forecast needs deals. With none synced there is no failing to report, only an absence.
Fix: Run a sync and come back. The card fills once deals arrive.
Why a whole row is missing from your sidebar instead
A page that only acts on a particular kind of tool is not offered to a workspace with none of them. The writer that puts hidden fields onto live forms speaks HubSpot and Marketo, so a Salesforce-only workspace is not shown the row — there is nothing it could do there. That rule is declared once for every sidebar row, hover-menu child and dashboard shortcut, so the three cannot disagree.
This is a different question from the plan and the role, and the article that covers all three is A page is missing from my menu, or asks me to upgrade.
State the denominator, including how much was read
Three tools give a record’s change history one record at a time — Pipedrive, Zoho CRM and Microsoft Dynamics — because each record costs its own request. On those, Field discipline reads a sample of at most 60 records rather than the whole store, and the page states that sample in its header rather than in a footnote.
What has been run against a live account, and what has not
Change history is verified on live HubSpot and Marketo accounts. Salesforce, Pipedrive, Zoho CRM and Microsoft Dynamics follow the vendors’ documented endpoints and are tested on payloads of that shape, but none has been run against a customer account. The same holds for the automations reader on Mailchimp, Marketing Cloud and Salesforce, and for the Salesforce forecast, which reads Opportunity History. Where a payload is not what MarqIQ expects, it ends as a plain sentence on the page and never as a finding.
If it did not work
A colleague on the same workspace sees a tab you do not
Why: Tab states are per tool, not per person. They are almost certainly looking at a different tool at the top of the Analysis screen.
Fix: Compare the tool name on both screens first. Where it is the same, the difference is your role or your plan, not the tool.
You connected a tool that should support the analysis and the tab is still grey
Why: The state is decided from the tools that are connected, and a connection that failed or was never finished does not count.
Fix: Open Setup & diagnostics and check the tool reads Ready rather than Failing or Not set up.
A link opened the Overview rather than the analysis you asked for
Why: The address names the analysis in its view parameter, and a name that matches none of the ten opens the Overview instead. A link to an analysis this tool cannot feed still opens that analysis, grey, with the sentence on it.
Fix: Pick the tab by hand and read the sentence on the card, which names what is missing.
Next steps
Related articles
Was this article helpful?