# Overview

The Event Editor is a no-code interface for shaping how Littledata sends Shopify events to your marketing and analytics destinations. Use it to align tracking with your reporting requirements without engineering effort or upstream schema changes.

## When to use it

Reach for the Event Editor when you need to:

* Match a destination's expected schema by renaming fields or adding required parameters
* Reduce noise by filtering out events that shouldn't reach a specific destination
* Capture additional context from metafields, cookies, or browser storage
* Generate a derivative event from an existing Shopify trigger

## Core capabilities

* Event control: enable, disable, or scope the default events tracked per destination
* Field mapping: customise how source fields map to destination parameters
* Filters and conditions: apply rules so events only fire when criteria are met
* Clones: generate additional events from a single Shopify trigger
* Custom data: enrich payloads with values from metafields, cookies, and local storage
* Preview: inspect the exact destination payload before saving

## In this section

* [Events tab](/event-editor/events-tab.md): browse, enable, and disable tracked events
* [Customise event field mappings](/event-editor/field-mappings.md): change how source fields map to destination parameters
* [Filter events](/event-editor/filter-events.md): stop matching events from being sent
* [Clone events](/event-editor/clone-events.md): send an extra event from one Shopify trigger
* [Trigger conditions](/event-editor/trigger-conditions.md): scope a customisation to matching events only
* [Custom Data Sources](/event-editor/custom-data-sources.md): use metafields, cookies, and local storage values
* [Event preview](/event-editor/event-preview.md): preview the destination payload before saving
* [Event Editor FAQ and troubleshooting](/event-editor/event-customiser-faq.md): answers and fixes for common issues
* [Glossary](/event-editor/glossary.md): look up available fields and objects


---

# 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-editor/overview.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.