> For the complete documentation index, see [llms.txt](https://help.daasity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.daasity.com/core-concepts/audiences-reverse-elt/pushing-audience-data-to-targets/klaviyo/target-endpoint-documentation.md).

# Target Endpoint Documentation

## Target Overview

The Daasity Audiences product uses the [Klaviyo Track-Identify](https://apidocs.klaviyo.com/reference/track-identify) endpoint to update a profile (Identify) or add an event to a profile (Track).  Daasity separates the entire list of generated profiles to be updated into individual records and makes an API call to Klaviyo for that specific profile to be updated

## Identify API

Daasity creates a new profile or updates an existing profile in Klaviyo based on the data provided by the Klaviyo Profile target

* Endpoint: <https://apidocs.klaviyo.com/reference/track-identify#identify>
* Frequency: Daily (available to run On-Demand via the UI)

| Daasity UI Section | Daasity Property | Klaviyo Property                            |
| ------------------ | ---------------- | ------------------------------------------- |
| Data Mapping       | $email           | $email                                      |
| Data Mapping       | $phone\_number   | $phone\_number                              |
| Data Mapping       | Source           | Property Name from Data Mapping Destination |

{% hint style="info" %}

* You must specify either $email or $phone\_number (for SMS only contacts) to match or create a new profile
* Daasity can update Klaviyo standard properties (not recommended) or create / update additional properties
  {% endhint %}

## Track API

Daasity pushes a new event into each profile at Klaviyo based on the data provided by the Klaviyo Events target

* Endpoint: <https://apidocs.klaviyo.com/reference/track-identify#track-get>
* Frequency: Daily (available to run On-Demand via the UI)

<table><thead><tr><th width="230.33333333333331">Daasity UI Section</th><th>Daasity Property</th><th>Klaviyo Property</th></tr></thead><tbody><tr><td>General</td><td>Event Name</td><td>$event_id</td></tr><tr><td>Data Mapping</td><td>$email</td><td>$email</td></tr><tr><td>Data Mapping</td><td>$phone_number</td><td>$phone_number</td></tr><tr><td>Data Mapping</td><td>Source</td><td>$value</td></tr></tbody></table>

{% hint style="info" %}

* You must specify either $email or $phone\_number to match or create a new profile that the event is related to
* You must specify an $event\_id to provide the name for the event
* You must specify a $value to indicate the value for the event
  {% 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://help.daasity.com/core-concepts/audiences-reverse-elt/pushing-audience-data-to-targets/klaviyo/target-endpoint-documentation.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.