What MarqIQ will never do to your data

Reading and writing are separate things

Everything MarqIQ tells you comes from reading. It pulls a copy of your records into a database that belongs to your workspace alone, and every analysis runs on that copy. None of it needs write access, except on Adobe Journey Optimizer, where a sync has to create an export in your sandbox before it can read a profile.

Writing is a second, deliberate act. A person starts every write to a record from a screen, and none runs on a schedule. The reviewed way to write is a change set. It works in HubSpot and Marketo today. There is none for any other tool yet.

The seven rules of a change set

1. A change set writes nothing a person has not seen and approved

A change set is a table: the record — shown as a masked email such as d***@acme.com — the field, what it holds now, what it would become, and one sentence saying why that record is on the list. Approval covers the whole reviewed list, after somebody has read it. A change set has no way to write without that step.

2. The safest class of change can only fill an empty field

Every change set has a class, and the class is worked out from the items rather than chosen by whoever proposed them. One replaced value moves the whole set up a class.

3. A proposal is re-checked against the live value at the moment of writing

A proposal is built from the synced copy, which is minutes or hours old. At apply time MarqIQ reads the live value of each field first.

• If the value is still what was proposed against, it is written.
• If somebody changed it since, the item is skipped and reported as left alone. It is never forced.
• If the record no longer exists in the tool, the item is skipped.
• If the field already holds the proposed value, nothing is written. The item is reported as left as it was, it is not counted as changed, and undo never touches it.

After the write MarqIQ reads each field again. An item counts as changed only when your tool said it wrote that record. Where your tool gave no answer, or accepted the write and the field does not hold the value, the item is reported as not confirmed. It is not counted as changed, and your tool may still hold what MarqIQ sent, so Put everything back reads that record again and writes the old value only where the field holds exactly what MarqIQ sent. For such a record MarqIQ cannot tell its own write from someone else putting the same value there, and the line under the button says so before anyone clicks. A record your tool refused, one MarqIQ never managed to send, and one MarqIQ cannot tell whether it wrote to are never read or written by Put everything back.

A proposal older than 14 days cannot be approved at all. The records will have moved on, so it has to be proposed again from fresh data.

4. What a change set wrote can be put back for 30 days

The Put everything back button restores the value that was there before, item by item, only on a record this change set sent a write to that may still hold it, and only where the field still holds exactly what MarqIQ sent. If the field holds anything else by then, because a colleague or one of your workflows changed it after MarqIQ did, that record is left exactly as it is and reported as Not put back: the field did not hold what MarqIQ sent. Where MarqIQ cannot tell whether it sent a record a write, it does not put that record back either: the item reads Not known, and the panel tells you to check it in your tool.

Undo needs a workspace admin, and it closes 30 days after the change was applied. After that, too much else has happened to those records for restoring an old value to be the safe thing to do.

5. An AI assistant may propose. It may never approve or apply

You can let your own AI assistant read this workspace. It can put a proposal in front of a person, and that is the end of what it can do. Approving is refused outright for a non-human actor, in the rules rather than in the screen, so there is no route around it.

One assistant operation proposes a change set. Everything else an assistant can do reads, including the one that reports where a proposal stands. An assistant cannot start any of the writes listed further down.

6. One change set changes at most 500 things

A change set holds at most 500 items. A larger one is refused at the point it is proposed, with a message telling you to propose it in parts.

A change set is also refused if two items would change the same field on the same record, or if any item would change nothing.

7. Every change set keeps a record of what it wrote

For each change set MarqIQ keeps who proposed it and whether they were a person or an assistant, who approved it, when it was applied, and for each item the value before, the value written, the result, and whatever the tool answered if it refused.

The History list under Changes MarqIQ can make for you shows the 50 most recent change sets for the tool whose page you are on, each with its state: Waiting for approval, Approved, not applied yet, Applying…, Applied, Partly applied, Not confirmed: check HubSpot (or Marketo), Not known, Nothing was applied, Nothing listed was applied, No changes listed, Put back, Nothing left to put back, Records erased from MarqIQ, Rejected, or Expired: propose again from fresh data.

The writes that are not a change set

None of these is proposed, approved or applied. Each runs when a person holding the permission starts it from a screen, and MarqIQ cannot undo any of them. Who can approve what has the detail for a permissions review.

MarqIQ deletes none of your records. From its screens, the only things it deletes in a tool are ones it made itself, and each is named under its write below.

First-touch Backfill

Under Tool Operations, in HubSpot and Marketo. It copies each most recent tracking value into its first-touch field, on up to 2,000 records a run. It fills only first-touch fields still empty in your tool, read just before writing. A refused record is skipped in the next 7 days’ runs; MarqIQ keeps its id and reason.

• Who can run it: a role holding Manage on Tool Operations. Among the built-in roles that is Workspace Admin and Marketing Ops.
• Plan: Pro and above, and the 14-day trial.
• What you see first: the number of records and the first 25 of them, with the values to be copied.
• Afterwards: MarqIQ keeps no list of the records it wrote.

Standardised or enriched values

Written onto people in HubSpot, Salesforce and Marketo from Intelligence Cloud, on up to 500 records a run. The write replaces the value that is there, and standardising a placeholder such as N/A clears the field. In HubSpot the first run also creates a property group named MarqIQ and two contact properties, Updated by and Last MarqIQ update, where your token lets it create properties. Each run then fills those two on the records it writes. A run also refreshes their descriptions, unless your team changed them.

