Read the write log
There is no single Write log screen. What MarqIQ wrote is recorded in three different places depending on which path wrote it, and this page tells you which to open for a given question. Read it before an audit or a client report, so you know what you can produce and what you cannot. For a change that was applied and looks wrong, go straight to Undo a change MarqIQ applied.
Before you start
Know which path made the change before you go looking. MarqIQ writes values onto your records three ways, and only one of them keeps a record inside MarqIQ.
| Path | Recorded in MarqIQ | Recorded in your tool |
|---|---|---|
| A change set, under Tool Operations | Every item: record, field, before, after, reason, result, and your tool’s own message where it refused | Nothing MarqIQ adds. HubSpot’s own property history names the private app that wrote |
| Tool Operations › First-touch Backfill | Nothing per record. Only a run summary on screen, which is gone when you leave the page | Nothing MarqIQ adds |
| Writing standardised or enriched values back, on Enterprise and Partner or a 7-day feature trial, into HubSpot, Salesforce and Marketo | Nothing per record | In HubSpot, two stamp properties on the contact, and in Salesforce one stamp field where your org has created it. Each is named below. Both tools also show MarqIQ/1.0 in their API logs. In Marketo, nothing MarqIQ adds |
Take care
The gap in the middle row is real. A first-touch fill run from Tool Operations › First-touch Backfill writes up to 2,000 records with no item-by-item record anywhere. Propose the same work as a change set instead when you need to be able to answer for it afterwards.
Read what a change set wrote
Open Tool Operations in the sidebar.
Click the tool the change was made in.
Scroll to History.
It holds that tool’s 50 most recent change sets, newest first, whatever their outcome. Each line gives the title, the number of changes, who proposed it, whether that was a person or an AI assistant, the date, and the state.
Click the set you want to read.
Read the What happened line.
It counts each outcome with its own number: how many changed, how many were left as they were because they already held the value, how many were left alone because the value had moved since the proposal, how many are no longer in the tool, how many your tool refused, how many could not be confirmed, and on an undone set how many were put back.
Work down the item table.
Six columns: Person, Field, Now, Would become, Why and Result. Now is the value the field held when the set was built, Would become is what MarqIQ wrote, and Why is the one-sentence reason that record was chosen.
Click Show all 340 to see past the first 25 rows.
The button carries your own count. Show fewer collapses it again.
Copy your tool’s message from any row that reads Refused by the tool.
It is printed in red under the result, in your tool’s own words, and it is the thing to hand to whoever administers that tool.
The masked email is deliberate
The Person column shows a masked address such as d**@acme.com. It is enough to recognise the record and check the Why* line, and not enough to lift the list out of MarqIQ. To identify a record in full, open it in your tool from the address or the name you already hold.
What the change-set record holds, and what it does not
The record is per item and it is complete for the items it covers. The limits are about what the screens show, not about what MarqIQ stored.
| Question | Answer today |
|---|---|
| What was in the field before MarqIQ wrote? | On the item, in the Now column |
| What did MarqIQ write? | On the item, in the Would become column |
| Why was this record chosen? | On the item, in the Why column |
| What did the tool answer? | On the item, in the Result column, with the tool’s own message where it refused |
| Who proposed it, and when? | On the set, in the History line and at the top of the panel |
| Was it proposed by an AI assistant? | Yes — the line reads (AI assistant) after the name |
| Who approved it, and when it was applied or put back | Stored, but no screen shows it. Ask support when you need it for an audit |
| Who rejected it, and why | The person and the reason are stored; the time is not |
| Filter by operation, by person or by date | Not available. The list is the 50 most recent for that tool, in order |
| Export it | Not available. There is no download on this screen |
| Sets older than the 50 most recent for a tool | Stored, but not reachable from the screen |
Find MarqIQ’s writes inside HubSpot
Two different marks, made by two different paths. Check which path wrote before you go looking for either.
- A change set leaves no field of its own. HubSpot’s property history on the contact names the private app that made the write, which is why the connect screen asks you to name that app MarqIQ. Open the contact, hover the property, and read the change source.
- An enrichment or standardising write adds two properties in a property group called MarqIQ: Updated by, which is set to the word MarqIQ, and Last MarqIQ update, which holds a line such as “2026-08-19 17:02 UTC · Normalization: Country, Industry”. Both are ordinary contact properties, so you can filter a list on them.
- MarqIQ creates those two properties on its first such write. Where your portal refuses property creation, the write still goes through, unstamped — so an absent stamp does not prove MarqIQ did not write.
Tip
To count every record an enrichment or standardising write touched, build a HubSpot contact list filtered on Updated by is equal to MarqIQ. Put the count in the report alongside the total contacts the list was drawn from, so the figure carries its denominator.
Find MarqIQ’s writes inside Salesforce
- Salesforce always shows the connected integration user as Last Modified By on any record MarqIQ wrote to. That is the first thing to check, and it needs nothing set up.
- MarqIQ also writes a field called MarqIQ_Last_Update__c, in the same format as the HubSpot stamp, but only where your org has already created that field under Setup › Object Manager. MarqIQ deliberately does not create it for you, because field-level security and permission grants make that unreliable.
- Create the field once if you want the finer record, then every later write fills it. Writes made before it existed are not filled in afterwards.
Note
Change sets do not write to Salesforce. MarqIQ builds change sets for HubSpot and Marketo only, so anything you find in Salesforce came from an enrichment or standardising write, which is on Enterprise and Partner, or on a 7-day feature trial.
Find MarqIQ’s writes inside Marketo
MarqIQ adds no stamp field in Marketo and writes no marker of its own. A change set applied to Marketo is recorded in MarqIQ, per item. MarqIQ keeps no record of a standardised or enriched value it wrote to Marketo. In Marketo each appears as a write from the API user behind the credentials you connected. Use the change-set item table as the record, and Marketo’s own lead activity to confirm the write landed.
Answering “did we do that, or did the CRM?”
This is the question the record is really for. Work it in this order.
Open Tool Operations and click the tool the record lives in.
Sets are listed per tool, so a set applied to Marketo is not under HubSpot.
Scan History for a set whose title names that field.
The operation title names the fields it fills.
Open each candidate set in turn.
Find the record in the item table.
Rows are sorted by the person label. On a large set click Show all first.
Compare the Would become value against what the field holds now.
A match, with the item marked Changed, means MarqIQ wrote it and nothing has changed it since. A mismatch means something wrote after MarqIQ did.
Check the stamp fields next when the tool is HubSpot or Salesforce.
A stamp dated after the change set points at an enrichment or standardising write rather than a change set.
Open the field’s own history in your tool last.
HubSpot’s property history and Salesforce’s field history name every writer, including your own workflows and imports. That is what settles it when MarqIQ’s record shows nothing.
Tip
Where the answer is that one of your own automations overwrote a field, the Field discipline analysis on the Analysis tab is the screen that measures how often that happens and on how many records.
If it did not work
The set you are looking for is not in History
Why: The list holds the 50 most recent sets for that tool, and it is filtered to that tool. A set applied to Marketo does not appear under HubSpot.
Fix: Open the other tool’s page. Where the set is older than the 50 most recent, ask support: MarqIQ still holds it, but no screen reaches it.
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.
A field changed and no change set mentions the record
Why: Either MarqIQ wrote it by another path, which keeps no per-record record, or something in your tool wrote it.
Fix: Check the stamp fields on the record, then the field’s own history in your tool. Both are described above.
The Updated by and Last MarqIQ update properties do not exist in HubSpot
Why: Either no enrichment or standardising write has run in this portal, or the portal refused property creation on the first attempt and the writes went through unstamped.
Fix: Check whether your workspace can write back at all — it is on Enterprise and Partner, or on a 7-day feature trial. Where it can, check that the private app has permission to create properties, then run the write again.
MarqIQ_Last_Update__c is empty on a Salesforce record you know MarqIQ wrote to
Why: The field did not exist at the time of the write, or field-level security hides it from the connected user.
Fix: Create the field under Setup › Object Manager and grant the integration user access to it. Earlier writes are not filled in retrospectively; use Last Modified By for those.
An auditor asks for an export of every change
Why: No screen exports change sets today.
Fix: Work from the item table on screen, and ask support for the approval and apply timestamps that no screen shows. Say in the report that the figures cover the 50 most recent sets per tool, so the scope is on the page rather than assumed.
Two records show the same value but only one appears in a change set
Why: At apply time MarqIQ skips an item whose live value has moved since the proposal, and a skipped item is in the set but marked Left alone.
Fix: Read the Result column rather than the presence of the row. A change was skipped, refused, or only partly applied explains each reason.
Next steps
Related articles
Was this article helpful?