> 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/common-setups.md).

# Common setups

These are common setups and configurations for the Event Editor you can copy. Each one solves a real problem step by step: what you'll build, what you need, and how to set it up.

### Cut orders you don't want counted

Hold an event back unless it matches your conditions, powered by trigger conditions. Staff orders, B2B, renewals: if it skews your data, filter it out before it reaches the destination.

* [Keep B2B orders out of your ad conversions](/event-editor/common-setups/keep-b2b-orders-out-of-ad-conversions.md)
* [Exclude subscription renewals from conversions](/event-editor/common-setups/exclude-subscription-renewals-from-ad-conversions.md)
* [Exclude staff and test orders](/event-editor/common-setups/exclude-staff-and-test-orders.md)
* [Exclude purchases from a specific market](/event-editor/common-setups/exclude-purchases-from-a-specific-market.md)
* [Send add-to-carts only above a value](/event-editor/common-setups/send-add-to-carts-only-above-a-value.md)

### Give a slice of orders its own event

Spin a named event off an existing one with custom events, without touching the original. Your destination gets a dedicated conversion to report on, trigger from, or optimize against.

* [Create a new-subscriber conversion event](/event-editor/common-setups/new-subscriber-conversion-event-meta-ads.md)
* [Create a VIP purchase event](/event-editor/common-setups/vip-loyalty-purchases-meta-ads.md)
* [Track purchases from a specific collection](/event-editor/common-setups/track-purchases-from-a-specific-collection.md)

### Send data that isn't in your events

Pull in data from metafields with custom data sources, then route it where the destination expects it with field mappings. Loyalty tier, quiz answers, margin: if an app stores it, you can send it.

* [Send product metafields to a destination](/event-editor/common-setups/personalise-klaviyo-flows-with-product-metafields.md)
* [Build audiences from survey answers](/event-editor/common-setups/quiz-answer-lookalikes-meta-ads.md)

### How each setup works

Every setup follows the same format:

1. **What you'll build**: the outcome in one sentence, and which Event Editor features it uses
2. **What you need**: apps, data sources, and destinations
3. **Steps**: the exact Event Editor setup
4. **Verify**: how to confirm it's working

The steps show one worked example. The same pattern works with your own fields and conditions, so treat any setup as a starting point.

{% hint style="info" %}
Have a use case you'd like to see as a setup? Email <help@littledata.io> and we'll consider it for the gallery.
{% endhint %}