> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/data-and-insights/marketing-integrations/zoho-crm.md).

# Zoho CRM

Connect Zoho CRM so deals that reach a stage you choose, such as Qualification, Proposal/Price Quote or Closed Won, can go to Google Ads as offline conversions.

Connect Zoho CRM so AdPage can see the deals your sales team works on outside the website. With **Offline conversions** on **Data boosts**, a deal that reaches a stage you choose (*Qualification*, *Proposal/Price Quote* or *Closed Won*, for example) goes to Google Ads as a conversion. Google Ads then learns which clicks turned into real customers, not only which clicks filled in a form.

AdPage only reads: it cannot create, change or delete a deal or a contact, and nothing is ever written back to Zoho.

{% hint style="info" %}
**Zoho CRM is part of Offline conversions, which is in a pilot.** The tile only appears for accounts it has been switched on for. If you do not see it, ask <support@adpage.io> to turn it on.
{% endhint %}

The screenshots on this page show a made-up store, with the app in Dutch.

### Before you start

The person who connects needs two things at once:

* An **AdPage login with access to the container** the deals belong to. The connection is stored per container, and a container connects to one Zoho CRM organization. Connecting a different organization later replaces the first one.
* A **Zoho CRM user who can see the deals** that should go along. AdPage reads with the rights of the user who connects: a deal or contact that user cannot see in Zoho, AdPage cannot see either. Connect as an administrator, or as a user whose role and profile give access to every deal in the pipelines you want to use.

Every Zoho data center works: zoho.com, zoho.eu, zoho.in, zoho.com.au and the others. You sign in on Zoho's own page, and Zoho tells AdPage where your account lives.

AdPage asks Zoho for five permissions, all read-only:

| Permission in Zoho              | What AdPage does with it                                                                            |
| ------------------------------- | --------------------------------------------------------------------------------------------------- |
| `ZohoCRM.modules.deals.READ`    | Reads the deals that changed in the period and their stage history: when a deal reached which stage |
| `ZohoCRM.modules.contacts.READ` | Reads the contact on such a deal, so Google can match the conversion to an ad click                 |
| `ZohoCRM.settings.fields.READ`  | Reads your pipelines and stages to choose from, and which deal fields your organization has         |
| `ZohoCRM.org.READ`              | Reads the name and currency of your organization                                                    |
| `ZohoCRM.users.READ`            | Shows which Zoho user made the connection                                                           |

Nothing else: no access to emails, notes, calls, quotes, invoices, accounts (companies) or files, and no write access to anything.

### Connect Zoho CRM

{% stepper %}
{% step %}

#### Open the tile

Go to **Integrations** and select the container at the top of the page. Then open the **Zoho CRM** tile in the email and lifecycle group. Searching for "zoho", "crm" or "deals" finds it too.

<figure><img src="https://data.adpage.io/help/offline-conversies/11-zoho-koppelen.png" alt="The Zoho CRM tile on Integrations, before connecting"><figcaption><p>The Zoho CRM tile, before connecting</p></figcaption></figure>
{% endstep %}

{% step %}

#### Connect

Select **Connect Zoho CRM**. You are sent to Zoho to sign in. Sign in with the Zoho user that can see the deals.
{% endstep %}

{% step %}

#### Accept AdPage in Zoho

Zoho shows the name of the app, **AdPage**, and the permissions above. Select **Accept**.
{% endstep %}

{% step %}

#### Back in AdPage

You return to **Integrations**. The tile shows your Zoho CRM organization (its name and ID), its data center (for example zoho.eu) and the Zoho user who connected it. Check that it is the organization your deals are in.

<figure><img src="https://data.adpage.io/help/offline-conversies/12-zoho-gekoppeld.png" alt="The Zoho CRM tile after connecting, with the organization, data center and user"><figcaption><p>Connected: the organization, its data center and who connected it</p></figcaption></figure>
{% endstep %}
{% endstepper %}

### What you get

Zoho CRM shows nothing in Data Studio by itself. It is a source for **Offline conversions**. Go to **Data boosts**, open the **Boosts** tab and open **Offline conversions**. Then select **New flow**, choose **Deals from Zoho CRM that reach a stage** and select **Create**.

<figure><img src="https://data.adpage.io/help/offline-conversies/13-zoho-nieuw.png" alt="Choosing Zoho CRM as the source of a new flow"><figcaption><p>Zoho CRM as the source of a new flow</p></figcaption></figure>

Under **Flow**, choose the **Pipeline** and the **Stage the deal reaches**, for example *Proposal/Price Quote* or *Closed Won*. The stages carry the names you use in Zoho. Do you not use pipelines in Zoho? Then there is one choice, **All deals**, and it is already selected.

<figure><img src="https://data.adpage.io/help/offline-conversies/14-zoho-fase.png" alt="Pipeline and stage of a Zoho CRM flow"><figcaption><p>Zoho CRM: the pipeline and the stage that counts as a conversion</p></figcaption></figure>

Then, in the flow:

