Connect Pipedrive
You create a personal API token in Pipedrive, then paste it into MarqIQ with your company domain. MarqIQ checks both against Pipedrive before it saves anything, and shows you whose account the token belongs to. If you want to know what you are granting before you start, read How connecting a tool works.
Before you start
Permissions required
The token belongs to a person, not to an app. It carries that person's permission set and their record visibility, Pipedrive attributes whatever it does to them, and it stops working when they lose their seat. Connect with an account that can see the whole CRM — a dedicated integration user is the usual choice.
There is no read-only version of this credential
Pipedrive offers no scope picker for a personal API token. Anything its owner could change in Pipedrive, the token could change too. MarqIQ makes exactly one write with it: creating custom Person fields you click to create.
Plan required
Connecting works on every plan. Starter includes one connected tool besides Google Tag Manager and Pro two, and both allow one tool from any single category — so a Starter or Pro workspace that already has HubSpot connected is refused by name at the Connect step. Business raises the total to four and drops the category rule. Creating the UTM fields inside Pipedrive needs a paid subscription; without one the page shows Paid feature · Upgrade in place of the button, and mapping an existing field still works.
- A personal API token from app.pipedrive.com/settings/api
- Your company domain — the subdomain of your own Pipedrive address, such as `mycompany` from `mycompany.pipedrive.com`
- A Pipedrive user who can read your Person, Organization and Deal field definitions, your pipelines and your stages. Those five reads have no fallback, and a sync that is refused any one of them ends with nothing stored.
Get your API token in Pipedrive
Sign in to Pipedrive as the account whose permissions you want MarqIQ to use.
MarqIQ sees exactly what that person sees. A restricted user connects perfectly well and then syncs only their own slice of the CRM, while the sync still reports success.
Click your profile avatar.
Open Personal preferences.
Open the API tab.
Or go straight there: app.pipedrive.com/settings/api
Copy your personal API token.
Nothing renews this token and nothing needs to. MarqIQ stores it encrypted and sends it in a request header, never in a URL. It stays valid until its owner regenerates it or loses their Pipedrive seat.
Note the subdomain of your Pipedrive address.
It is the part before `.pipedrive.com` in your address bar while you are inside Pipedrive — `mycompany` from `mycompany.pipedrive.com`.
Connect it in MarqIQ
Open Connected Tools in MarqIQ and click the Pipedrive card.
The page is headed Integrations, and Pipedrive sits under the CRM heading.
Paste the token into API Token.
Type your subdomain into Company Domain.
The box shows `.pipedrive.com` beside it and removes that ending for you if you paste the whole host. MarqIQ accepts one plain label and nothing else: it strips `https://`, any path and a trailing `.pipedrive.com`, then refuses whatever is left over.
This field is not cosmetic. It becomes the address your token is sent to, which is why a mistyped value is refused rather than tried.
Click Connect Pipedrive.
MarqIQ fetches that user's own Pipedrive profile and saves nothing if Pipedrive says no. The connection then shows User, Domain and Company. Check the company is the one you meant — the page does not show that person's email address, so the name is all you have to go on.
If Pipedrive is already connected the button reads Update credentials instead. Use it to replace a token without losing your field mappings.
Leave the tab open while the first sync runs.
Connecting starts the record sync on its own. The chunk loop runs in your browser, so the status line says "keep this tab open". Close the tab and the run stops where it is; the next run, manual or scheduled, carries on from the saved cursor.
Read the result line.
A first load finishes with "Fully synced — N records", where N is how many people are now stored. Deals, activities and leads are not counted in that figure, so do not read their absence there as a failure. Later runs say "Up to date — N changes since your last sync", and that N does count every object.
Note
The very first sync in a new workspace can answer "This workspace's database was just created, so nothing was synced in this run. Run the sync again — or it starts on its own within the hour." Click Sync now again, or leave it.
What comes across
- The connected user's own profile — their name and your company name — read once at connect time to identify the account.
- People, Organizations, Deals and Activities, walked oldest-change-first so a run that stops halfway resumes where it left off. Organizations are walked first, so a person carries their company name.
- Archived deals, on a pass of their own, because Pipedrive's deal list leaves them out.
- Leads from the Leads Inbox, in full on the first run and only what changed after that. MarqIQ marks them as leads so they never inflate a pipeline figure.
- Deleted deals, and the recent-changes feed for People and Organizations, so a record deleted in Pipedrive stops counting here.
- Your field definitions for Person, Organization, Deal and Activity, plus your lead labels. This is how a 40-character field key becomes the name you gave the field, and an option id becomes its label.
- Pipelines, stages and users, so stage, pipeline and owner read as names rather than numbers — including each stage's configured probability.
- Every value on a synced record, except the Pipedrive bookkeeping MarqIQ drops: visibility, the BCC-to-Pipedrive address, profile-picture ids, instant-messaging handles and map coordinates.
- The deals timeline, for the audit's deal section and its deal-field completeness.
- A deal's or a person's change log, one record at a time, for Forecast accuracy and Field discipline.
Owners with no name
Your field definitions, pipelines and stages have no fallback: a refusal on any one of them ends the run with nothing written. Three companions in the same call fall back quietly — your list of users, your Activity field definitions and your lead labels. Where that list of users is refused, owners are stored with no name at all, so "who closes" reads as a column of ids.
Create the UTM fields in Pipedrive
MarqIQ tracks seventeen fields: nine under Most Recent UTM Fields and eight under First Touch UTM Fields. The UTM Field Validation section on the Pipedrive page shows which of them already exist as Person fields in your account.
Scroll to UTM Field Validation on the Pipedrive page.
Each group prints "N/N fields found in Pipedrive", and counts the missing ones beside it.
Click Create N missing to add every missing field in that group at once.
Click Create beside one row to add only that field.
MarqIQ creates a text field on Person named after the row — "UTM Source (First Touch)", and so on.
Click Map existing where you already keep that value in a field of your own.
A box opens on that row. Mapping writes nothing to Pipedrive.
Type the Pipedrive field key into that box.
The box shows `utm_source_c1a2b3` as its example. A Pipedrive custom field is keyed by 40 hexadecimal characters, and that key is what MarqIQ stores.
Click Save.
Click Refresh to read your Person fields again.
A green tick means MarqIQ found the field in Pipedrive; a blue tick means you mapped it by hand.
Take care
The two Create N missing buttons send one request per field and never read the answer. Where the token's owner may not add custom fields, those buttons fail quietly and the list comes back unchanged. The single Create button shows you Pipedrive's own refusal, so use it on one row to find out what is wrong.
Note
A field you map by hand is written into your tracking script on Pro and above. A Starter workspace still captures every standard UTM value; the custom field key is left out of the script it is served.
What MarqIQ writes back
- Custom Person fields — the only write in the whole Pipedrive connection. One text field per missing UTM field you click to create, never on a schedule.
- Nothing on Deal, Organization, Activity or Lead.
- MarqIQ never updates or deletes a record in Pipedrive.
What connecting Pipedrive unlocks
- Source truth — whether the field you report channels from can bear the weight.
- Field discipline and Forecast accuracy, both built from Pipedrive's per-record change log.
- Audience health, Lead scoring, Funnel and Form fills.
- The Integration Audit Report for Pipedrive, and the reports and attribution models over your synced records.
What it does not unlock
- The Email analysis and the Automations analysis. A CRM sends no marketing email, and Pipedrive exposes no reporting API for automations.
- Hidden tracking fields on your forms, the guided source-tracking setup and the source-tracking workflow. Those are HubSpot and Marketo only.
- Change sets, the one-click first-touch backfill, normalisation and enrichment. None of them lists Pipedrive, so no Pipedrive record is ever offered for writing back.
- Campaign emails, landing pages, web forms (LeadBooster) and web visits. Those sections of the audit say so rather than showing a zero.
The limits to know before you quote a number
| What | The limit |
|---|---|
| The audit's deal breakdowns | The first 2,000 deals added in the period. The deal count itself stays whole, and the screen says which it is showing. |
| Forecast accuracy | At most 2,000 deals won or lost in the last two years, spread evenly across them rather than taking the most recent, and at most 1,000 change-log entries per deal. |
| Field discipline | A sample: up to 60 people and 60 deals, spread across the account, and one request of up to 500 entries per record. A heavily edited record can lose its oldest changes. |
| Leads | At most 20,000 read per run. The run marks leads as caught up either way, so anything past that cap is not picked up next time. |
| The deletion sweep | At most 10,000 changed records per run. Its first run looks back 30 days and later runs resume from the last successful one. |
| Person fields on this page | Page after page, up to 40 pages, rather than the first page alone. Pipedrive serves 100 per page, and an account past that first page used to have its UTM fields reported missing and offered again as duplicates. |
Each figure is what the code reads, not a guideline.
Leads are not deals
A Pipedrive lead is never recorded as lost. Archiving a lead means it was set aside, not lost, so it stays open in the store and is kept out of deal analyses. Pipedrive also has no forecast category and marks no stage as closed, so Forecast accuracy judges the stage ladder and close-date slippage only.
If it did not work
"Company domain must be the subdomain of your Pipedrive URL, like "mycompany" from mycompany.pipedrive.com."
Why: What you pasted is not one plain label after MarqIQ strips `https://`, any path and a trailing `.pipedrive.com`. A full address with a path, or a value holding a slash or a dot, is refused before anything leaves MarqIQ.
Fix: Type only the subdomain — `mycompany` — into Company Domain, and click Connect Pipedrive again.
"API token is invalid. Check your Pipedrive personal API token."
Why: Pipedrive answered 401 or 403 to the profile call MarqIQ makes to verify the token. The token is wrong, has been regenerated, or its owner no longer has a Pipedrive seat.
Fix: Copy the token again from app.pipedrive.com/settings/api, paste it into API Token, and connect again. If the person has left, use an account nobody is going to deactivate.
"Could not reach yourdomain.pipedrive.com. Verify your company domain."
Why: The request never got an answer from that host, so the domain is almost certainly not yours.
Fix: Check the subdomain against your own address bar inside Pipedrive, correct Company Domain, and connect again.
"Could not connect to Pipedrive (yourdomain.pipedrive.com). Verify your company domain and token."
Why: Pipedrive answered, and refused for a reason other than the token — a valid host that is not your account, for instance.
Fix: Check both fields together rather than only the one you changed last, then connect again.
"API token is required" or "Company domain is required"
Why: One of the two boxes reached MarqIQ empty or holding only spaces.
Fix: Fill in both API Token and Company Domain, and click Connect Pipedrive.
Connect is refused and the message names your plan and counts your connected tools
Why: Your plan's total is enforced at the Connect step, not only in the picker. Starter includes one tool besides Google Tag Manager, Pro two and Business four, and the message lists the tools already using them.
Fix: Disconnect the tool the message names, or move up a plan. Reconnecting a tool you already have is always allowed, so a workspace at its limit can still rotate this token.
Connect is refused and the message names a tool from this category
Why: Starter and Pro allow one tool from any single category, and Pipedrive is a CRM. A workspace holding HubSpot, Salesforce, Zoho or Dynamics is refused here even with a tool slot free.
Fix: Disconnect the CRM the message names, or move to Business, which allows more than one from the same category.
"This workspace is read-only. Renew the subscription to connect tools."
Why: The subscription has expired. A read-only workspace connects nothing, and this refusal comes before any check on your token.
Fix: Renew the subscription, then connect Pipedrive. Your tracking script is paused for the same reason, so renewing fixes both.
"Pipedrive rejected the API token — reconnect the integration."
Why: This is what MarqIQ says for every 401 and 403 from Pipedrive, not only for a bad token. With nothing synced at all, the likeliest cause is a user who cannot read your field definitions, pipelines or stages. With some records already in, it is the visibility of whichever object the run stopped on — people, organizations, deals, activities or leads.
Fix: Connect with an account that can see the whole CRM, then click Sync now. Where the sync stopped part-way, nothing is lost: each object keeps its own resume point.
"Creating fields in Pipedrive is a paid feature — upgrade to create them, or map an existing field."
Why: Creating fields inside your tool needs an active subscription, and this workspace has none. The rule is enforced on the request itself, so it applies even where the button is visible.
Fix: Upgrade, or create the field in Pipedrive under Person yourself and point MarqIQ at it with Map existing.
The two Create N missing buttons run and the list is unchanged
Why: Those buttons send one request per field and never read the answer, so a refusal from Pipedrive is not shown. Adding a custom field is an admin right in Pipedrive.
Fix: Click Create on a single row instead. That one shows Pipedrive's own refusal, which names what the account may not do.
"Pipedrive credentials could not be read — reconnect the integration." or "Missing Pipedrive API token or company domain — reconnect the integration."
Why: The stored credentials cannot be decrypted or are incomplete, so MarqIQ has nothing to send.
Fix: Paste the token and the company domain again, and click Update credentials.
"Another sync is already running for this workspace — it will finish on its own."
Why: The scheduled run holds this workspace. Only one sync per tool runs at a time, by design.
Fix: Nothing. Your records are being refreshed right now, which is why the message is shown in green rather than red.
The audit says "Deals could not be pulled"
Why: The deals timeline is a different request from the deal list and fails on its own. The same sentence covers the stage, pipeline, deal-field and user reads that section makes alongside it.
Fix: Read the rest of the message — it quotes Pipedrive back to you — then reconnect with an account that can read your deals and your pipelines.
The sync reports success but your numbers are short
Why: A restricted user is the quiet case: the token is accepted, the run finishes, and MarqIQ stores only the records its owner can see. The number on screen is how many people were stored, so it looks complete.
Fix: Compare the count against your own Pipedrive filters. Where they disagree, reconnect with an account that can see the whole CRM and click Sync now.
Next steps
Related articles
Was this article helpful?