# Export events

Every item you export with Duplify, whether it’s a product, collection, order, or theme, counts as an **export event**. 

Export events are the unit of measurement that determine how much data you can transfer to your destination store per each export job. Your plan includes a set number of events for job, and if you exceed that limit, additional charges apply. 

By understanding how events are counted, you can better plan exports, avoid additional charges, and choose the plan that fits your store’s needs.

## In this section

* [Understanding export events](#tracking-export-events)
* [Tracking export events](#tracking-export-events)
  * [Auto-sync export events](#auto-sync-export-events)
  * [Examples with metafields](#examples-with-metafields)

***

## Understanding export events

Duplify calculates the size of your source store’s export by tracking export events. Each event represents a single data item or file.

* **One item exported = 1 export event.**
* Your plan includes a fixed number of export events each export job.
* If you hit your export event limit, then you're prompted to upgrade your plan to export more.
* Your balance resets every 30 days based on your plan tier.

Visit our [pricing page](/getting-started/pricing-and-plans.md) to review the available different tiers.

***

## **Tracking export events**

When selecting items to export, the total events for each category appears in the right-hand column. Duplify also displays the estimated total based on your selections.

On the Duplify app dashboard page, you can track how many events you’ve used. This number resets every 30 days with your billing cycle.

{% hint style="success" %}
**Tip**

One item exported is one export event.
{% endhint %}

<table><thead><tr><th width="186.0062255859375">Export category</th><th width="213.590087890625">Export amount</th><th>Export events</th></tr></thead><tbody><tr><td>Products</td><td>1 product</td><td>1 export event</td></tr><tr><td>Collections</td><td>1 collection</td><td>1 export event<br>+ Products (required)</td></tr><tr><td>Customers</td><td>1 customer </td><td>1 export event</td></tr><tr><td>Orders</td><td>1 order </td><td>1 export event + Products and Customers (required)</td></tr><tr><td>Content files</td><td>1 file </td><td>1 export event</td></tr><tr><td>Published theme</td><td>1 active theme </td><td>1 export event + Theme editor images/content files (Optional)</td></tr><tr><td>Navigation menus</td><td>1 menu </td><td>1 export event</td></tr><tr><td>Pages</td><td>1 page</td><td>1 export event</td></tr><tr><td>Blogs and posts</td><td>1 blog post </td><td>1 export event</td></tr><tr><td>Redirects</td><td>All redirects </td><td>Unlimited</td></tr><tr><td>Shop Metafields</td><td>All definitions and values</td><td>Unlimited</td></tr><tr><td>Metaobjects</td><td>All definitions and values</td><td>Unlimited</td></tr></tbody></table>

### Auto-sync export events

After the initial export, auto-sync also uses export events. Any change in the source store triggers an event that updates the destination store if it's set to auto-sync.

When a new product is created in the source store, the destination store automatically receives it with all details, including images, prices, and descriptions. This action initiates an export event.

| Auto-sync category | Amount            | Export event   |
| ------------------ | ----------------- | -------------- |
| Products           | 1 product sync    | 1 export event |
| Collections        | 1 collection sync | 1 export event |


---

# 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://support.duplifyapp.com/using-duplify/export-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.