> ## 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.

# rc_purchase Event

> Track purchases from returning customers — automatically generated by Upstack

> [!NOTE]
>
> **Automatically generated** — Upstack creates this event from your `purchase` events. You don't fire it.

Fires when Upstack already has a customer record for the buyer of a `purchase`.

## How It Works

Upstack classifies every `purchase` event it processes:

1. **Customer lookup.** Upstack looks for a customer record under the buyer's Upstack identity and under each email address on the event.
2. **Classification.** If there is one, Upstack generates `rc_purchase`. If there's no record, it generates [`nc_purchase`](https://docs.upstackdata.com/event-tracking/event-taxonomy/standard-events/nc-purchase) instead.
3. **Record update.** Upstack adds the order to the buyer's customer records.
4. **Forwarding.** The new event goes to your destinations, as shown below.

The customer records are Upstack's own, built from the orders and purchase events it has received for your store. Upstack doesn't look up the customer's history in Shopify. A `purchase` event with no Upstack identity gets neither `rc_purchase` nor `nc_purchase`.

This check is separate from the [customer type](https://docs.upstackdata.com/data-dictionary/measures-and-dimensions.md#customer-type) that splits order reports into new and returning, which matches orders on the Shopify customer ID. The two counts can differ.

## Parameters

You don't send this event. Upstack creates it from [`purchase`](https://docs.upstackdata.com/event-tracking/event-taxonomy/standard-events/purchase), so it carries the same standard parameters and user data.

The event is the purchase event under a different name. Upstack also adds a customer segmentation value, which Meta receives as `customer_segmentation` (see the table below).

## Destination Mapping

| Destination | Event name | Sent by default |
| - | - | - |
| Meta | `rcPurchase` (custom event), with `customer_segmentation: existing_customer_to_business` in custom data | Yes |
| TikTok | `RCPurchase` | Yes |
| GA4 | `rc_purchase` | Yes |
| Reddit | `rc_purchase` (custom event) | Yes |
| Microsoft Ads | `rc_purchase` (custom event) | Yes |
| Google Ads | The conversion action you map it to | No. Map it to a conversion action |
| Klaviyo, Pinterest | Your choice | No. Add a [destination event mapping](https://docs.upstackdata.com/guides/custom-events/destination-event-mappings.md) |
| Snapchat, LinkedIn, AppLovin | Not sent | No |

Meta needs each custom event approved before you can optimize on it. See [How to approve Meta custom events](https://docs.upstackdata.com/destinations/catalog/meta-capi/how-to-approve-facebook-meta-custom-events.md).

## Related events

* [purchase](https://docs.upstackdata.com/event-tracking/event-taxonomy/standard-events/purchase.md) — The base purchase event for all orders
* [nc\_purchase](https://docs.upstackdata.com/event-tracking/event-taxonomy/standard-events/nc-purchase.md) — New customer purchases
* [all\_purchase](https://docs.upstackdata.com/event-tracking/event-taxonomy/upstack-generated/all-purchase.md) — All purchases
* [lapsed\_purchase](https://docs.upstackdata.com/event-tracking/event-taxonomy/upstack-generated/lapsed-purchase.md) — Purchases from lapsed customers who returned


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