MarqIQ
Browse all help topics
How to9 min read

Find a field in the unified catalog

Last updated 26 September 2026Available onFree TrialProBusinessEnterprisePartnerThe same plan feature as the report builder, saved reports and dashboards. Starter does not include it: the Intelligence Studio row is absent from the sidebar, and the address itself returns an empty table. Nothing has to be connected to open the catalog: with no tools connected it still lists every field MarqIQ knows how to read, marked Available.

The Unified Field Catalog lists every field MarqIQ can report on, from every connected tool and every imported spreadsheet, in one searchable table. Use it to settle which of two similar-looking fields you actually want before you build anything, and to find out whether a field holds data at all. To use a field once you have found it, read Build a report from scratch.

Before you start

Know two things before you search: which tool you think the field lives in, and whether you want to group by it or add it up. The catalog answers both, but the search is faster when you can narrow to one source first.

Note

This catalog is the reporting one. It is not the catalog the Data Audit and the analyses read — those use the per-object field catalog each sync saves for a tool, which records picklist options and fill rates that this page does not. A field can be in one and described differently in the other, which is why a report and an analysis can name the same field in different words.

Open the catalog and read what it is telling you

  1. Open Intelligence Studio in the sidebar, under Reports & Intelligence.

  2. Click Unified field catalog.

    The tab row at the top of every Studio page calls the same page Field Catalog.

  3. Read the count box at the top left.

    It reads “N fields · M custom”. N is every field across every source listed on the page, including sources you have not connected. M is the subset MarqIQ found in your own synced records rather than shipping with.

  4. Read the row of source chips underneath.

    Each chip names a source, gives its field count, and carries a mark: a green tick for a source with records in MarqIQ, a blue plug for one that is connected but has synced nothing yet, and a grey circle for one that is neither.

Find the field

  1. Type into Search fields….

    The search matches three things, ignoring case: the field’s name as shown, its underlying key, and its object. Searching “Contact” therefore returns every contact-level field, and searching “hs_analytics” returns HubSpot’s analytics properties by key.

    It does not search the description under a field name, nor the category. A field whose only clue is in its description will not be found by typing that clue.

  2. Click a source chip to narrow to one system.

    Click it again to go back to every source. The All sources list above does the same thing.

  3. Read across the row.

    Six columns: Source System, Object, Field Name, Type, Category and Availability.

  4. Check for a CUSTOM badge beside the field name.

    A badge means the field is not one MarqIQ ships for that tool — it was found in your own records. No badge means it is a field MarqIQ knows for that tool whether or not you use it.

There is no filter by object or type

The only two controls are the search box and the source. To narrow to an object, type its name, because the search reads the Object column. The objects in use are Account, Campaign, CampaignMember, Contact, Event, Lead, Member, Opportunity, Profile, Prospect, Session, Sheet, Submission, Subscriber, Unified and User. To find every measure, there is no control at all; measures read “measure” in the Type column, so scan it.

Searching by object never finds a custom field

A field MarqIQ discovered in your own records carries no object, so its Object column reads an em dash and no object name matches it. The three time dimensions — Year, Quarter and Month — read an em dash for the same reason. Search those by name or by key.

What the three availability badges mean

BadgeWhat it meansCan you report on it today?
SyncedMarqIQ holds records for this source, and this field was found on them — or it is a count or a derived field that always works once there are recordsYes
ConnectedThe tool is connected, and this field was not on any of the 300 records the badge was measured on — see the warning belowYou can put it on a report, and every row may read (not set)
AvailableMarqIQ knows this field for this tool, and the tool is not connectedNo

What *Synced* was measured on

For each connected tool, MarqIQ works out which fields are present by reading the 300 most recently synced records of that tool and listing every property it finds on them. Three hundred records is the whole basis of the Synced badge and of the CUSTOM rows. A field filled on older records but on none of the newest 300 reads Connected, not Synced, and a custom field only your oldest records carry does not appear at all. Put the field on a report before you conclude it is empty — the report reads far more records than this page does.

Telling two fields that look alike apart

Most confusion here is two fields with nearly the same name. Four columns settle it, and you rarely need more than two of them.

  • Source System — HubSpot’s Original Source and Salesforce’s Lead Source are different tools’ answers to the same question and will not agree.
  • Object — a field on Contact and a field on Opportunity describe different records even inside one tool.
  • The CUSTOM badge — a custom field your team built usually beats the tool’s own field, or is stale beside it. Find out which before you report on it.
  • Category — Attribution & Source against Campaign against Revenue & Deals tells you what a field was meant for. Categories are assigned by name, so a field called anything unusual lands in Custom Fields whatever it holds.

