---
slug: offline-conversions-importieren
title: "How do I get CRM deals into the reporting?"
category: berichte
locale: en
updated: 2026-10-16
keywords: ["offline","CRM","import","in-store","phone sales","deal","B2B"]
questions: ["Can I import conversions that did not happen on the website?","Do I need consent for the offline import?","Which consent columns does the import need?","Import offline conversions","Match CRM deal","Measure in-store purchase","Attribute phone sale to a campaign","Add a conversion afterwards"]
url: https://bench.metrunio.com/en/help/offline-conversions-importieren
---

# How do I get CRM deals into the reporting?

**Can I import conversions that did not happen on the website?**

You import them as CSV: a lead closed on the phone weeks later just as well as a purchase in the shop. Matching happens through a unique anchor (order ID, lead ID or click ID); rows without such an anchor are rejected rather than guessed.

1. Open “Orders & goals” and download the template.
2. Per row, enter a reference, the timestamp, the value and the anchor that identifies the person.
3. Choose the website and the file and click “Check”. The dry run shows what would be imported without storing anything.
4. Click “Import”. Seconds later the conversions appear in journeys and attribution.

## The anchor

| Column | What belongs there |
| --- | --- |
| order_id | the order number assigned online |
| lead_id | the lead identifier from the form; the SDK writes it there as `metrunio_lead_id` |
| click_id | gclid, fbclid, msclkid, ttclid or li_fat_id |

One is enough. If a row carries several, the order number wins over the lead ID, and that over the click ID. The order number is the most unambiguous.

For subscriptions there are two optional columns, for purchases only: subscription_id (or abo) with the subscription ID and subscription_renewal (or folgezahlung) with yes or no. A renewal is attributed according to the first order of the same subscription; the article on subscription renewals has more. An empty value means “not a renewal”, an unreadable one rejects the row.

## Consent per row

| Column | What belongs there |
| --- | --- |
| consent_state | granted or partial, as the person consented; empty if there is no information |
| consent_purposes | analytics and/or marketing, separated by semicolons |
| consent_source | where consent was given, e.g. contact form, cookie banner, contract |
| consent_at | when consent was given |
| consent_ref | where the evidence is kept on your side: record in your CRM or consent tool including the text version shown |
| consent_withdrawn_at | if withdrawn: when; the row is then not imported |

Uploading the file is not consent from the people in it. Every row therefore carries its own: with consent the row is matched to its journey, and with marketing it is also reported to advertising platforms; source and time stay with the row as evidence. Without information, only a purchase is imported: for revenue reconciliation with its order number, without browser, customer or advertising identifiers, counted in revenue, attributed to no channel. The same applies to a purchase with denied, as after any refusal, but only with an activated additional instruction for revenue reconciliation; without it the row shows as rejected after the import, with the reason. A lead without information or with denied is rejected, as is a row with a withdrawal or with incomplete or contradictory information. If a row carries consent, you confirm when importing that you can prove it. Metrunio checks your information for completeness and contradictions, not whether the consent is legally valid.

When a row is matched by lead ID or click ID, the reference from the first column appears as its order number: the number the deal carries in your CRM or point of sale. A phone sale has no order number from the shop, and an invented one would be worse than the real reference.

> **Note:** A row without an anchor is rejected, not imported. It would be revenue without a journey: the conversion count would rise, the match rate would fall, and the measurement would be no better for it.

## What this is not

Not offline modelling. Only what actually happened is imported, and the link to the journey comes from a unique anchor. The imported conversion counts as measured; the way it is shared among the touchpoints preceding it counts as attributed. Nothing is extrapolated.

> **Legal note:** A conversion from your CRM does not originate in a browser; a consent tool cannot report anything about it. As the controller you are responsible for the consent information. It must show what the person consented to. Before the first import, check whether your privacy policy covers this joining of data. This note does not replace legal advice.

> **Caution:** An import cannot be undone with one click: the rows take the same route as measured events. Hence the dry run, and hence “Import” only unlocks after it. Uploading the same file twice still creates no duplicate conversions; the per-row reference prevents that.

## Also asked

- Do I need consent for the offline import?
- Which consent columns does the import need?
- Import offline conversions
- Match CRM deal
- Measure in-store purchase
- Attribute phone sale to a campaign
- Add a conversion afterwards

## Related

- https://bench.metrunio.com/en/help/conversion-rueckgabe
- https://bench.metrunio.com/en/help/gemessen-zugeordnet-geschaetzt
- https://bench.metrunio.com/en/help/welche-kennungen
- https://bench.metrunio.com/en/help/herkunft-im-formular
- https://bench.metrunio.com/en/help/abo-folgezahlungen