> ## Documentation Index
> Fetch the complete documentation index at: https://docs.upstackdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# all_purchase Event

> Track all purchases with unified customer segmentation — automatically generated by Upstack

<Info>
  **Automatically Generated** — This event is created by Upstack backend services for Shopify customers. You do not need to fire this event manually.
</Info>

## Overview

The `all_purchase` event is generated for every purchase, regardless of customer type. It provides a unified purchase event that includes customer segmentation metadata, making it ideal for destinations that need a single purchase event with segmentation data attached.

## How It Works

When a purchase occurs, Upstack generates an `all_purchase` event alongside the standard `purchase` event:

1. **Order received** — Shopify sends a purchase webhook to Upstack
2. **Customer analysis** — Upstack determines customer type (new, returning, lapsed, etc.)
3. **Event generation** — An `all_purchase` event is created with segmentation metadata
4. **Forwarding** — The event is sent to configured destinations

This event is useful when you want all purchases sent to a destination but still need to segment by customer type in your reporting.

## Properties

This event includes all properties from the original `purchase` event:

| Property | Type   | Description                              |
| -------- | ------ | ---------------------------------------- |
| orderId  | string | Shopify order ID                         |
| value    | number | Order total value                        |
| currency | string | ISO 4217 currency code (e.g., `USD`)     |
| items    | array  | Products purchased                       |
| email    | string | Customer email (hashed for destinations) |
| phone    | string | Customer phone (hashed for destinations) |

## Destination Mapping

This event is forwarded to destinations as:

| Destination           | Event Name        | Notes                                     |
| --------------------- | ----------------- | ----------------------------------------- |
| **Meta CAPI**         | `Purchase`        | Standard purchase with all customer types |
| **Google Ads**        | `purchase`        | Unified purchase event                    |
| **TikTok Events API** | `CompletePayment` | All purchases                             |
| **Klaviyo**           | `Placed Order`    | All orders                                |
| **GA4**               | `purchase`        | Standard e-commerce purchase              |

## Use Cases

* **Unified reporting** — Single event stream that includes all purchase types
* **Destination simplification** — Send one purchase event type instead of managing multiple
* **Consistent attribution** — Ensure all purchases contribute to campaign optimization equally
* **Baseline metrics** — Track total purchases before segmenting by customer type

## Relationship to Other Events

The `all_purchase` event represents the union of:

* `nc_purchase` — New customer purchases
* `rc_purchase` — Returning customer purchases

Every purchase generates both an `all_purchase` event AND one of the customer-type-specific events (`nc_purchase` or `rc_purchase`).

## Related Events

* [purchase](/pixel/standard-events#purchase) — The base purchase event
* [nc\_purchase](/pixel/events/upstack-generated/nc-purchase) — New customer purchases only
* [rc\_purchase](/pixel/events/upstack-generated/rc-purchase) — Returning customer purchases only