# Event preview

Event preview shows the exact payload Littledata will send to your destination.

It uses a real historical event from your shop.

## Use the preview

{% stepper %}
{% step %}

### Open an event editor

Open any supported event from the destination **Events** tab.
{% endstep %}

{% step %}

### Review the preview

The preview uses a recent example of the same event type.

It applies your current mappings, including unsaved changes.
{% endstep %}

{% step %}

### Switch views if needed

Use **Pretty** for readability.

<figure><img src="/files/TlV0repJlylLKVC4ZXSt" alt=""><figcaption></figcaption></figure>

Use **Raw** to inspect the exact JSON payload.

<figure><img src="/files/48mx8AygHBFlEe3pr9X7" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

This helps you verify:

* Source field paths return the values you expect.
* Custom parameters map to the correct destination keys.
* The output matches your destination schema.

## Pretty vs Raw

* **Pretty** shows a formatted, readable view.
* **Raw** shows the exact JSON payload.

## What the preview shows

The preview always shows the **destination payload**, not the raw Shopify source event.

* For **Modify** customisations, it shows the modified event.
* For **Clone** customisations, it shows the cloned copy.

{% hint style="info" %}
The preview is not available for **Filter** customisations. Filters produce no output event.
{% endhint %}

## Limitations

* The preview uses a stored historical event, not a live one.
* Very recent metafield additions may not appear yet.
* Trigger conditions are not applied in the preview.


---

# 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/event-preview.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.