A field I have in my CRM is not showing in MarqIQ
MarqIQ never works from a fixed field list — it asks your tool which fields exist and reads what that tool returns for your credential. So a field you can see in your CRM and cannot see here has one of six causes, and each one is checkable in about a minute. Work down this article in order and stop at the first that matches.
Before you start
You need the tool connected and at least one sync finished, because field discovery runs as part of a sync rather than on its own.
Tip
Open Integration Audit Report under Connected Tools and click the Field Intelligence tab before you read on. It lists the fields MarqIQ holds for each of the tool’s own objects, with the percentage of records each one is filled on, so it tells you in one look whether the field arrived empty or did not arrive at all. On Pro and above the same tab sits on the tool’s page under Data sources.
First, look in the two places that list fields
These screens answer different questions, and reaching for the wrong one is the commonest reason a field looks missing when it is present.
| Screen | Where | What it lists |
|---|---|---|
| Field Intelligence | A tab on Integration Audit Report, under Connected Tools. On Pro and above, also a tab on each tool under Data sources. | Every field MarqIQ holds for that tool, split by the tool’s own objects, with how full each one is. |
| Unified field catalog | In the sidebar, under Intelligence Studio | Every field across every source, as the report builder offers them. Pro or above. |
Field Intelligence is the one to trust when you are asking whether a field arrived. Unified field catalog is the one to check when you are asking whether you can report on it.
Note
The two lists are built differently, so they can disagree. Field Intelligence starts from the field list your tool gave MarqIQ at sync time. Unified field catalog reads the 300 most recently synced people for that source and lists the keys it finds on them, on top of a registry of the well-known fields. A field filled on only a handful of old records appears in the first and not the second.
The six causes, most common first
The field is listed but reads 0% filled, or does not reach the report builder
Why: The field is empty on your records. A value that is empty is not stored against the record at all, so there is nothing for the report builder’s sample to find. This is the commonest cause by a wide margin, and it is not a sync fault — MarqIQ is reporting your tool accurately.
Fix: Open the field in your own tool and check a few records. If it is genuinely blank there, fill it in your tool and sync again. Nothing in MarqIQ can produce a value your tool does not hold.
The field is on deals, opportunities or companies, and you are looking at a people list
Why: The report builder’s field discovery reads people — contacts, leads, persons, prospects or subscribers — and nothing else. A field that only exists on a deal or a company is never in that sample.
Fix: Open Field Intelligence for that tool and change the object sub-tab to the one the field belongs to. Each of the tool’s objects is listed separately, with its own field list.
HubSpot deal and company fields are missing although contacts look right
Why: HubSpot contacts and HubSpot companies-and-deals are two separate engines. The Sync button runs the contacts engine only; companies and deals are pulled by the scheduled run.
Fix: Wait for the scheduled run to reach that workspace. It fires on the hour, and more often while a first load is still in motion. Check Field Intelligence again afterwards — the Deals and Companies sub-tabs say in as many words when nothing is synced for them yet.
The field exists in your tool and never appears for any object
Why: The credential you connected with cannot see it. MarqIQ asks your tool to describe the object and then asks for what that description returned, so a field your connected user is not allowed to read is never requested and never reported as missing.
Fix: Check the connected user’s access in your own tool, against the row for your tool in the table below, then sync again. Field discovery re-runs on every sync, so the field appears on the next run once the access is granted.
A tool with thousands of fields is missing the newest ones
Why: Each tool has a ceiling on how many fields MarqIQ asks for per object, and a portal past that ceiling loses whatever falls beyond it.
Fix: Read the ceiling for your tool in the table below. Where the ceiling is the cause, the fix is in your own tool: remove fields you no longer use, or rename the one you need so it matches the priority words that tool keeps first.
You created the field today and it is not here yet
Why: MarqIQ asks your tool for its field definitions at the start of a sync run. A field created after the last run finished is not in the list that run worked from.
Fix: Click Sync on the tool’s card and leave the tab open until the status line says it has finished. The new field is discovered at the start of that run, and records carrying a value for it land in the same run.
What each tool leaves out, and why
These are the limits in the code, tool by tool. A field that falls into one of these rows is not a fault to report — it is a boundary to work around.
| Tool | Field ceiling per object | Never requested |
|---|---|---|
| HubSpot | 3,000 contact properties. A named core list is always included, so the everyday fields cannot fall past it. | HubSpot’s own bookkeeping ids and its calculated searchable phone columns. |
| Salesforce | No count ceiling. Every field the describe returns is asked for, in batches, so an object carrying 900 fields still syncs whole. | Address, location, base64 and encrypted-string types. Anything your profile’s field-level security hides. |
| Zoho CRM | 600 fields per module. Standard columns first, then names that look like source, campaign, UTM, channel, medium, MQL, SQL, score, rating, industry, revenue, employees, status, stage, owner, region, country, segment, reason, lifecycle, program, referrer or partner, then the rest alphabetically. | Fields Zoho reports as not visible, subforms, file, image and profile-image uploads, rollup summaries, consent lookups, and lookups pointing at several records or modules at once. |
| Microsoft Dynamics | No ceiling. The walk asks for no particular columns, so every column of every record arrives. | Nothing on the four tables it reads. Only accounts, contacts, leads and opportunities are read at all. |
| Marketo | No ceiling on the full read. MarqIQ asks Marketo what it has and splits the names into request-sized groups. | Nothing on a full read. The incremental change feed names the fields it wants and that list is trimmed to fit, so an edit to a field past that point produces no change record until a full re-read reaches that person. |
| Adobe Campaign | No ceiling. Profiles are read from the extended profile resource, so your own custom attributes arrive with Adobe’s standard ones. | Subscriptions, preferred language, time zone, the CCPA opt-out flag and the profile’s own externalId column. |
Every one of these ceilings is a sanity limit rather than a budget. Where a tool is not listed, MarqIQ asks it for every field it declares.
Where a field name changes on the way in
A field can be present under a name you did not expect, which reads as missing.
- MarqIQ stores each field under the key your tool uses, and labels it with the label you gave it. A Pipedrive custom field arrives under a 40-character key and is shown under its own name.
- Lookups are flattened to a display name. A Zoho lookup arrives as the name it points at, not as an object.
- Adobe Journey Optimizer profiles arrive as flattened paths, so a nested attribute reads as `homeAddress.country` rather than as two levels.
- Marketing Cloud subscriber attributes keep their own names, and only attributes Marketing Cloud marks as retrievable are asked for.
The UTM field check is a different question
Each tool page carries a UTM field check, and it is narrower on purpose than the field lists above. It asks whether MarqIQ’s own tracking fields exist so they can be written to, not whether your fields arrived.
- On Zoho CRM it only ever looks at — and only ever creates on — the Leads module. A UTM field you keep on Contacts or Deals is reported as missing.
- On Microsoft Dynamics it only looks at single-line text columns on the Contact table. The same value in a multi-line column, in a column of another type, or on a Lead, reads as missing.
- On Pipedrive it creates Person fields only — 17 of them across the two groups — and never on a Deal, Organization, Activity or Lead.
- On Adobe Campaign it checks MarqIQ’s 17 tracking fields against your profile resource. A tenant that has never had them made shows every row crossed, which is the expected first state.
If it did not work
Field Intelligence shows the field and the report builder does not offer it
Why: The report builder reads the 300 most recently synced people for that source. A field filled only on older records is not in that sample.
Fix: Report on it through an analysis on that tool instead, which reads a sample drawn across your whole history rather than the newest records.
A Salesforce field appears on some records from one run and is blank on others
Why: Salesforce fields past the first group are fetched in extra batches per page of records. A batch that fails is stepped over for that page only, with no message on screen.
Fix: Click Sync now on the Salesforce page. The next run re-reads those records, and the upsert makes a repeat harmless.
The field arrived but its values are ids rather than names
Why: Names come from a separate read that your credential may not cover. On Salesforce, campaign names need Read on Campaign, and owner names on HubSpot need the owners scope.
Fix: Grant the missing access in your own tool and sync again. Salesforce is the one place where missing campaign names carry no message at all — raw ids beginning 701 are the only sign.
You cannot open Unified field catalog at all
Why: That screen is part of Pro and above. A Starter workspace does not see it.
Fix: Open Integration Audit Report under Connected Tools and read the Field Intelligence tab there instead. That route is on every plan.
Nothing at all is listed for the tool
Why: Either no sync has finished, or the tool has no sync engine and is connected for field mapping only.
Fix: Check the tool’s card on Data sources, which needs Pro or above. "Mapping only · no record sync yet" means MarqIQ does not pull that tool’s records, so it has no fields to list. The eleven tools listed at the top of this article are the ones that do pull records.
Next steps
Related articles
Was this article helpful?