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

# Offline conversions

Send quotes and deals that close outside your webshop to Google Ads as conversions, from Magento orders or HubSpot or Zoho CRM deals, with rules you set yourself.

A quote that your sales team turns into an order in the Magento admin, or a deal that closes in HubSpot or Zoho CRM, never reaches Google Ads by itself. Smart Bidding then only learns from what happens in the webshop. **Offline conversions** sends those orders and deals to Google Ads as conversions, so Google learns which clicks really turned into customers.

You set it up in a **flow**: a source (Magento orders, or HubSpot or Zoho CRM deals that reach a stage), rules for what goes along, and per store a Google Ads account with a conversion action. Customer data only goes to Google hashed.

{% hint style="info" %}
**Offline conversions is in a pilot.** It 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 %}

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

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

## Before you start

* **Your source is connected** under **Integrations**: [Magento](https://docs.adpage.io/data-and-insights/marketing-integrations/magento.md) for orders, or [HubSpot](https://docs.adpage.io/data-and-insights/marketing-integrations/hubspot.md) or [Zoho CRM](https://docs.adpage.io/data-and-insights/marketing-integrations/zoho-crm.md) for deals.
* **Google Ads is connected** under **Integrations**, and the Google Ads accounts of your stores are selected there. A flow can only send conversions to these accounts: that way they never end up in an account that is not yours. Are your accounts linked under AdPage's manager account (MCC)? Then AdPage can add them for you: ask <support@adpage.io>.
* **You know what sharing customer data with Google rests on**: your terms or privacy statement, or a consent field on the order. Without that, nothing goes to Google, not even for a check.

## Set up a flow

{% stepper %}
{% step %}

### Open Offline conversions

Go to **Data boosts**, open the **Boosts** tab and open **Offline conversions**. You see your flows, at most ten per container, each with its last dry run.

<figure><img src="https://data.adpage.io/help/offline-conversies/01-lijst.png" alt="The list of flows on the Offline conversions page"><figcaption><p>Your flows, with the result of the last dry run</p></figcaption></figure>
{% endstep %}

{% step %}

### Create a flow

Select **New flow**, choose where the conversions come from and select **Create**:

* **Magento**: orders from your Magento store.
* **HubSpot**: deals that reach a stage you choose, for example *Quote accepted*.
* **Zoho CRM**: deals that reach a stage you choose, for example *Proposal/Price Quote* or *Closed Won*.

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

For HubSpot and Zoho CRM, choose the **Pipeline** and the **Stage the deal reaches** under **Flow**. The moment a deal first enters that stage is the conversion time. A Zoho CRM organization without pipelines has one choice, **All deals**.

<figure><img src="https://data.adpage.io/help/offline-conversies/10-hubspot.png" alt="Pipeline and stage of a HubSpot flow"><figcaption><p>HubSpot: the pipeline and the stage that counts as a conversion</p></figcaption></figure>
{% endstep %}

{% step %}

### Do a dry run

The **Dry run** is at the top of the page, next to Brent. Choose a period of at most 31 days and select **Dry run**. AdPage reads the orders or deals of that period, runs them through your rules and shows what would go along. Nothing goes to Google.

<figure><img src="https://data.adpage.io/help/offline-conversies/03-builder.png" alt="The flow page with Brent on the left and the dry run at the top right"><figcaption><p>Brent on the left, the dry run at the top</p></figcaption></figure>

The dry run shows:

* **Records**: all orders or deals in the period.
* **Goes along**: what passes all rules.
* **Value**: the total value of what goes along.
* **Without email address**: goes along, but gives Google nothing to match on.

Below that are the first orders that go along, and the first ones that drop out, with the rule they dropped out on. The stores in the dry run are the stores you later choose a Google Ads account for.

<figure><img src="https://data.adpage.io/help/offline-conversies/04-proefdraai.png" alt="The result of a dry run"><figcaption><p>What would go along, and what drops out on which rule</p></figcaption></figure>
{% endstep %}

{% step %}

### Decide what goes along

Tell **Brent** in plain words what should go along, for example "Only orders sales created in the admin" or "No orders from bol and Amazon". Brent changes the rules for you; you save. He never chooses a Google Ads account or the basis for sharing data.

<figure><img src="https://data.adpage.io/help/offline-conversies/05-brent.png" alt="Brent adds a rule"><figcaption><p>Brent adds a rule; saving is up to you</p></figcaption></figure>

The rules are under **What goes along**, **In plain words** or **As conditions**. A record has to pass every rule, in order; per rule you see how many records it held back in the last dry run. You can add, change and remove rules yourself as well.

<figure><img src="https://data.adpage.io/help/offline-conversies/06-regels.png" alt="The rules of a flow in plain words"><figcaption><p>The rules in plain words</p></figcaption></figure>

Changes are a draft until you select **Save**. After a change, do a new dry run: the counts belong to the rules of the previous one.
{% endstep %}

{% step %}

### Set the value and the matching

Under **Value and matching**:

* **Conversion value**: excluding or including VAT. Choose excluding VAT if your ROAS target is based on revenue without VAT. HubSpot and Zoho CRM have no VAT on a deal: the value is the deal amount.
* **What Google matches on**: the email address always goes along, hashed. Add the phone number and name and address for a better match rate, hashed as well.
* **What sharing with Google rests on**: your terms or privacy statement, or a field on the order, and where it is stated.

<figure><img src="https://data.adpage.io/help/offline-conversies/07-waarde.png" alt="Value, matching keys and the basis for sharing data"><figcaption><p>Value, what Google matches on, and what sharing rests on</p></figcaption></figure>
{% endstep %}

{% step %}

### Choose the Google Ads account per store

Under **To which Google Ads account**:

1. Choose **Through which login**: AdPage's MCC, if your account is linked under AdPage's manager account, or the container's own Google login from Integrations.
2. Check **This client's Google Ads accounts**. Only these accounts can be chosen. Missing one? Select it under **Integrations** at Google Ads.
3. Per store (or pipeline of your CRM), choose the **Google Ads account** and the **Conversion action**.

No suitable conversion action yet? At the bottom of the **Conversion action** list:

* **+ Create "…" (secondary)** creates one with the name above the accounts (by default *Sales order (offerte)*).
* **+ New conversion action with a name of your own…** asks for a name first. Use it when you want a separate action per store or per type of order.

<figure><img src="https://data.adpage.io/help/offline-conversies/08-accounts.png" alt="Choosing the Google Ads account and conversion action per store, with a conversion action with a name of your own"><figcaption><p>Per store an account and a conversion action, here one with a name of your own</p></figcaption></figure>

AdPage always creates the action as a **secondary import action**: it does not count in your bidding strategy yet. Making it primary is up to you in Google Ads, once you trust the numbers. A website action gets a warning: Google does not accept offline conversions there.
{% endstep %}

{% step %}

### Save and have Google check it

Select **Save**, then **Check with Google** under **Have Google check it**. Google checks the login, the account, the conversion action and the data of the last dry run, without recording anything. Per store you see whether Google accepts it, or why not.

<figure><img src="https://data.adpage.io/help/offline-conversies/09-controle.png" alt="The result of the check by Google per store"><figcaption><p>Google accepts the conversions for both stores</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Reading the numbers

**The conversion time is when the order was created**, or for HubSpot and Zoho CRM when the deal first entered the chosen stage.

**Records Google cannot match still count as going along.** A record without an email address gives Google nothing to match on, unless phone matching is on and the record has a phone number. The dry run counts the rest as **Without email address**. Switching on the phone number makes that number smaller.

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

## Troubleshooting

**There are no accounts under This client's Google Ads accounts.** Select the Google Ads accounts of your stores under **Integrations** at Google Ads. Accounts under AdPage's MCC are added by AdPage: ask <support@adpage.io>.

**A store says the account is not one of this client's accounts.** The store was linked to an account that is not in the list. Choose another account, or have it added first if it is yours. Until then the flow does not save and Google does not check it.

**The conversion actions do not load.** The container has no Google Ads login of its own that reaches the account. Connect Google Ads under **Integrations**, or choose the account per store and enter the conversion action ID yourself.

**The dry run says the source did not answer.** Check the Magento, HubSpot or Zoho CRM tile under **Integrations**: an expired connection is the usual cause.

Still stuck? Contact <support@adpage.io> and include the container and the name of the flow.


---

# 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/offline-conversions.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.
