> 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/hubspot.md).

# HubSpot

Connect HubSpot so deals that reach a stage you choose, such as an accepted quote, can go to Google Ads as offline conversions.

Connect HubSpot so AdPage can see the deals your sales team closes outside the webshop. With **Offline conversions** on **Data boosts**, a deal that reaches a stage you choose (*Quote accepted*, for example) goes to Google Ads as a conversion. Google Ads then learns which clicks turned into 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 HubSpot.

{% hint style="info" %}
**HubSpot 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 %}

### 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 HubSpot account. Connecting a different HubSpot account later replaces the first one.
* A **HubSpot user who may install apps** in that HubSpot account: a Super Admin, or a user with permission to install apps from the App Marketplace. Without that permission, ask an admin of your HubSpot account to do the connecting, or to give you the permission.

AdPage asks HubSpot for two permissions, both read-only:

| Permission in HubSpot       | What AdPage does with it                                                                     |
| --------------------------- | -------------------------------------------------------------------------------------------- |
| `crm.objects.deals.read`    | Reads the deals that reach the stage you choose, and the pipelines and stages to choose from |
| `crm.objects.contacts.read` | Reads the contact on such a deal, so Google can match the conversion to an ad click          |

Nothing else: no access to emails, notes, calls, tickets, companies or files, and no write access to anything.

### Connect HubSpot

{% stepper %}
{% step %}

#### Open the tile

Go to **Integrations** and select the container at the top of the page. Then open the **HubSpot** tile in the email and lifecycle group. Searching for "crm" or "deals" finds it too.
{% endstep %}

{% step %}

#### Connect

Select **Connect HubSpot**. You are sent to HubSpot. If your HubSpot user has access to more than one HubSpot account, HubSpot first asks which one: choose the account the deals are in.
{% endstep %}

{% step %}

#### Approve AdPage in HubSpot

HubSpot shows the name of the app, **AdPage**, and the two permissions above. Approve them.

{% hint style="warning" %}
**AdPage's HubSpot app is new.** HubSpot therefore asks you to confirm that you trust AdPage as an integration before you can connect it. That is expected: confirm, and continue.
{% endhint %}
{% endstep %}

{% step %}

#### Back in AdPage

You return to **Integrations**. The tile shows your HubSpot account (its domain and portal ID) and the HubSpot user who connected it.
{% endstep %}
{% endstepper %}

### What you get

HubSpot shows nothing in Data Studio by itself. It is a source for **Offline conversions**:

1. Go to **Data boosts**, open the **Boosts** tab and open **Offline conversions**.
2. Select **New flow**, choose **Deals from HubSpot that reach a stage** and select **Create**.
3. Choose the **Pipeline** and the **Stage the deal reaches**, for example *Quote accepted* or *Closed won*.

Then, in the flow:

* **What goes along**: rules on the deal amount, the deal type, the owner, 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 above 1,000 euros". Changes stay a draft until you select **Save**.
* **Value and matching**: the conversion value is the amount of the deal. 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.

{% hint style="info" %}
**Switching a flow on comes in a next step.** For now you can set up flows, do dry runs and have Google check them. Nothing goes to Google Ads as a conversion yet.
{% endhint %}

### What AdPage reads from HubSpot

Until a flow is switched on, AdPage only reads HubSpot while you work on a flow: to list your pipelines and stages, and when you do a dry run or have Google check it. It then reads, for the deals that entered the chosen stage in the period:

* from the deal: the amount, currency, deal type, owner, pipeline, close date, and when it entered the stage;
* from the first contact associated with the deal: email address, phone or mobile number, first and last name, address, 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 deal types), 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 when the deal entered the stage**, not its close date or the date it was created.

**Only the first contact on a deal 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**.

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

**A long period can be too much for one dry run.** The dry run then says it shows part of the deals. Choose a shorter period.

### Troubleshooting

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

**HubSpot does not let you approve.** Your HubSpot user may not install apps. Ask a Super Admin of your HubSpot account to connect, or to give you that permission.

**You come back on Integrations with an error.** The approval was cancelled or did not complete. Select **Connect HubSpot** again.

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

**A flow cannot load the HubSpot pipelines.** Usually the connection expired: check the HubSpot tile under **Integrations**.

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

{% hint style="warning" %}
**HubSpot is not covered by the daily connection check**, so a broken connection does not email you. If you change users or apps in HubSpot, 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/hubspot.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.
