What MarqIQ does

The short answer

MarqIQ is all three. It connects to your tools, reads your records, reports what is wrong, and proposes fixes that a workspace admin approves before they are written.

It is not a place your team works every day. You open it when a number looks wrong, when you are about to report to a board, or when you want to know whether your data will hold up.

The tools it connects to

You connect a tool once, with its own sign-in. MarqIQ then pulls a copy of your records into a database that belongs to your workspace alone. Fourteen tools are live today.

Seven more sit on the Browse all tools page with Early access at the front of their description: Google Ads, Meta Ads, LinkedIn Ads, Google Analytics 4, Snowflake, Google BigQuery and Custom API.

How it reads your fields

MarqIQ does not work from a fixed list of field names. It reads whatever fields you have on an object, including every custom one. It then works out from the values what each field is: a lead source, a stage, a score, an owner, a first touch, a close date.

That is why Source__c, sfdc_lead_src, Acquisition Channel and lead_source all land in the same place, whatever you happened to call yours. Each finding names the exact count, the number of records it was measured on, example values, and how to reproduce it by filtering your own tool.

The nine analyses

Each one asks a question a sales or marketing leader already asks, and answers it from your records. An analysis your tool cannot feed is not offered for that tool.

The nine analyses are on Pro, Business and Enterprise, and on the 14-day trial. On Starter, the Integration Audit Report covers one connected tool instead.

A tenth tab, Overview, sits at the top of that list. It reports on the other nine and has no findings of its own. Under Start here it ranks what they found by how much harm each is doing now, and labels every item Doing harm now, Costing you results or Worth a look.

Where you read all that: Insights, and Home

Insights, in the left-hand menu, reads one connected tool five ways, and a switcher along the top of every view picks the tool: the Executive Read (one tool’s deals as the page a board asks for), the Data Audit (the condition of its records), the Analysis (the analyses above), the Suggested Plan (a quarter plan built from what they found) and Field Intelligence (every field on every object, how full it is and what it holds).

Home opens on Needs attention: the top five things the Suggested Plans of your connected tools say need doing, ranked the one way the Monday Brief ranks its three things, each with its figures, its tool and one link to the evidence. Home reads only what a plan already found; it never builds one.

Agents: the read, sent to you

An agent is a report that runs on the schedule you set — or any time with Run now — and reaches the people you name by email, in Agents › Inbox and, once Slack is connected, in Slack. Three are built. The Monday Brief: what was created, won and lost last week, what moved, how the quarter is pacing against the target, the risks, and three grounded things to do. Alerts on history: a daily check of the figures MarqIQ keeps, with one message when a rule fires — new MQLs down a third week, people with no owner up by half, open pipeline down by a third, no deal won for two weeks, duplicate groups up by half, a sync that stopped — and nothing on a quiet day. The Pipeline Inspector: the open deals that need a look — past their close date, no next step, a stage gone backwards, a close date pushed, an amount cut — per rep, with a table for managers and each rep’s own list sent only to them.

Agents read a history MarqIQ keeps for twelve months: the change log of your synced records (stage, lifecycle, owner, amount, close date) and each tool’s headline figures once a day, with each month’s last figure kept beyond that. Ask does not read that history yet; the agents do. Slack is a channel too: an admin connects the MarqIQ Slack app under Agents, an agent posts its shared sections to one public channel, and each recipient can get their own copy as a DM (see Send agent reports to Slack).

How it proposes a fix

A finding tells you what is wrong. A change set is how MarqIQ offers to put it right: a list of records, the field, what it holds now, and what it would become, with a sentence saying why each record is on the list.

A change set writes nothing until a workspace admin has read that list, approved it and applied it. The safest class of change can only fill an empty field. What a change set wrote can be put back for 30 days, on any record nobody has edited since. Read What MarqIQ will never do to your data for the full set of rules, and for the writes that are not change sets.

Change sets work in HubSpot and Marketo today. For any other tool that has a Tool Operations page, that page says there is none yet, rather than leaving you to find out.

Recording where visitors came from

A tracking script on your site records how somebody first arrived, and keeps that first touch through the whole buying cycle. The durable copy sits on MarqIQ servers, because Safari caps a cookie written by a script at seven days. A person’s first touch is learned once and never changes.

Hidden fields on your forms carry the first touch and the most recent touch into your own tool when somebody fills anything in. That is what stops a campaign lead arriving as Direct.

Reporting on revenue

Prebuilt reports split credit across four models: First Touch, Last Touch, Linear and Time Decay. You can also build your own reports, pivot any connected source, and put the result on a dashboard for your leadership team.

Every money figure prints the number of records it rests on, so you can defend a headline when your finance team asks where it came from.

Checking whether AI assistants name you

AI Answer Visibility asks the questions your buyers ask and measures whether your name comes up, across ChatGPT, Gemini, Perplexity and Claude. It also shows which domains the engines cite, so you can see which pages they are drawing their answers from. This is on the Business plan and above.

What MarqIQ is not

• It is not a CRM. It never becomes the place your records live.
• It does not send marketing email. It reads the results of the email your own tool sent. The only email it sends your team is an agent’s report, from a no-reply address with a one-click unsubscribe.
• It does not buy or run ads.
• It does not change a record in your tools on its own. A person starts every write to a record, and a change set is approved by a workspace admin first.
• It is not a consent tool. Turn on Wait for consent before sending anything to MarqIQ on the Tracking Script page and the script stores nothing until your banner reports a decision. That setting is off until you turn it on. Global Privacy Control and Do Not Track are honoured either way.