Tip

The same field can be listed twice under one tool with the same label — once as MarqIQ’s own name for it and once as the raw key found in your data. Either works in a report and both read the same values. Pick one and stay with it so two reports do not look different for no reason.

How a custom field becomes a dimension or a measure

MarqIQ decides this from the values it sampled, not from the type your tool declares.

  • More than 80% of the non-empty sampled values parse as numbers, and the field did not land in the Time category: it becomes a measure, added up by default.
  • The name contains revenue, amount, value, mrr, arr, deal, price, spend or cost: the measure is formatted as currency and filed under Revenue & Deals.
  • Anything else becomes a dimension you can group by, listed as text.
  • A field lands in Time, and stays a dimension whatever its values, when its name carries date, timestamp, time or _at — and only when no earlier category claimed it. So a numeric field called close_date stays a dimension, and one called deal_date is claimed by the revenue word first and becomes a currency measure.

Take care

A field of numbers that are not quantities — an account number, a postcode, a numeric identifier — is a measure by this rule and will happily be summed into a total that means nothing. Check the Type column before you drop a field into Values.

The sources on this page that are not the usual ones

SourceWhat it isWhat to know
Marqiq AttributionYour own tracked form submissionsAlways connected. Reads Synced once one submission exists
Unified (Cross-System)One row per email address, merged across every sourceIts fields are namespaced — HubSpot Original Source, Salesforce Lead Source — and cover a fixed set, not every field of every tool. Read Compare the same people across two systems
A spreadsheetEvery imported file is its own source, named after the fileIts columns are read from the 300 most recent imported rows of that file, the same way a tool’s are
Google Analytics 4Sessions, users and eventsIts fields are listed, and MarqIQ pulls no GA4 records, so the catalog never marks them Synced and a report built on that source returns nothing

Take the field into a report

  1. Note the field’s Source System and its name exactly as the catalog spells it.

  2. Click Build a Report at the top right.

  3. Choose the same source in Data Source.

    A field only exists inside its own source. Choosing a different source will not offer it.

  4. Type the field’s name into Search fields… in the left panel.

    The builder groups fields by category, so a field you cannot see is usually inside a collapsed category rather than absent.

  5. Send it to Rows, Columns or Values.

If it did not work

A field you use every day in your tool is not listed

Why: MarqIQ lists a tool’s custom fields from the 300 most recently synced records. A field none of those records carries is not there, and a field your sync does not pull at all never will be.

Fix: Run a sync from Data sources and reload the catalog. If it is still missing, read A field is missing from MarqIQ, which covers the fields each sync pulls and the ones it does not.

A field reads Connected although you know it holds values

Why: None of the 300 most recently synced records of that tool carries it. The badge describes that sample, not your database.

Fix: Put it on a report anyway. A report reads far more records, and a column with values in it settles the question. Where the report is empty too, the field is genuinely not coming through the sync.

Searching the description text finds nothing

Why: The search reads the field name, its key and its object. Descriptions and categories are not searched.

Fix: Search the name or the key instead, or narrow to the source with a chip and scan the category column.

Two rows have the same field name under the same tool

Why: One is MarqIQ’s own name for the tool’s field and the other is the raw key found in your synced data.

Fix: Use either. They read the same values. Choose one for the whole team so two reports built from the same idea do not look different.

A text field is listed as a measure

Why: Over 80% of its sampled values parsed as numbers, so it was treated as a number.

Fix: Use it as a row dimension rather than a value. Grouping by it works; adding it up produces a total with no meaning.

The table is empty and the count box reads 0 fields · 0 custom

Why: Your workspace is on Starter. The catalog, the builder, saved reports and dashboards are one plan feature, and the refusal — “The report field catalog is part of the Pro plan — your workspace is on Starter.” — comes back to the page rather than onto it, so the table reads empty instead of explaining itself.

Fix: Read What each plan includes, then upgrade. Your role does not affect this — every signed-in person on an included plan can open the catalog, and on an included plan the table is never empty.

The page reads No fields match your filters.

Why: The search text and the chosen source have no field in common.

Fix: Clear the search box, or click the highlighted source chip again to go back to every source.

Next steps

Related articles

Was this article helpful?