> For the complete documentation index, see [llms.txt](https://help.littledata.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.littledata.io/event-editor/recipes.md).
# Recipes
Add a ready-made event to a destination in one click, then customize it in the Event Editor.
A **recipe** is a ready-made event built by Littledata. Its base event, trigger conditions, and field mappings are already set, so you can add a working setup to a destination in one click instead of building it from scratch.
Adding a recipe creates a normal [custom event](/event-editor/custom-events.md) in that destination. From then on it behaves like an event you built yourself: you can change its conditions, remap its fields, rename it, or disable it.
### Where to find recipes
Open the destination's [Event Editor](/event-editor/getting-started.md). Recipes that suit your store appear in the **Recommended for your store** carousel, above the events list.
Which recipes you see depends on the destination and on your store, so the carousel differs between connections.
The carousel only shows recipes you haven't added yet. Once you add one it drops out of the carousel, so you can't create the same event twice by accident.
### Available recipes
These recipes are available for Meta, GA4, Segment, TikTok and Pinterest:
| Recipe | What it sends |
| ------------------------------- | ---------------------------------------------------------------------------- |
| **New customer purchase** | A customer's first order. Subscription renewals are not included. |
| **Returning customer purchase** | Any order from a customer who has ordered before, and subscription renewals. |
| **First recurring purchase** | The first order of a new subscription. |
| **Recurring purchase** | Subscription renewals. |
Each destination names the event in its own format. This is the name your destination receives:
| Recipe | Meta | GA4 | Segment | TikTok | Pinterest |
| --------------------------- | ------------------------------------------ | ----------------------------- | --------------------------------------- | ------------------------------------- | ------------------------------------- |
| New customer purchase | `New Customer Purchase - Littledata` | `new_customer_purchase` | `New Customer Order - Littledata` | `NewCustomerPurchaseLittledata` | `NewCustomerPurchaseLittledata` |
| Returning customer purchase | `Returning Customer Purchase - Littledata` | `returning_customer_purchase` | `Returning Customer Order - Littledata` | `ReturningCustomerPurchaseLittledata` | `ReturningCustomerPurchaseLittledata` |
| First recurring purchase | `Subscribe` | `first_recurring_purchase` | `First Recurring Order - Littledata` | `FirstRecurringPurchaseLittledata` | `FirstRecurringPurchaseLittledata` |
| Recurring purchase | `Recurring purchase` | `recurring_purchase` | `Recurring Order - Littledata` | `RecurringPurchaseLittledata` | `RecurringPurchaseLittledata` |
| Built on | `Purchase` | `purchase` | `Order Completed` | `CompletePayment` | `checkout` |
### Preview a recipe
Click **Preview** on a recipe card to see what it does before you commit to it:
* **How it works**: what the event is for, in plain language
* **Where the event is**: the standard event the recipe builds on
* **Conditions**: the [trigger conditions](/event-editor/trigger-conditions.md) that decide when the event is sent, and whether ALL or ANY of them have to match
* **Send event to**: the destination that receives it
From the preview you can either **Add event** to take the recipe as it is, or **Customize** to open it in the full Event Editor and change it before saving.
### Add a recipe
Click **Add event**. Littledata creates the event and enables it immediately, so it starts sending as soon as an event matches its conditions. There's no extra step.
The new event appears in your events list with:
* The name from [Available recipes](#available-recipes) for that destination, for example `New Customer Purchase - Littledata` in Meta or `new_customer_purchase` in GA4
* A **Built by Littledata** label, so you can tell recipe events from your own
* An event type of **Custom**
* A status of **Enabled**
### Customize a recipe
A recipe is a starting point, not a locked template. You can change it at two moments:
* **Before adding**: click **Customize** in the preview. The Event Editor opens with the recipe's name, description, conditions, and mappings filled in, and nothing is saved until you click **Save event**.
* **After adding**: open the **three-dot menu** on the event row and select **Edit**. See [Edit an event](/event-editor/edit-an-event.md).
Everything is editable: the event name and description, the [trigger conditions](/event-editor/trigger-conditions.md), the [field mappings](/event-editor/field-mappings.md), and any [custom data sources](/event-editor/custom-data-sources.md) you want to pull in. Use the [event preview](/event-editor/event-preview.md) to check the payload before you save.
{% hint style="info" %}
The event name is the name your destination receives. If you mark the event as a conversion in Meta, GA4, or anywhere else, use the name the recipe gave it, and be aware that renaming it later means the destination starts receiving a different event.
{% endhint %}
### Example: New customer purchase
The **New customer purchase** recipe sends first-time purchases to Meta as their own event, so you can optimize acquisition campaigns on new customers instead of on all purchases.
It builds on **Purchase**, and is sent only when ALL of these are true:
| Field | Operation | Value |
| ----------------------- | -------------------- | ----------- |
| `properties.order_type` | `does not equal` | `RECURRING` |
| `customer.orders_count` | `less than or equal` | `1` |
The first condition drops subscription renewals. The second keeps the event to a customer's first order. Together they give Meta a clean new-customer conversion to optimize toward.
### Good to know
* Recipes are scoped to one connection, like every other Event Editor change. Adding a recipe to Meta does nothing to GA4 or any other destination. To get the same event elsewhere, add the recipe in that destination too.
* Recipes only change what Littledata sends from now on. Historical data isn't reprocessed.
* A recipe event can be turned off without deleting it. See [Enable or disable events](/event-editor/enable-disable-events.md).
### What's next
* [Common setups](/event-editor/common-setups.md): step-by-step versions of setups that don't have a recipe yet
* [Trigger conditions](/event-editor/trigger-conditions.md): how conditions decide when an event is sent
* [FAQ and troubleshooting](/event-editor/event-customiser-faq.md)