• Who can run it: a role holding Manage on Intelligence Cloud. Among the built-in roles that is Workspace Admin and Marketing Ops.
• Plan: Enterprise and Partner. A workspace on another plan can open it once, for 7 days, on a feature trial that only a workspace admin can start.
• What you see first: standardising lists the first 300 records, each with its value at the last sync and its new value. Leave them all ticked and it writes the others too. Enrichment lists each person once, with one value now, and writes to every record that person has in these tools. A record that held a different value is replaced without being shown. The two HubSpot properties are not shown first.
• Afterwards: where they exist, the two HubSpot properties say which contacts were written, and so does MarqIQ_Last_Update__c on Salesforce where your org has created it. Nothing marks a Marketo record.

A new field for a tracking value

One field for each tracking value you ask MarqIQ to create, in HubSpot, Marketo, Mailchimp, Pardot (MCAE), Pipedrive and Zoho CRM. In HubSpot it also creates the UTM Tracking property group that holds them. In Adobe Journey Optimizer it creates one field group named MarqIQ UTM Tracking, which holds all 17 tracking fields at once.

• Who can run it: a role holding Manage on Tool Operations. Among the built-in roles that is Workspace Admin and Marketing Ops.
• Plan: any paid subscription, and Partner. The 14-day trial cannot create a field.
• What you see first: the name of the field. In Adobe Journey Optimizer, the name of the field group and the fields it will hold.
• Afterwards: MarqIQ never deletes a field. Delete it in your tool.

Fields on your forms

Added to the forms you tick, in HubSpot and Marketo, on up to 50 forms a run. Where your tool accepts the change, it is live on every page that carries the form. In Marketo MarqIQ approves the form’s draft to make it live, which also publishes any other edit waiting in that draft.

• Who can run it: a role holding Manage on Tool Operations. Among the built-in roles that is Workspace Admin and Marketing Ops.
• Plan: Pro and above, and the 14-day trial.
• What you see first: your forms and the fields to be added. You tick the forms.
• Afterwards: remove the field from the form in your tool.

The source tracking workflow

A workflow in HubSpot, or a smart campaign and its folder in Marketo. Each arrives switched off and does nothing until you switch it on in your tool. Asking MarqIQ to recreate the HubSpot workflow deletes the one it made before, and only while HubSpot shows that one still switched off and unchanged.

• Who can run it: a role holding Manage on Tool Operations. Among the built-in roles that is Workspace Admin and Marketing Ops.
• Plan: Pro and above, and the 14-day trial.
• What you see first: the rule it will build.
• Afterwards: delete it in your tool.

A template

Pushed from Template Studio into HubSpot, Marketo, Pardot (MCAE) or Salesforce Marketing Cloud. MarqIQ sends nothing. Pushing a template again replaces the one MarqIQ pushed before, so an email or page built on it can change. In HubSpot and Pardot a pushed template is live at once, and in Marketo MarqIQ approves it. Validate, for HubSpot, writes a test file there and deletes it.

• Who can run it: a role holding Manage on Template Studio. Among the built-in roles that is Workspace Admin only.
• Plan: Pro and above, and the 14-day trial. A workspace on another plan can open it once, for 7 days, on a feature trial that any member can start.
• What you see first: the template as you built it.
• Afterwards: delete it in your tool.

A draft email or landing page

Created from a template in HubSpot or Marketo. It stays a draft: MarqIQ sends no email and publishes no page.

In Marketo it also creates the folder or program you ask for to hold the draft, and removes unused blocks from the draft email it is building. A design that did not start from one of your Marketo templates gets a template of its own there: the one you pushed before, or a new one named after the draft with (MarqIQ source) added. MarqIQ approves that template, and publishing the design again replaces its content and approves it again.

• Who can run it: a role holding Manage on Template Studio. Among the built-in roles that is Workspace Admin only.
• Plan: Enterprise and Partner. A workspace on another plan can open it once, for 7 days, on a feature trial that only a workspace admin can start. The Marketo folder or program needs Template Studio: Pro and above, and the 14-day trial.
• What you see first: the email or page as you built it.
• Afterwards: delete the draft in your tool.

An image for a template

Stored in HubSpot’s file manager or Marketo’s Design Studio when you upload one in Template Studio. In HubSpot the file is public, but it is not offered to search engines. It gets a name of its own there.

In Marketo it goes into the Images folder under the file’s own name. A file already there under that name is left as it is: the image goes up with a short code from its contents added to the name, and sending the same image again uses the file already there.

• Who can run it: a role holding Edit on Template Studio. Among the built-in roles that is Workspace Admin, Marketing Ops, Agency Collaborator, Campaign Manager and Content & SEO.
• Plan: Pro and above, and the 14-day trial. A workspace on another plan can open it once, for 7 days, on a feature trial that any member can start.
• What you see first: the image you chose.
• Afterwards: delete the file in your tool.

The tracking tag in Google Tag Manager

One tag named MP Unified Tracking, created or updated in a workspace of your container. MarqIQ never publishes the container, so the tag is not live until you publish it.

• Who can run it: a role holding Manage on Tracking Script. Among the built-in roles that is Workspace Admin, Marketing Ops and Developer.
• Plan: Pro and above, and the 14-day trial.
• What you see first: the script.
• Afterwards: delete the tag in Tag Manager.

What this does not protect you from

• An approved change is a real change. MarqIQ writes what the approver agreed to.
• A connection carries the rights of whoever authorised it. If that person can edit a field in your tool, so can a change set approved in MarqIQ, and so can each write listed above. Connect as a dedicated integration user rather than as a named person who might leave.