Propose a change
Proposing builds the exact list of changes MarqIQ would make and puts it in front of a person. It writes nothing to your tool, so you can propose a set to see the size of the problem and then reject it. Read How a change set works: propose, approve, apply, undo first if you have not approved one before.
Before you start
Connect HubSpot or Marketo and let its first sync finish. MarqIQ builds the proposal from its synced copy of your records, so a tool that has never synced has nothing to propose against.
Permissions required
You need a role that holds Manage on Tool Operations to propose a change. Of the ten built-in roles, Workspace Admin and Marketing Ops hold it. Anyone else is refused by the server: Proposing or rejecting a change set needs the “manage” permission on Tool Operations, which your role does not have. Approving and applying are a Workspace Admin’s, so agree who will do that before you build a large set.
Tip
Map your first-touch fields under Tool Operations › Field Mapping first. Where a field is not mapped, MarqIQ proposes against its own default field name, and your tool refuses every item on that field because no such field exists there.
Build the proposal
Open Tool Operations in the sidebar.
The page is headed Marketing Tool Operations. It lists one card per connected tool that has operations, each with a Connected badge and the number of live operations on it. A connected tool with no operations does not appear at all.
Click the tool you want to change.
Pick HubSpot or Marketo. Any other tool listed there shows Change sets work in HubSpot and Marketo today. There is none for [your tool] yet. where the operations would be.
Scroll to Changes MarqIQ can make for you.
Choose the operation.
There are two, and each card says what it does and why.
- Fill empty first-touch fields from what MarqIQ captured writes the values MarqIQ recorded when that person first arrived on your site. This is the strongest evidence there is, so run it first. MarqIQ matches a person to what it captured by email address, and reads your oldest 50,000 recorded form fills: a person with no email address in your tool is never matched, and neither is anyone whose first form fill came after those 50,000.
- Fill empty first-touch fields from the most recent touch copies the most-recent values across for people whose first-touch fields are empty. It is weaker evidence, and it only chooses a person whose first-touch medium is empty and whose most-recent medium holds a value.
Click Show me what would change.
The button reads Working it out… while MarqIQ compares its synced copy of every person in that tool against what it captured. Nothing is written to your tool at any point.
Read the summary line at the top of the panel that opens.
It states how many empty fields would be filled, on how many people, then No existing value is touched., then how far MarqIQ read to build it: Read all 330 contacts. when it read every record, or Read the first 40,000 of 3,000,000 contacts; 500 are in this change set. when it stopped at the cap, with Propose again after this one is applied for the next ones.
Read How safe it is.
Both operations fill empty fields only, so this reads Fills empty fields only. It cannot replace a value, and it can be undone.
Check the table, row by row.
Six columns: Person, Field, Now, Would become, Why and Result. The Why column gives the one-sentence reason that record was chosen — for a captured first touch it quotes the value MarqIQ recorded.
The first 25 rows are shown. Click Show all 340 (or whatever your count is) to see the rest, and Show fewer to collapse it again.
Leave the set for a Workspace Admin to approve.
It now appears under History with the amber label Waiting for approval, alongside the number of changes, your name and the date.
Note
The Person column shows a masked email such as d**@acme.com. It is enough to recognise the person and check the Why* line against what you know, and not enough to copy the list out.
What to do before you propose a large one
A proposal is safe to build. What follows it is a write into production, so do these three things once, before the first big set.
- Check what your own automation listens to on the first-touch fields. A workflow that fires on a field change fires on these writes, and undo does not reverse it.
- Propose once and read the Why column on twenty rows you know well. If the reasons do not match what you remember about those people, stop and check your field mapping.
- Agree with the Workspace Admin who approves, so a proposal does not sit for 14 days and expire.
Take care
A proposal expires 14 days after it was made and cannot be approved after that. MarqIQ labels it Expired: propose again from fresh data. This is deliberate. The records will have moved on, so the set is rebuilt rather than applied stale.
The limits
- One change set holds at most 500 changes. MarqIQ cuts the list at a record boundary, so nobody gets half their fields filled, and the summary says how far it read.
- MarqIQ reads your records in order, 2,000 at a time, and stops when the set is full or at 100,000 records. The summary says which. Propose the same operation again once the first set has been applied, and MarqIQ builds the next 500 from what is still empty. When a proposal stopped at 100,000 records, the next one carries on from there, so a large tool is covered over several proposals.
- A field of a record that an open set already lists is left out of a new proposal, whichever operation proposed it. So you can propose the same operation again while the first set waits, and get the next records; the same record is never proposed twice.
- A workspace may hold 20 open change sets at once, and may make 20 proposals a minute. Both limits meet an AI assistant’s token too.
- The captured-first-touch operation matches on email address, reading the recorded form fills for the 2,000 people of each page as it goes. Someone whose first visit was recorded under a different address from the one your tool holds gets nothing from it; run the most-recent-touch operation afterwards for whoever is left.
If it did not work
The message reads 20 change sets are already open in this workspace, the most that can be open at once.
Why: A workspace may hold 20 open change sets at once: proposed, approved or applying. Expired ones do not count.
Fix: Open History, and approve or reject some of the waiting sets, or apply the approved ones. Then propose again.
A green message reads Nothing to change and no panel opens
Why: No person in that tool has an empty first-touch field that this operation could fill. MarqIQ shows it in green, because it is the good outcome.
Fix: Nothing to do for that operation. If you expected changes, run the other operation, and check under Tool Operations › Field Mapping that your first-touch fields point at the right properties.
The Show me what would change button is greyed out
Why: The tool is not connected. An amber bar above the cards reads [your tool] isn’t connected — operations need an active connection.
Fix: Click Connect → in that bar, reconnect the tool, and let a sync finish before you propose.
A red message says change sets are part of a higher plan
Why: Change sets need the Tool Operations entitlement, which is on Pro, Business, Enterprise and the Free Trial. A Starter workspace does not have it, and Tool Operations is not in its sidebar.
Fix: Upgrade the workspace, or ask whoever owns billing to. The message names your current plan and the cheapest plan that includes change sets.
A message says change sets are being set up for this workspace
Why: A brand-new workspace gets its change-set storage on a schedule rather than the moment you sign up, and the same happens briefly after a release that adds a table.
Fix: Wait. MarqIQ prepares each workspace in turn, on the hour, so this can take a few hours. Nothing is needed from you, and the rest of the product works in the meantime.
Every row in Would become looks wrong for the person in that row
Why: The first-touch fields are mapped to the wrong properties, so MarqIQ is reading and proposing against fields that hold something else.
Fix: Reject the set. Open Tool Operations › Field Mapping, correct the mapping, and propose again.
A red message reads This workspace has proposed 20 change sets in the last minute, the most it may in one.
Why: A workspace may make 20 proposals a minute, whatever became of them since. The limit is the same for a person on this screen and for an AI assistant’s token.
Fix: Wait a minute and click the button again. Nothing was saved by the refused attempt.
Next steps
Related articles
Was this article helpful?