> 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/new-subscriber-conversion-event-meta-ads.md).

# Create a new-subscriber conversion event

Create a new custom event that targets only new subscribers. This can be used for ad platform to optimize for new subscribers or if you want to explicitly track them in Google Analytics.

### What you'll build

A [custom event](/event-editor/custom-events.md) based on purchase, scoped with a [trigger condition](/event-editor/trigger-conditions.md) that fires only when a customer starts their first subscription.

For a subscription brand, a new subscriber is worth far more than a one-time buyer. Instead of treating every purchase the same, A dedicated new-subscriber event tells your destination exactly what a win looks like.

### What you need

* A subscription app that tags first subscription orders, such as [Recharge](https://rechargepayments.com)
* At least one Littledata destination connected, for example [Meta Conversions API](/integrations/facebook-capi.md) or [Google Ads](/integrations/google-ads/google-ads-install-guide.md)
* Access to the Event Editor in the Littledata app

{% hint style="info" %}
Apps like Recharge tag orders to distinguish first subscription orders from renewals, for example `Subscription First Order`. Open a recent first subscription order in Shopify admin to confirm the exact tag your setup writes.
{% endhint %}

### Steps

{% stepper %}
{% step %}

#### Add a custom event

Go to **Settings** for your destination, then open the [Event Editor](/event-editor/getting-started.md).

Click **Add event**.
{% endstep %}

{% step %}

#### Name it and pick the base event

Name the event to your liking, e.g. `NewSubscriber`

Select **Purchase** as the base event. The custom event inherits the complete field mappings of its base, so it sends a full, valid payload from the start. See [Derive a new custom event](/event-editor/custom-events.md).
{% endstep %}

{% step %}

#### Scope it with a trigger condition

Without a condition, the new event fires on every purchase. Add a condition so it only fires for first subscription orders:

| Field             | Operation  | Value                      |
| ----------------- | ---------- | -------------------------- |
| `properties.tags` | `contains` | `Subscription First Order` |

Use the exact tag your subscription app writes. See [Trigger conditions](/event-editor/trigger-conditions.md).
{% endstep %}

{% step %}

#### Preview and save

Use the [event preview](/event-editor/event-preview.md) to check the payload, then click **Save**.
{% endstep %}
{% endstepper %}

### Destination notes

* **Meta**: in Events Manager, mark `NewSubscriber` as a custom conversion, then choose it as the optimization event for acquisition campaigns. Meta optimizes delivery toward people likely to start a subscription.
* **GA4**: mark the event as a key event to report subscriber acquisition by channel.
* **Klaviyo**: use the event as a flow trigger for subscriber onboarding.

### Verify it's working

1. Place a test order that starts a new subscription, or wait for a real one.
2. Confirm the new event appears alongside the standard purchase event, for example in Meta **Events Manager** or GA4 **DebugView**.
3. Renewal orders and one-time purchases should not fire it.

### Make it yours

This setup is a [custom event](/event-editor/custom-events.md) with a condition on an order tag. Any slice of purchases can become its own conversion: first-time customers, a product line, a market.

* Pair it with [Stop subscription renewals counting as conversions](/event-editor/common-setups/exclude-subscription-renewals-from-ad-conversions.md) so purchase stays acquisition-only while the new event targets your highest-LTV conversions.
* Custom events exist per connection. To use the same event in another destination, create it there as well.