How to Debug Synthetic Users

How to Debug Synthetic User

Follow the steps below to verify that Synthetic User attribution is working correctly for your container.


1. Log in to the DCP

Open the DCP and select the container you want to test.


2. Check the Conversion Tag Setup

Ensure the container includes at least one conversion tag that uses the variable Synthetic User Click-ID in the Essential Mode Values column. This is required for proper Synthetic User attribution.


3. Confirm the Campaign Parameter

Navigate to the Settings tab of the Synthetic User Model. Identify the Campaign URL Parameter used for this model (e.g., utm_campaign). You will need this in a later step.


4. Start a Preview

Go to Publish, select your container, and start a Preview Session.


5. Open the Debug URL as a New User

Copy the generated Debug URL and open it in a private/incognito window. This ensures you start with a clean, unrecognized user.


In the preview mode, decline consent. Synthetic User prediction is explicitly designed for non-consented traffic.


7. Add Click ID and Campaign to the URL

Modify the URL to include:

  • a click ID you want to test

  • the campaign identifier configured in Step 3

Example:

Make sure the campaign identifier exactly matches the value defined in your Synthetic User Model.


8. Trigger Events to Collect Predictor Data

Perform a few interactions (page views, button clicks, etc.) so the system can collect enough predictor data. This data is used only for model prediction and is deleted after prediction.

The predictor data is not visible in the preview or debug monitor, so you need to perform a few interactions on the website to generate the necessary data.


9. Repeat for Multiple Test Users

Repeat Steps 5–8 using:

  • the same campaign identifier

  • different click IDs

This allows you to simulate multiple Synthetic Users under the same campaign.


Perform a conversion as a non-consented user. If everything is configured correctly, the system will:

  • replace the real click ID with the Synthetic User Click-ID

  • attribute the conversion to the Synthetic User

This confirms that Synthetic User attribution is working as expected.

Last updated

Was this helpful?