> 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/attentive/target-endpoint-documentation.md).

# Target Endpoint Documentation

## Overview

The Daasity Audience feature uses the Attentive [Custom Attributes endpoint](https://docs.attentivemobile.com/openapi/reference/tag/Custom-Attributes/) to update a subscriber and the [Custom Events endpoint](https://docs.attentivemobile.com/openapi/reference/tag/Custom-Events/) to add an event to a subscriber.  Daasity splits the list of subscribers from the Audience Source into individual records and makes an API call to Attentive for that specific subscriber to be updated

## Custom Attribute API

Daasity updated an existing subscriber in Attentive based on the data provided by the Attentive Subscriber target

* Endpoint: <https://docs.attentivemobile.com/openapi/reference/tag/Custom-Attributes/#tag/Custom-Attributes/operation/postCustomAttributes>
* Frequency: Daily (available to run On-Demand via the UI)

| Daasity UI Section | Daasity Property | Attentive Property                          |
| ------------------ | ---------------- | ------------------------------------------- |
| Data Mapping       | phone            | phone                                       |
| Data Mapping       | email            | email                                       |
| Data Mapping       | Source           | Property Name from Data Mapping Destination |

{% hint style="danger" %}

* You must have "phone" or "email" in your data mapping in order to match to an existing subscriber
* You can only add custom attributes to subscribers that already exist in Attentive and are opted-in to email or SMS
  {% endhint %}

## Custom Event API

Daasity pushes a new event into each subscriber at Attentive based on the data provided by the Attentive Events Target

* Endpoint: <https://docs.attentivemobile.com/openapi/reference/tag/Custom-Events/#tag/Custom-Events/operation/postCustomEvents>
* Frequency: Daily (available to run On-Demand via the UI)

| Daasity UI Section | Daasity Property | Attentive Property |
| ------------------ | ---------------- | ------------------ |
| General            | Event Name       | type               |
| Data Mapping       | phone            | phone              |
| Data Mapping       | email            | email              |
| Data Mapping       | Source           | properties         |

{% hint style="danger" %}

* You must have "phone" or "email" in your data mapping in order to match to an existing subscriber
* You must specify a type for the event
* You can push events for any Subscriber
  {% 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/attentive/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.