> 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/configure-your-advertising-tools.md).

# Configure your advertising tools

### What this step accomplishes

Once your Synthetic Users model is published and in training, you need to tell each advertising tool in your JENTIS setup how to work with Synthetic Users. This involves three configuration changes per tool:

* [ ] Enabling Essential Mode on the tool, which allows JENTIS to fire the tool for non-consenting users (using only privacy-compliant, modeled data).
* [ ] Mapping the click ID variable so that modeled conversions include a valid click ID from the Synthetic Users segment pool instead of the original user's (non-existent) click ID.
* [ ] \[For Google Ads] Setting Google Consent Mode parameters to indicate positive consent to the ad platform. This is necessary because Synthetic Users data is decoupled from the original non-consenting user — the modeled conversion is a new, privacy-compliant signal that the ad platform should accept and process normally. The consent mode signals confirm that the data being sent has been appropriately processed.

### Shared prerequisite: Legal Hub vendor configuration

Before configuring any individual advertising tool, verify this setting for each tool vendor:

Navigate to Legal Hub → Vendors in your JENTIS dashboard. For each advertising vendor you plan to use with Synthetic Users (Google, Meta, Microsoft), ensure the consent setting is set to "Consent Enabled (Essential Mode)".

<figure><img src="/files/JOewiVamlAndprM1UNDT" alt=""><figcaption></figcaption></figure>

This must be done once per vendor. After this, you can stay in said vendor’s settings and proceed to the platform-specific configuration:

→ [Configure Google Ads for Synthetic Users](/jentis-dcp-elements/synthetic-users/configure-your-advertising-tools/configure-google-ads-for-synthetic-users.md)

→ [Configure Meta Ads for Synthetic Users](/jentis-dcp-elements/synthetic-users/configure-your-advertising-tools/configure-meta-ads-for-synthetic-users.md)

→ [Configure Microsoft Ads for Synthetic Users](/jentis-dcp-elements/synthetic-users/configure-your-advertising-tools/configure-microsoft-ads-for-synthetic-users.md)

<br>


---

# 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://docs.jentis.com/jentis-dcp-elements/synthetic-users/configure-your-advertising-tools.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.