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

# Target Endpoint Documentation

## Overview

The Daasity Audience feature uses the [Offline User Data Job](https://developers.google.com/google-ads/api/fields/v14/offline_user_data_job) that is part of the [Google Ads Reports API](https://developers.google.com/google-ads/api/fields/v14/overview) to load and process user data that can be used to create a custom audience in Google Ads.

## Offline User Data Job

Daasity uses the output from the report / query to generate a file and then loads this into Google Ads using this endpoint

* Endpoint: <https://developers.google.com/google-ads/api/fields/v14/offline_user_data_job>
* Frequency: Daily (available to run On-Demand via the UI)

| Daasity UI Section | Daasity Property | Google Ads Property |
| ------------------ | ---------------- | ------------------- |
| User List Setting  | List             | user\_list          |
| Data Mapping       | Source           | properties          |


---

# 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:

```
GET https://help.daasity.com/core-concepts/audiences-reverse-elt/pushing-audience-data-to-targets/google-ads/target-endpoint-documentation.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.