“Offline conversions” report

The report shows offline conversions uploaded to Yandex Metrica: for which IDs and goals they were sent, whether they were linked to sessions, and what revenue they generated. For each conversion, you can see whether it was matched to a session, and if it wasn't — for what reason.

Yandex Metrica matches each uploaded conversion to a user session so you can see which source, campaign, or keyword led to that conversion. Only matched conversions are used to optimize campaigns in Yandex Direct and appear in reports.

Conditions for getting the report

To get the report, you need to configure transmitting offline conversions to Yandex Metrica.

To view the report: in the Yandex Metrica left menu, go to Reports → End-to-end analytics → Offline conversions.

Report structure and setup

Some of the report metrics can be used as segmentation conditions.

When uploading a conversion, you transmit one or more IDs (ClientId, UserId, Yclid, PurchaseId), which Yandex Metrica uses to find a matching session.

Report columns:

Column	Description
Conversion date	The date and time of a conversion. It may differ from the date of the session to which the conversion is matched.
ClientID	The ClientId user ID passed in the conversion.
UserID	The UserId user ID passed in the conversion.
YCLID	The Yclid click ID passed in the conversion.
PurchaseID	The PurchaseId purchase ID passed in the conversion.
Target	The goal identifier passed in the Target field.
Goals	The number of goals associated with this conversion.
Session attribution	Specifies whether the conversion is matched to a session or not. If it's not, the reason is provided. To learn more about the reasons, see Why the conversion wasn't matched to a session.
Revenue/currency	The conversion value and currency.
Upload ID	The ID of the data upload that contained the conversion.
Conversion ID	The unique ID of a conversion.

For information about configuring reports, see Report settings.

Why the conversion wasn't matched to a session

Yandex Metrica matches offline conversions to sessions only within a 21-day attribution period before the data upload.

If a conversion isn't matched to a session, the reason for that is provided in the Session attribution column.

Table of reasons

Reason in the report	What it means	What to do
Couldn't find suitable goal	The ID provided in the Target field doesn't match any of the tag's goal identifiers.	Make sure that the tag has an active goal with an identifier matching the value passed in the Target field.
Conversion record is too large	The conversion data row is too large to be processed.	Shorten the values in the conversion fields.
Specified time is in the future	The conversion time is later than the current time at the moment of upload.	Provide the current date and time or an earlier timestamp.
Conversion falls outside the conversion window	The conversion time is earlier than the attribution period start at the moment of upload. Yandex Metrica matches offline conversions only within 21 days of upload.	Upload data within 21 days of the conversion.
No IDs specified for matching	No IDs were provided for finding a session (ClientId, UserId, Yclid, or PurchaseId).	Provide at least one of these IDs.
Couldn't find sessions matching these IDs	No sessions were found for the provided IDs in the range from the start of the attribution period to the conversion time. This means that the ID doesn't exist in the Yandex Metrica database or the session with this ID occurred after the conversion time.	Check that the IDs (ClientId, UserId, Yclid, PurchaseId) are correct and make sure that the session with the given ID occurred no later than the conversion time and within the attribution period.

Examples of messages shown if a conversion wasn't matched to a session

Example 1

A conversion occurred on September 1, 2025, at 18:54. The conversion data was uploaded to Yandex Metrica on September 25, 2025. The Session attribution column displays the following:

“The conversion falls outside the conversion window. The conversion time (01.09.2025 18:54:00) is earlier than the start of the window (04.09.2025 12:45:00) at the time of data upload. Yandex Metrica associates offline conversions with sessions only within 21 days from the time of upload.”

Example 2

The conversion data includes the following IDs: ClientId 123, PurchaseId 345, Yclid 567, and UserId 790. No sessions with these IDs were found in the Yandex Metrica database. The message in the interface:

“Couldn't find sessions with the following provided IDs from the start of the conversion window (04.09.2025 12:45:00) to the conversion time (25.09.2025 18:54:00): ClientId 123, PurchaseId 345, Yclid 567, UserId 790.”

To learn more about uploading offline conversions, see Transmitting and processing data.

Chat with us

---