> For the complete documentation index, see [llms.txt](https://docs.roivenue.com/roivenue-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/attribution/transactions-history.md).

# Transactions History

Transactions History shows every order with the customer journey behind it: which touchpoints led to the conversion, when they happened and how much credit each one got.

Most reports in Roivenue show results per platform, campaign or creative. Transactions History goes one level deeper. It lists individual orders and, for each order, the touchpoints that led to it. Use it when you need to explain attribution on a real example, check how a specific order was credited, or verify that tracking works as you expect.

Use Transactions History when you want to:

* show a client or a colleague how attribution splits the credit of one real order
* check why a channel got credit for a specific order
* verify that touchpoints, impressions and path stitching are tracked correctly
* find an order by its ID and see its full journey

<figure><img src="https://4279879158-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGvvrlVUvq4TNL0oYP6%2Fuploads%2Fn06ynAAQFhWigAZr6LXV%2F01-01-transactions-history-overview.png?alt=media&amp;token=18efc83b-f97c-4025-b6d4-637bc3c5b2db" alt=""><figcaption></figcaption></figure>

The page has five parts:

1. **Page actions:** share or save the view, choose the currency, the attribution model and the date range.
2. **Orders table:** all orders in the selected period with their status, Net Revenue and Gross Profit.
3. **Total and Average:** the summary of all orders that match the filters, and the controls to move between pages.
4. **Add to Dashboard:** adds the Orders table to a dashboard. See [Dashboard](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/dashboard).
5. **Filter Panel:** narrows the orders by dimensions such as Site, Platform Name or Campaign (auto). See [Filter Panel](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/filter-panel).

Click an order to open the second level of the page, the **Order Detail** with the customer journey of that order.

To open the page, go to **Attribution → Transactions History** in the left navigation. The date range, the attribution model and the Filter Panel apply to the whole page. See [Date Picker](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/date-picker).

***

### How to read the Orders table

Each row is one order.

| Column       | What it shows                                                          |
| ------------ | ---------------------------------------------------------------------- |
| Order ID     | The ID of the order, as it comes from your web or order data.          |
| Time         | The date and time of the order.                                        |
| Order Status | The status of the order, for example Completed, Delivered or Canceled. |
| Net Revenue  | The Net Revenue of the order in the selected currency.                 |
| Gross Profit | The Gross Profit of the order in the selected currency.                |

The **Total** and **Average** rows at the bottom summarize all orders that match the current filters, not only the rows on the current page.

By default, the newest orders are at the top. Click a column name to sort the table by that column. **Rows per page** sets how many orders you see on one page. Use the arrows next to the page number to move between pages.

***

### How to find a specific order

1. Type into the empty field under a column name, for example the order ID under **Order ID**.
2. The table shows only the matching orders. The filter icon next to the column name turns purple.
3. To choose a different condition, click the filter icon next to the column name, for example to filter **Order Status** by **Contains**.
4. To remove the filter, delete the text from the field.

<figure><img src="https://4279879158-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGvvrlVUvq4TNL0oYP6%2Fuploads%2FB5gIAoYdEWiuVhZBbwOn%2F02-04-find-order.png?alt=media&amp;token=3e45b30f-0639-4294-bea0-5c49ab1a57a1" alt=""><figcaption></figcaption></figure>

The Time column has no text filter. To narrow orders by time, change the date range at the top of the page.

{% hint style="info" %}
**Tip:** Filter **Order Status** by Delivered or Completed to hide canceled orders, which have Net Revenue and Gross Profit of EUR 0.
{% endhint %}

***

### How to open the customer journey of an order

Click an order in the table. The **Order Detail** window opens.

<figure><img src="https://4279879158-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGvvrlVUvq4TNL0oYP6%2Fuploads%2F0MclYqGdzYwIYXTGlxgM%2F03-02-order-detail.png?alt=media&amp;token=40026b56-1f87-4333-a9f8-7f711202bfb0" alt=""><figcaption></figcaption></figure>

1. **Order summary:** Order ID, Customer ID, Time, Order Status, Net Revenue and Gross Profit of the order.
2. **Dimension fields:** choose what the touchpoints show. See [How to choose what the touchpoints show](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/attribution/transactions-history#how-to-choose-what-the-touchpoints-show).
3. **Touchpoint table:** the customer journey. Touchpoints go from the oldest to the newest, so the last row is usually the visit with the conversion.

<table data-search="false"><thead><tr><th>Column</th><th>What it shows</th></tr></thead><tbody><tr><td>No.</td><td>The order of the touchpoint in the journey.</td></tr><tr><td>Dimension</td><td>The value of the selected dimension, for example, the platform. The eye icon next to the dimension value marks an impression; the click icon marks a click.</td></tr><tr><td>Time</td><td>When the touchpoint happened.</td></tr><tr><td>Touchpoint Type</td><td>The type of the touchpoint. See the table below.</td></tr><tr><td>Device Category</td><td>The device of the touchpoint, for example, a desktop or mobile. Synthetic touchpoints, such as SI show (undefined). Roivenue creates them artificially, so there is no device information for them.</td></tr><tr><td>Net Revenue</td><td>The part of the order's Net Revenue that the model gives to this touchpoint.</td></tr><tr><td>Conversion Share</td><td>The share of the conversion that the model gives to this touchpoint. The shares of all touchpoints add up to 100%.</td></tr><tr><td>Connection Probability</td><td>How confident Roivenue is that the touchpoint belongs to the same customer journey. See <a href="https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/attribution/transactions-history#how-to-read-connection-probability">How to read Connection Probability</a>.</td></tr></tbody></table>

| Touchpoint type           | What it is                                                                                                                                                                                           |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Visit                     | A website session.                                                                                                                                                                                   |
| SV (Synthetic Visit)      | The first touchpoint of a journey reconstructed from GA4 API data.                                                                                                                                   |
| Impression                | An ad impression tracked by the Roivenue impression pixel. See [Impression Tracking](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/impression-tracking). |
| SI (Synthetic Impression) | An impression reconstructed from platform data.                                                                                                                                                      |

For more about the difference between clicks and impressions, see [Click-based vs. Impression-based Touchpoints](https://docs.roivenue.com/roivenue-resources/roivenue-training/core-concepts/click-based-vs.-impression-based-touchpoints).

**Example:** the order in the screenshot has Net Revenue of EUR 16,386 and eight touchpoints. The customer came twice from Criteo, then directly, then from Google Ads, and four more times directly before buying. AI Data Driven gives 60.4% of the conversion to the first Criteo visit, 16.7% to the second Criteo visit, and 22.9% to Google Ads. In Net Revenue, that is EUR 9,900.45, EUR 2,739.75 and EUR 3,745.85. The direct visits get 0%. To see why a touchpoint gets no credit, see [FAQ 1](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/attribution/transactions-history#id-1.-why-does-a-touchpoint-have-0-conversion-share).

To close the window, click **×** in the top right corner.

***

### How to choose what the touchpoints show

Above the touchpoint table, there are two **Dimension** fields:

* The first dimension defines the main column, for example, **Platform Name**.
* The second dimension is optional. It adds another column, for example **Campaign (auto)** or **Ad Creative**, so you see the platform and the campaign of each touchpoint at once.
* To remove the second dimension, click **×** in the field.
* The dimensions you choose stay the same when you open another order.

<figure><img src="https://4279879158-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGvvrlVUvq4TNL0oYP6%2Fuploads%2Fuhc9iXSQniGMcmFGJgyT%2F04-03-second-dimension.png?alt=media&amp;token=f061a9fd-e6f8-47a6-a3a6-3dad3bec18ff" alt=""><figcaption></figcaption></figure>

You can use any dimension of your account, for example Channel Type, Source/Medium/Campaign, or See-Think-Do-Care. You can also create your own dimension. See [Custom Dimensions](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/data/custom-dimensions).

***

### How the attribution model changes the journey

The journey and the credit come from the attribution model selected at the top of the page. When you switch the model, the same order can show different touchpoints and a different split of credit:

* **AI Data Driven** spreads the credit across the journey, including synthetic impressions if the model uses them. See [AI Data Driven Attribution](https://docs.roivenue.com/roivenue-resources/roivenue-training/core-concepts/ai-data-driven-attribution).
* Rule-based models such as **Last Touch**, **First Touch**, or **Linear** split the credit by a fixed rule. They do not include synthetic impressions, so their journeys can be shorter.

To see which settings the model uses, for example, path stitching or synthetic impressions, open **Model Info** in [Path Analysis](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/attribution/path-analysis). To compare the results of several models per channel, use [Model Comparison](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/attribution/model-comparison).

***

### How to read Connection Probability

Roivenue Measurement uses path stitching to connect touchpoints that would otherwise look like separate journeys, for example, when a customer starts on a phone, continues on a laptop, and buys on a tablet. Roivenue compares signals such as the device setup and browsing patterns to decide whether the visits belong to the same customer.

Connection Probability shows how confident Roivenue is about each connection:

* **100%** means the touchpoint is clearly part of the same journey.
* A lower value together with a different **Device Category** usually means that Roivenue joined the touchpoint through cross-device stitching.

Use it to understand fragmented journeys and to see why a touchpoint on another device still gets credit.

{% hint style="info" %}
**Tip:** Path stitching needs [Roivenue Measurement](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement) as the source of web data. Without it, Connection Probability is usually 100% for all touchpoints, because Roivenue does not join sessions across devices.
{% endhint %}

***

### How to save and share the view

* **Save** saves the current view as a bookmark. See [Bookmarks](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/bookmarks).
* **Share** copies a link to the current view.
* **Add to Dashboard** adds the Orders table to a dashboard. See [Dashboard](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/dashboard).

***

#### FAQ

<details>

<summary>1. Why does a touchpoint have 0% Conversion Share?</summary>

The model gives this touchpoint no credit for the conversion. There are two common reasons. The model sees the touchpoint as not important for the purchase, for example, a repeated direct visit shortly before it. Or a rule in the attribution model sets the weight of this touchpoint to zero, for example, a rule that zeroes out direct traffic. See Custom Touchpoint Weights in [Attribution Models](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/account-configuration/attribution-models#custom-touchpoint-weights). The touchpoint stays in the journey, so you still see the full sequence. See also [Direct and Organic Traffic](https://docs.roivenue.com/roivenue-resources/roivenue-training/core-concepts/direct-and-organic-traffic).

</details>

<details>

<summary>2. Why does the same order look different in another attribution model?</summary>

Each model builds and credits the journey in its own way. AI Data Driven can include synthetic impressions and spread the credit across the journey. Rule-based models do not include synthetic impressions, so the journey can be shorter, and the credit is assigned by a fixed rule. See [Last Touch vs. AI Data Driven Attribution](https://docs.roivenue.com/roivenue-resources/roivenue-training/core-concepts/last-touch-vs.-ai-data-driven-attribution).

</details>

<details>

<summary>3. Why don't I see any impressions in the journeys?</summary>

Impression touchpoints need an active Roivenue impression tracking pixel in your advertising platforms. See [Impression Tracking](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement/impression-tracking). SI touchpoints need web data and platform data that Roivenue can match, and the attribution model must use synthetic impressions. See the FAQ in [Path Analysis](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/attribution/path-analysis).

</details>

<details>

<summary>4. What does SV mean in Touchpoint Type?</summary>

SV is a Synthetic Visit. It appears when web data comes from the GA4 API, which reports only the first and the last touchpoint of a journey. Roivenue adds the first touchpoint as a Synthetic Visit to keep the journey complete. For full journeys, connect GA4 through BigQuery or use Roivenue Measurement. See [Sharing GA4 Data through BigQuery](https://docs.roivenue.com/roivenue-resources/implementation/web-data/google-analytics-4/sharing-ga4-data-through-bigquery) and [Roivenue Measurement](https://docs.roivenue.com/roivenue-resources/implementation/web-data/roivenue-measurement).

</details>

<details>

<summary>5. Why do canceled orders show EUR 0?</summary>

A canceled order has Net Revenue and Gross Profit of EUR 0, so it adds no revenue to any channel. The journey still shows which touchpoints led to it. To hide canceled orders, filter the Order Status column. See [How to find a specific order](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/attribution/transactions-history#how-to-find-a-specific-order).

</details>

<details>

<summary>6. What do "(undefined)" or "Referral" mean in a journey?</summary>

They are the default values of the dimension. When no rule for the dimension matches a touchpoint, Roivenue labels it with the default value, for example, Referral or Other in Platform Name, or (undefined) when the default value is empty. Add a rule in **Data → Dimensions** to move the touchpoints to the right value. See [Custom Dimensions](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/data/custom-dimensions).

</details>

<details>

<summary>7. Can I export the orders and their journeys?</summary>

The Orders table can be added to a dashboard. For a file with the journeys of all orders, Roivenue offers the Raw Path Export, which contains raw touchpoints and conversions. An orders export with data from your order management system needs the Transaction Feed. Both are add-on services. To order them, contact your Customer Success Manager through the [Roivenue Help Center](https://docs.roivenue.com/roivenue-resources/roivenue-help-center).

</details>

<details>

<summary>8. Why are there no orders for an older period?</summary>

Transactions History shows only orders for which Roivenue has data. An older period is usually empty for one of two reasons. Your web data were not connected to Roivenue in that period, for example, because tracking started later. See [Web Data](https://docs.roivenue.com/roivenue-resources/implementation/web-data). Or, if you use the [Transaction Feed](https://docs.roivenue.com/roivenue-resources/implementation/connecting-backend-data), the order data for that period were not sent to Roivenue. To add data for an older period, contact your Customer Success Manager through the [Roivenue Help Center](https://docs.roivenue.com/roivenue-resources/roivenue-help-center).

</details>
