<!-- https://docs.youtarget.com/advertiser/en/troubleshooting/no-conversions.html -->

# Conversions are not coming in

> Why conversions from your tracker do not show up in the dashboard and how to find where the postback gets lost.

Start with the postback log in your tracker: the platform's response to the postback is the main clue. A conversion usually appears in **Conversions** → **Events** within a minute. If it arrived right after the click, it can take up to 10 minutes.

## 1. What the platform responded

**How to check:** find the postback in the tracker log and look at the response code.

- **400**: the platform rejected the postback. The reason is in the response text, see the table below.
- **200**: the postback was accepted for processing. This does not yet mean the conversion was counted: go to check 2.
- **No response**, or the postback was not sent: check in the tracker that the postback for the source is on and that the link from the **Integration code** window is pasted in full.

| Response text | Cause | Fix |
| --- | --- | --- |
| `invalid payout` | The payout is empty, uses a comma (`1,5`), or an unreplaced macro arrived instead of it | The payout must be a number with a dot: `1.5`. Check the payout macro in the integration settings |
| `invalid uuid format` | `click_id` does not look like a click ID: the tracker did not replace the macro or sent its own value. Or `postback_id` is corrupted | Check that the tracker passes the click ID from the link and that the postback link is copied in full |
| `invalid currency code` | The `cur` parameter is missing or does not contain a currency code | Edit the integration and select **Conversion currency**, then update the link in the tracker |
| `unknown conversion type` | The `ct` parameter has a typo: no such conversion type exists | Copy the link from the **Integration code** window again |

## 2. The click reached the tracker with the click ID

If the platform responded 200 but there is no conversion, the postback most often did not find the click.

**How to check:** open the campaign or creative link. It must contain the `{click_id}` macro, and the tracker must return this value in the postback unchanged.

**How to fix:** add `{click_id}` to the campaign's **Target URL** or to the creative's **Target URL**. For the list of macros, see the [Macros](../reference/macros.md) reference.

A conversion counts only if it arrives no later than 60 days after the click.

## 3. The conversion was not dropped as a duplicate

**How to check:** open the integration in **Conversions** → **Integrations** and look at the **Accept duplicate conversions** toggle.

**How to fix:** if the toggle is off, the platform counts only the first conversion per click and conversion type. The payout does not matter. If the conversion type is not set, the platform counts only one conversion per click. Set **Conversion type** in the integration or turn on the toggle.

## 4. The integration was not deleted

The platform responds 200 to postbacks for a deleted integration but does not show the conversions.

**How to check:** find the integration in the list on the **Integrations** tab.

**How to fix:** if it is not there, create a new one and replace the link in the tracker. Changes to an integration, such as a new conversion type, take effect within 15 minutes.

## 5. Check the date range

**How to check:** on the **Events** tab, check the period at the top of the page and find the conversion: paste its `click_id` into the **Search** field in full, all 36 characters. A partial ID finds nothing.

- A postback from the tracker appears with the date and time it was processed, in Moscow time (UTC+3).
- A conversion uploaded from a file appears with the date of the **click**, not of the upload.

## Test conversion

To check the whole setup, go to the **Conversion Check** tab, select a campaign and a creative, open the link and complete the target action on the site. The test link fills in only `{click_id}`, `{campaign}`, `{creative}` and `{cpc}` in the URL and works for 7 days. A test conversion looks like a regular one in **Events**.

## If you uploaded a file

- The "Changes successfully saved" message means the file was accepted, but it does not confirm that the conversions matched their clicks. Check them on the **Events** tab.
- If the file has at least one invalid row, the platform rejects the whole file. Errors such as "Invalid click_id format (UUID expected)" and "Empty values in columns …" tell you what to fix.
- Columns: `click_id`, `payout`, `cur`. The payout must be zero or more, with a dot.

> [!NOTE]
> The platform counts all received conversions as approved. Do not send a postback for rejected or pending conversions: the `event_type` parameter in the link does not change this.

## Still not working

Contact your manager: their contacts are under **Manager** in the left menu. Include the integration's `postback_id`, the conversion's `click_id` and the time the tracker sent the postback.
