> ## Documentation Index
> Fetch the complete documentation index at: https://help.the-meridian.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Transactions

Transactions are every subscription event Shopify has reported for your app: activations, cancellations, expirations, declines and freezes. It's the ledger behind your revenue numbers, one row per event rather than one row per store.

## The events

| Event | What happened |
| - | - |
| **Activated** | A subscription started: new revenue |
| **Canceled** | A merchant cancelled: revenue lost |
| **Expired** | A trial ended without converting |
| **Declined** | A payment failed |
| **Frozen** | Billing was paused, usually a failed card |

Each of these has its own KPI above the table, with the **amount** attached: activations show revenue added, cancellations and expirations show revenue lost, declines and freezes show the amount at risk. That's the difference between "we lost four subscriptions" and "we lost four subscriptions worth \$340".

## The table

Date, shop, event, plan, mode and amount, newest first. Search by shop name or domain, and filter by event type, plan, or mode. The **date** and **amount** headers sort the whole ledger: one click on amount surfaces the largest transactions first, a second reverses it, a third returns to newest first. The sort survives search and filter changes and lives in the URL, so a sorted view can be shared.

## Live and test

Test events come from development stores and are counted separately. The live-events KPI tells you how many test events sit behind it. Filter to **live** when you're reading revenue, and to **test** when you're checking your own integration.

## How it relates to everything else

* The same events drive [Analytics](/introduction-11): this is the row-level view of what those metrics aggregate.
* Each store's own transactions appear on its [profile](/profile-1), with its full billing history.
* Activations, cancellations and freezes each fire an [automation trigger](/subscription-activated), so a flow can react the moment one lands.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.