* **What goes along**: rules on the deal amount, the deal type, the lead source, the owner (by name), or whether the contact has an email address. Brent, next to the rules, can set them for you in plain words, for example "Only deals with lead source Google AdWords" or "Only deals above 1,000 euros". Changes stay a draft until you select **Save**.
* **Value and matching**: the conversion value is the amount of the deal, in the currency of the deal or otherwise that of your organization. Google matches on the email address, always hashed; the phone number and the name and address can be added, hashed as well. Choose what sharing with Google rests on: without a basis nothing goes to Google, not even for a check.
* **To which Google Ads account**: a Google Ads account and a conversion action per pipeline. AdPage can create the conversion action for you, as a secondary import action.
* **Dry run**: what would go along over a period of up to 31 days. Nothing goes to Google.
* **Have Google check it**: Google checks the login, the account, the conversion action and the data of the last dry run, without recording anything.

The [Offline conversions](https://docs.adpage.io/data-and-insights/marketing-integrations/offline-conversions.md) page walks through each of these steps with screenshots.

Once the dry run and Google's check are fine, AdPage switches the flow on for you during the pilot. From then on, every hour, the deals that reached the stage since the previous run go to Google Ads. Nothing from before the moment it was switched on goes along.

### Which stage to choose

The stage is what Google Ads learns to bid on, so choose the moment that means "this was a good lead" for your business:

* **An early stage**, such as *Qualification*, gives Google more conversions and faster feedback, but includes leads that never buy.
* **A late stage**, such as *Closed Won*, is the strongest signal, but there are fewer of them and they come later. A deal that closes long after the click may fall outside the click window of the conversion action in Google Ads.

You can make more than one flow, for example one for *Proposal/Price Quote* and one for *Closed Won*, each with its own conversion action. Then decide in Google Ads which of the two your bidding uses.

### What AdPage reads from Zoho CRM

Until a flow is switched on, AdPage only reads Zoho while you work on a flow: to list your pipelines and stages, and when you do a dry run or have Google check it. Once a flow is on, it reads the same every hour, for the deals that changed since the previous run. It reads:

* the deals that changed since the start of the period: stage, pipeline, amount, currency, type, lead source, owner, the linked contact, and when the deal was created and last changed;
* for those deals in your pipeline, their **stage history**: which stage they reached, and when;
* from the contact in the deal's **Contact Name**: email address (or secondary email), phone or mobile number, first and last name, mailing street, postcode, city and country.

None of that customer data is stored with the flow. A dry run keeps counts, deal numbers, dates and values, and which values occur in the rule fields (such as your lead sources), so you can pick them in a rule. It keeps no names, email addresses or phone numbers. Whatever goes to Google is hashed (SHA-256) first, as Google requires.

### Reading the numbers

**The conversion time is the first moment the deal reached the stage**, taken from its stage history. A deal that moves back and enters the stage again counts once. A deal that passed the stage and moved on, for example from *Proposal/Price Quote* to *Closed Won*, still counts for the earlier stage.

**Only the contact in the deal's Contact Name field counts.** A deal without a contact, or whose contact has no email address, gives Google nothing to match on. The dry run counts those as **Without email address**.

**A phone number without a country code (such as 06 12345678) only helps if the contact has a country**, for example *Netherlands*, *Nederland* or *NL*.

**The value is the deal amount as entered in Zoho.** A deal in Zoho has no VAT, so whether the value includes VAT depends on how your team fills in the amount.

**A dry run uses Zoho API credits.** AdPage reads the stage history of every deal that changed in the period, one request per deal. A dry run over a month with many changed deals uses a few hundred of your daily Zoho credits. At most 500 deals are read per dry run; with more, the dry run says it shows part of the deals. Choose a shorter period.

### Troubleshooting

**The Zoho CRM tile is missing.** Offline conversions is switched on per customer; see the note at the top of this page.

**You come back on Integrations with an error.** The approval was cancelled or did not complete. Select **Connect Zoho CRM** again. Does the error say Zoho sent you back from a data center AdPage does not recognize? Then contact <support@adpage.io>.

**The tile says Access expired.** AdPage was removed from the connected apps of the Zoho user, or that user lost access to Zoho CRM. Select **Reconnect**, preferably as a Zoho user who stays with the company.

**A flow cannot load the pipelines and stages.** Usually the connection expired: check the Zoho CRM tile under **Integrations**.

**The dry run asks you to choose the pipeline and stage, while you did.** The stage was renamed or removed in Zoho. Choose the stage again.

**Deals you expect are missing.** The Zoho user who connected cannot see them (their role or sharing rules), or they are in another pipeline. Reconnect as a user who sees every deal.

**Disconnecting.** Select **Disconnect** in the tile. AdPage withdraws its access at Zoho and deletes its copy of it. Flows with Zoho CRM as their source stop reading anything. You can also remove AdPage in Zoho itself, from the connected apps of your Zoho account.

{% hint style="warning" %}
**Zoho CRM is not covered by the daily connection check**, so a broken connection does not email you. If you change users or permissions in Zoho, check the tile afterwards.
{% endhint %}

Still stuck? Contact <support@adpage.io> and include the container and what the tile showed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.adpage.io/data-and-insights/marketing-integrations/zoho-crm.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
