Run an integration audit report
The Integration Audit Report is one printable page per connected tool: how healthy the connection is, how full every field is, what your data quality looks like, and what activity the tool reports over a period you pick. Sections a tool cannot serve say why, in one sentence, instead of showing a zero. If you want the deal-by-deal read for a board rather than the connection health, read Read the Executive Read for a connected tool instead.
Before you start
- One of the eleven tools above, connected and showing as Connected.
- One finished sync. Field completeness and data quality read MarqIQ’s synced copy, so with nothing synced those sections say so.
- Nothing else. The report is read-only and writes nothing back to your tool.
Note
The report opens on the first connected tool it finds and runs by itself, so you rarely have to press anything to see it.
Run the report
Open Insights in the left-hand menu, then Health report (printable).
The page is headed Integration Audit Report. The address is /audit, and adding ?tool=hubspot opens it straight on that tool; Printable health report on a tool’s Data Audit opens it the same way.
Choose the tool along the top.
Only connected tools appear. With none connected the page says so and names HubSpot, Marketo and Salesforce as the place to start.
Pick a period.
The pills are Last 30 days, Last 90 days, This quarter, Last quarter, This year and Last 12 months, and a Custom pill opens a from and a to date beside them. There is no All time here, because the live calls to your tool have to be bounded.
The period rides in the address bar, so a link you paste to a colleague opens on the same period.
Wait for the live pulls.
A few seconds is normal. The report fans out to a dozen endpoints at once and has 60 seconds in total; a section that does not answer reports why rather than failing the page.
Click Re-pull after you change something in the tool.
Changing the tool or the period re-runs it on its own, so Re-pull is for the case where neither changed.
Click Print / Save PDF to hand it over.
It opens your browser’s print dialogue. Every section prints, including the ones that say why they are empty.
Take care
A custom range longer than 400 days is refused before anything is pulled, with the message “Live provider figures cover up to 400 days at a time — pick a shorter range.” Run two reports rather than one.
What follows the period, and what does not
This catches people out, so the page states it above the report: emails, pages, forms, visits and deals created in the period follow the period. Field completeness, data quality and field intelligence describe the whole synced store, whatever period you pick.
That is deliberate. A fill rate for “the last 30 days” would describe 30 days of records and be read as a description of the database. The store is what you are reporting on, so the store is what those sections measure.
Read it section by section
The health strip
One line across the top: the tool, the period, Connected, Last sync, Synced records and Field mappings. Where a mapping points at a field that no longer exists in the tool, the count of those is added in amber. The right-hand end says when this report was pulled.
The six tiles
Emails sent, Form submissions, Page visits, Deals created, Active automations and Landing pages. Each is counted inside the period. A tile a tool cannot serve shows a dash and the words “not available”, and hovering it gives the reason. A dash is never a zero.
A tool can also give part of a section and not the rest — the views of your landing pages but not the list of them, or the recent deals but not their totals. The part it gave is shown, a dash stands for the part it did not, and the line under the card says what came back. A count that begins “at least” is of a list the tool stopped answering part-way through: what is shown is the part that was read.
Data quality basics
Three counts: Duplicate emails, Missing email and Records checked. These are exact counts over the whole contact table for that tool, not a sample, and Records checked is the number they were counted on. Duplicates count the extra records sharing an address, so three records on one address count as two duplicates.
Note
Deleted records are excluded before anything is counted. A report that grades records nobody has any more grades nothing.
Field completeness
A meter per field, for the identity fields that matter on your tool, with the fill rate and the filled count beside each. View all N fields opens every property MarqIQ has seen on those records, with its API key, sorted by how often it is filled, and a CSV button beside the search box.
- The scan reads every synced contact in batches of 1,000, counting as it goes. Nothing is sampled.
- The scan has a 40-second budget. If it runs out, the report says “Field completeness covers the first N of M records”, and the data-quality counts above are still whole-table.
- The full field list shows the 400 most-filled properties. Past that the toggle reads View all 400 fields (capped), a report note gives how many exist, and the fill rates themselves still cover every scanned record.
- A field held under an alternative key counts as filled. A portal that keeps numbers in Mobile Phone and never in Phone is filled, not empty.
- The right-hand corner of the card states the denominator: either “N records” or “sample of N / M”.
On HubSpot, Pipedrive, Zoho CRM, Dynamics 365 and Pardot a second completeness card appears for deals, headed Field completeness — Deals (created in period), or Field completeness — Deals (added in period) on Pipedrive, which uses its own word. That one does follow the period, and its own denominator is printed beside it. Salesforce has no deal completeness card: its opportunity figures come back as totals rather than as rows that can be profiled.
Email sends, landing pages, form submissions and page visits
These are pulled live from the tool for the period you picked. The email funnel counts recipients, not sends, and the line above it gives the number of emails so the two are never confused. Bounces and unsubscribes sit under the funnel with their own rates.
Deal creation
How many deals were created in the period, their total value, a bar per stage and the most recent ones. The stage names are the labels your pipeline uses, resolved from the ids the API returns.
| Figure | Measured on |
|---|---|
| Created | Every deal created in the period, as the tool counts them |
| Pipeline value | The total amount on the deals that were read, which can be fewer than Created — see the note below. On Salesforce it is the summed amount of every deal created in the period. It is printed in the currency your tool records on those deals. Where they are in more than one currency, the card lists each currency’s value with its deal count and adds nothing across them. Where no currency is recorded, and on Salesforce, it is a plain number with no symbol, in your tool’s own currency |
| The stage bars | The deals that were read. On Salesforce, every deal created in the period |
| Recent deals | The eight newest on screen, each amount in that deal’s own currency. The CSV button beside the card heading carries fifteen, with a Currency column |
Read the deal note before you quote the value
How many deals the breakdowns read differs by tool. On HubSpot it is the 200 most recent created in the period, pulled live. On Pipedrive it is the first 2,000 of those the deals timeline returns. On Zoho CRM, Dynamics 365 and Pardot it is the 5,000 most recent in the synced store. On Salesforce nothing is capped: the stage counts and the total value come back as one grouped query over every opportunity created in the period. Where a cap bit, a report note says so and gives both numbers, and the Created count is the full count either way.
Automations
Active against inactive, and the ten busiest by name, status, Processed and Updated. The sub-label under Processed says what that tool counts — the tools do not all count the same thing. A CSV button carries the full list. For the judged read of what is broken or reaching nobody, use the Automations analysis rather than this card.
Report notes
The grey block at the foot holds every caveat the report generated: a scan that hit its budget, a capped field list, a capped deal read, a provenance read that failed, an object with nothing synced. It is always shown, never behind a toggle, so a capped number cannot be read as a whole one.
Which sections are blank on which tools
A blank section always means the tool does not expose that data through its API. It never means the number is zero, and the section says which.
| Tool | What the live pulls give | What is absent, and why |
|---|---|---|
| HubSpot | Emails, landing pages, forms, visits, deals and workflows | Nothing |
| Marketo | Emails, landing pages, forms, visits and smart campaigns | Deals. Marketo has no opportunities of its own |
| Salesforce | Deals and flows from the live org | Marketing activity: Salesforce core sends no marketing email and hosts no pages |
| Pipedrive | Deals from the synced store | Email campaign analytics live in Pipedrive Campaigns, which has no reporting API. LeadBooster web-form submissions are not exposed either — the leads they create are counted in the deal store. Landing pages, visits and automations are not exposed |
| Zoho CRM | Deals from the synced store | Email, landing pages and visits live in Zoho Campaigns, Zoho LandingPage and Zoho SalesIQ or PageSense, each a separate product with its own API. Web form submissions are recorded as lead creations. Workflow rules are not listed by the CRM API |
| Dynamics 365 | Opportunities from the synced store | Email, marketing pages, forms and visits belong to Customer Insights – Journeys. Power Automate flows and classic workflows are managed in Power Apps and are not in the Sales Web API |
| Pardot (MCAE) | Opportunities from the synced store | Email, landing page, form and visitor statistics are not exposed by the Account Engagement v5 API in a form that can be totalled for a period. Engagement Studio programs are not listed |
| Mailchimp | Campaign reports, landing pages and automations | Signup-form submissions appear only as new audience members and are counted in the synced audience. No web visits. No deals |
| Marketing Cloud | Sends and journeys | No deals |
| Adobe Campaign | Nothing live | The Adobe Campaign Standard REST API covers profiles and services only. Delivery statistics, landing pages, forms, visits and workflows all say so and point you to Campaign’s own reports. Profile completeness and data quality still come from the synced store |
| Adobe Journey Optimizer | Nothing live | The same shape as Adobe Campaign: profile completeness and data quality from the synced store, activity sections unavailable |
The other two tabs
Above the report sit Field Intelligence and Suggested Plan.
- Field Intelligence profiles each of the tool’s own objects separately — Leads apart from Contacts on Salesforce, Persons, Leads, Deals and Organizations on Pipedrive — and lets you change which field MarqIQ reads for each role. A red dot on the tab means a critical finding is waiting.
- Suggested Plan ranks what to do about all of it. Every tool the picker offers has a CRM audit behind it, so the tab opens; on Starter it opens and reports that the plan is part of Pro. A tool with no CRM audit greys the tab out and gives that as the reason on hover.
- Each tab prints on its own. Switch to the one you want before clicking Print / Save PDF.
Re-run it to show progress
The report is the same arithmetic every time, so two runs a quarter apart are comparable as long as you keep two things fixed.
Keep the period the same length.
Compare Last 90 days against Last 90 days, not against Year to date. The activity tiles are counts inside the period, so a longer period is a bigger number rather than a better one.
Quote the field fill rates with their denominator.
Those describe the whole store, which grows between runs. “Lead Source is filled on 71% of 48,310 contacts” compares cleanly against the same sentence next quarter; “71%” on its own does not.
Save each run as a PDF and keep it.
Nothing stores past runs for you. The PDF is the record.
If it did not work
“No auditable tool is connected yet”
Why: No tool with an audit provider is showing as Connected.
Fix: Connect one of the eleven tools listed at the top of this article, then come back. A tool whose token has expired shows as something other than connected and will not appear in the picker.
“Audit reports are not yet available for …”
Why: The address carries a tool slug with no audit provider behind it.
Fix: Open /audit with no tool in the address and pick from the buttons instead.
“Live provider figures cover up to 400 days at a time — pick a shorter range”
Why: The custom range you chose is longer than 400 days. It is refused before anything is pulled, rather than after a failed call.
Fix: Shorten the range, or run Last 12 months and a second report for the earlier period.
Every activity section says the credentials could not be read
Why: The stored credentials for that tool no longer decrypt or no longer work, usually after a password change or a revoked app.
Fix: Reconnect the tool from Data sources. The synced-data sections — health, field completeness and data quality — are unaffected and still fill in the meantime.
A note says field completeness covers only the first N records
Why: The scan reached its 40-second budget before it finished the table. It stops and says how far it got rather than presenting a partial number as the whole.
Fix: Read the fill rates as describing those N records, which the card’s corner also states. The duplicate and missing-email counts in Data quality basics are whole-table either way.
Field completeness says no synced records yet
Why: Nothing has synced for this tool, so there is nothing to measure fill against.
Fix: Run a sync from Data sources and re-run the report when it finishes.
“Suggested Plan is part of the Pro plan — your workspace is on Starter”
Why: The plan is a Pro feature. The report itself, its field completeness and its data quality are on Starter; the ranked plan is not.
Fix: Read the report and the Field Intelligence tab, which both work on Starter, or move the workspace to Pro or above.
The Suggested Plan tab is greyed out and will not open
Why: The tool has no CRM audit behind it. This is separate from the plan check above.
Fix: Hover the tab to read the reason, and run the plan on a tool whose data audit MarqIQ builds.
The printed PDF is missing a section you can see on screen
Why: Only the tab you are on prints. The picker, the period control and the Re-pull button are hidden on purpose.
Fix: Switch to the tab you want, then print. Print each tab separately if you need all three.
Next steps
Related articles
Was this article helpful?