> 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/optional-test-with-a-single-campaign.md). # (optional) Test with a single campaign At this point you should have: * [ ] Completed the creation of your first Synthetic Users model * [ ] Configured at least a single connector that supports Synthetic Users If you'd prefer to validate Synthetic Users results before enabling it across all your campaigns, you can configure it for a single advertising campaign first. This lets you compare the performance of one campaign with Synthetic Users against your other campaigns without it, giving you concrete data on the impact. This approach is recommended when you want to demonstrate value to stakeholders before full rollout, when you're on a shared JENTIS account with multiple teams and want to prove the concept in your domain first, or when you simply want to build confidence in the modeled conversion numbers. \ How single-campaign setup differs The configuration process is identical to the full setup described in \[Configure your advertising tools], with one key difference: instead of enabling Synthetic Users on all tags for an advertising platform, you configure it only on the tags that fire for your chosen test campaign. In practice, this means creating a dedicated tag (or duplicating an existing one) for your test campaign with Essential Mode enabled and the Synthetic User Click ID mapped, while leaving your other campaign tag(s) with click ID fields empty. \ → [Configure Google Ads in JENTIS to test Synthetic Users with a single campaign](/jentis-dcp-elements/synthetic-users/optional-test-with-a-single-campaign/configure-google-ads-in-jentis-to-test-synthetic-users-with-a-single-campaign.md) → [Configure Meta Ads in JENTIS to test Synthetic Users with a single campaign](/jentis-dcp-elements/synthetic-users/optional-test-with-a-single-campaign/configure-meta-ads-in-jentis-to-test-synthetic-users-with-a-single-campaign.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/optional-test-with-a-single-campaign.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.