# Send profile events

#### Overview <a href="#overview" id="overview"></a>

In this destination service, DinMo will export events in the profiles of **Klaviyo.**

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

* Creating a Klaviyo destination. Refer to the [corresponding section](https://docs.dinmo.io/integrations/destination-platforms/klaviyo) for more info.
* Creating a user segment composed of all the events and their attributes that will be sent in Klaviyo. Refer to this [step-by-step tutorial](https://docs.dinmo.io/guides/get-started-with-dinmo/create-and-activate-segments-on-dinmo/create-your-first-segment) to learn how to build segments without SQL in DinMo.
* Activating the segment to the Klaviyo destination to start sending data.

{% hint style="info" %}
Any records added to your model or segment are treated as new events and are sent to Klaviyo when your sync runs.
{% endhint %}

### Destination setup <a href="#destination-setup" id="destination-setup"></a>

To start sending events, you are first required to create a Klaviyo destination with the corresponding destination service.

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

### Activation configuration

Once the destination has been setup, and your DinMo event segment (or model) created, you can create an activation to start sending data to Klaviyo right away.

#### Fields mapping

In the Fields mapping section, you are asked to specify the field contained in your DinMo segment that Klaviyo will use to link each segment's records to a Klaviyo contact. Depending on your Klaviyo configuration, it may be the **email address** of the user or a **phone number**.

You are also asked to specify the event name.<br>

You can also map standard attributes linked to your event, especially:

* The time of occurence
* The value
* The currency
* The event ID

<figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2FjbnRjJFq9sCC3i3s1xgU%2Fimage.png?alt=media&#x26;token=801996b3-9fd7-406d-95c4-68300f56ec4e" alt="" width="563"><figcaption></figcaption></figure>

#### Scheduling

In this section, specify how often the events should be sent to Klaviyo.

All new events will be sent in batch to Klaviyo at the specified time interval (but using the event\_time you declared)

#### Warnings

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

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


---

# 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://docs.dinmo.io/integrations/destination-platforms/klaviyo/send-profile-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.