> For the complete documentation index, see [llms.txt](https://daton-sarasanalytics.gitbook.io/daton/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daton-sarasanalytics.gitbook.io/daton/faqs/api-keys/criteo-client-id-and-secret.md).

# How to create Criteo API User and generate Client Id and Client Secret

Help documentation to create Criteo API User and generate Client Id and Client Secret and to use them to create integration on Daton

Follow the below instructions for create your Criteo Client Id and Secret

* Sign in to Criteo at using your  Criteo login credentials.
* Expand the menu and click on **Team** under **Settings**

![Navigate to Criteo settings](https://15515196-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LbJ1eMq5M51cIpU163R%2F-LqkA4dH5yhfQmowwWGH%2F-LqkAxxjTHNkw6Ht9m8T%2FCriteo1.jpg?alt=media\&token=d35f9673-aee4-4337-aa42-1c7ba0afdf26)

* Click on **Create New User** button under **API Users - REST API** list

![Add new Criteo API user](https://15515196-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LbJ1eMq5M51cIpU163R%2F-LqkA4dH5yhfQmowwWGH%2F-LqkBN2z7eFbm39TS8lK%2FCriteo1.5.jpg?alt=media\&token=0ea349ee-bd52-447b-aeaa-998cc97099d6)

* Enter an mail address (one who integrates Criteo on Daton) and select role as **View Only.** Client Id and Secret will be generated when you hit the **Add User** button. Copy the Client Id and Secret and save it someplace safe as secret will not be displayed again. You are required to provide these details while integrating Criteo on Daton.&#x20;

![](https://15515196-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LbJ1eMq5M51cIpU163R%2F-LqkA4dH5yhfQmowwWGH%2F-LqkCYIyRs9ig2XCnZS4%2FCriteo2.jpg?alt=media\&token=768d4866-8556-401c-b21d-2908b4f05654)

* Please note that Daton would require only read access to extract the data from Criteo.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://daton-sarasanalytics.gitbook.io/daton/faqs/api-keys/criteo-client-id-and-secret.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
