> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/jentis-dcp-elements/synthetic-users/quick-start-guide.md).
# Quick-start guide
Go through this checklist before starting the Synthetic Users configuration process:
* [ ] JENTIS tracking (tracking code, DNS A record) configured
* [ ] CMP bridge connected
* [ ] Essential Mode enabled for connector
* [ ] Ad tool configured
This step list walks you through the entire Synthetic Users setup from start to finish. Each step links to its detailed documentation page. The total implementation time (excluding the model training period) is approximately 1–2 hours of active configuration work, spread across several sessions.
### Step 1 — Verify your prerequisites (5 minutes)
Confirm that JENTIS server-side tracking is active, Essential Mode is enabled, your CMP is connected, and at least one advertising tool is configured server-side. → See \[What Are Synthetic Users? — “What you need before starting“ section]
### Step 2 — Create your Synthetic Users model (10 minutes)
Navigate to the Synthetic Users section in your JENTIS dashboard, create a new model along with raw data collection tags, and publish it. The model will begin its data-gathering phase. → See \[Create and Configure Your Model]
### Step 3 — Wait for model training (\~14-21 days, no action required)
The AI model needs approximately 21 days of consented user data to identify behavioral patterns and build segments. You can monitor progress on the Synthetic Users dashboard. Sites with fewer than 300,000 sessions per month may need a bit more time!
### Step 4 — Configure your advertising tools (15–30 minutes per tool)
Once the model reaches READY status, configure each advertising tool (Google Ads, Meta Ads, Microsoft Ads) by mapping the click ID variable, and setting consent mode parameters. → See \[Configure Your Advertising Tools]
### Step 5 (Optional) — Test on a single campaign first
If you'd prefer to validate results before full rollout, you can configure Synthetic Users for a single advertising campaign first. → See \[[Test with a Single Campaign](/jentis-dcp-elements/synthetic-users/optional-test-with-a-single-campaign.md)]
### Step 6 (Optional) — Connect analytics tools
If you want to see Synthetic Users data in analytics platforms like GA4, you can activate click ID sharing on analytics tools as well. → See \[[Share Click IDs with Analytics Tools](/jentis-dcp-elements/synthetic-users/optional-share-synthetic-users-click-ids-with-analytics-tools.md)]
### Step 7 (Optional) — Debug and Preview Synth.User
When your configuration is ready you can preview it. Follow our guide on best practices how to identify Synth.Users is active. → See \[[How to debug Synthetic Users](/jentis-dcp-elements/synthetic-users/how-to-debug-synthetic-users.md)]
### Step 8 (Optional) — Access segmentation data via API
For developers who want to use segment assignments in custom applications or personalizations, a JavaScript API (on the JENTIS Server) is available. → See \[[Retrieve Synthetic Users Segmentation](/data-control/data-enrichment/retrieve-synthetic-users-segmentation.md)]
---
# 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://docs.jentis.com/jentis-dcp-elements/synthetic-users/quick-start-guide.md?ask=&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.
