> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/integrations/destination-platforms/zuora/send-usage-data.md).

# Send Usage Data

### Overview

In this destination service, DinMo will send usage events to Zuora.

To do so, you will need to go through these three steps:

* Creating a Zuora destination. Refer to the [corresponding section](#destination-setup) for more info.
* Creating a user segment composed of all the usage events that will be inserted n Zuora.
* Activating the event segment to the Zuora destination to start sending data. Refer to the [corresponding section](#activation-configuration) for more info.

The destination service only supports “insert only” mode, meaning that we will insert any new event usage in the Orders table.

{% hint style="warning" %}
Insert mode will create every event that is present in the DinMo segment/model.\
**Make sure to filter items that have already been imported.**
{% endhint %}

### Destination Setup

To start synchronizing usage event, you are first required to create a Zuora destination with the corresponding destination service.

{% hint style="info" %}
Learn how to create such a destination in our[ step-by-step tutorial](/guides/get-started-with-dinmo/initial-configuration-of-dinmo/create-a-destination.md).
{% endhint %}

### Activation Configuration

Once the destination has been setup, and your DinMo segment / model created, you can create an activation to start sending data to Zuora right away.

#### Fields mapping

In the Fields mapping section, you are asked to specify the field contained in your DinMo segment / model corresponding to the attributes you want to update for each usage event.

{% hint style="danger" %}
Some fields are specified as mandatory they are necessary to create new events.
{% endhint %}

To insert a new usage event, Zuora requires several attributes. You must map them all to create a new event. These fields may differ depending on your account configuration.

Most of the time, Zuora requires: `Account ID`, `Account Number`, `Quantity`, `Start Date Time` and `Unit of Measure` .

If you wish, you can map any other fields that exist in DinMo and that you wish to keep up to date in Zuora.

**Scheduling**

Define how frequently your data is updated in Zuora. With each scheduled update, DinMo will insert new usage events, with their custom attributes.

**Warnings**

In this section, specify if you want to receive warning for your Zuora activation.

{% hint style="info" %}
Consult the specific section to [learn more about sync warnings](/activations/troubleshooting-syncs/sync-warnings.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.dinmo.io/integrations/destination-platforms/zuora/send-usage-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.