# Clone events

Cloning lets one Shopify event produce two destination events.

Littledata sends the original event and an extra modified copy.

## When to use clones

* Send a standard `purchase` event and a `recurring_order` event.
* Create a second event with a different destination name.
* Produce two different payload shapes from one Shopify event.

## How cloning works

{% stepper %}
{% step %}

### Send the original event

Littledata keeps the original event unchanged.
{% endstep %}

{% step %}

### Create a copy

Littledata creates a second event and applies your custom mappings.
{% endstep %}

{% step %}

### Deliver both events

Littledata sends the original event and the cloned event to the destination.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Clones run after filter and modify customisations. If a filter matches, no clone is produced.
{% endhint %}

## Create a clone

{% stepper %}
{% step %}

### Open the destination Events tab

Go to **Settings** for the integration you want to update.

Then open **Events**.
{% endstep %}

{% step %}

### Open an event

Click the event you want to clone.
{% endstep %}

{% step %}

### Choose Clone

Select **Clone** as the customisation type.
{% endstep %}

{% step %}

### Add trigger conditions

Use [trigger conditions](/event-customiser/trigger-conditions.md) to control when the clone runs.
{% endstep %}

{% step %}

### Configure field mappings

Set the [field mappings](/event-customiser/field-mappings.md) for the cloned event.
{% endstep %}

{% step %}

### Save the clone

Click **Save** to activate it.
{% endstep %}
{% endstepper %}

## Example: Subscription order as a separate event

| Field       | Value                                      |
| ----------- | ------------------------------------------ |
| Event       | `order_created`                            |
| Destination | Google Analytics 4                         |
| Type        | Clone                                      |
| Condition   | `app.name` **is** `Recharge Subscriptions` |

### Mappings on the clone

| Source                           | Destination                    |
| -------------------------------- | ------------------------------ |
| `recurring_order` (static value) | `events[0].name`               |
| `locationId`                     | `events[0].params.location_id` |

With this setup, all `order_created` events are sent to GA4 as normal. When the order comes from Recharge, an additional `recurring_order` event is also sent.

## Setting a static event name

{% stepper %}
{% step %}

### Choose Static value

Leave the source dropdown set to **Static value**.
{% endstep %}

{% step %}

### Enter the event name

Type the event name you want, such as `recurring_order`.
{% endstep %}

{% step %}

### Set the destination field

Use `events[0].name` as the destination.
{% endstep %}
{% endstepper %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.littledata.io/event-customiser/clone-events.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.