Skip to main content

The Conversion Error Log

View error logs to identify and understand issues during conversion creation.

Written by Trackdesk Team

The conversion error log lists every failed conversion request that hasn't been deleted, newest first. Use pagination to browse older entries.

Navigate to Tools β†’ Logs β†’ Conversion Error Log to open the log.

Only failures from the conversion-creation HTTP endpoint and the JS pixel are logged here. CSV-import failures are shown inline in the import preview, not in this log. Bulk status changes and webhook delivery failures are tracked separately.

Error statuses

Each row carries one of two statuses, shown as a colored chip:

  • Error (red): the conversion request was rejected for a reason on the caller's side (invalid identifiers, missing data, blocked traffic, etc.). The side modal shows a curated, human-readable description; the most common reasons are listed below.

  • System error (orange): something inside Trackdesk failed while processing the request. The side modal shows the raw internal error message so you can include it when contacting support.

Side modal contents

Clicking a row opens the side modal with three sections:

  • Details: timestamp, status, error message, CID, External CID.

  • Related: the linked offer and affiliate, when the CID can be matched to a tracked click.

  • Request parameters: the raw JSON the conversion request was sent with, useful for reproducing the issue against your integration.

Error messages

  • conversion source not found: the source ID (CID) couldn't be matched to any affiliate, link, or click in the system.

  • conversion source with the external cid not found: the External CID couldn't be matched to any tracked source.

  • conversion source with the client not found: the External Client ID couldn't be matched to any tracked source.

  • conversion type not found: the conversion type code in the request doesn't exist in the system.

  • revenue origin not found: the revenue origin ID in the request is unknown.

  • revenue origin does not belong to offer: the revenue origin used in the request belongs to a different advertiser than the offer's.

  • offer not active: the offer is paused, inactive, or otherwise not accepting conversions.

  • conversion already exists: the conversion request is a duplicate. Either the offer is non-recurrent and a conversion already exists for this click, or the External ID matches one already in the system.

  • source disabled: the affiliate (or their source) is disabled.

  • revenue and payouts for conversion type not configured: the conversion type exists in the system but is not set up on this offer's payouts.

  • missing conversion amount: the conversion type uses a percentage payout but the request didn't include an amount.

  • no targeting matched in offer revenue and payout groups: the offer uses targeting rules and the click's parameters don't match any of them.

  • group with currency not configured: the conversion's currency isn't configured in the offer's payout groups.

  • conversion limit reached: the offer (or affiliate / source cap) reached its maximum number of conversions.

  • no valid coupon code: a coupon code was required but the request didn't include a valid one.

  • ip address not allowed: the request came from an IP that isn't in the offer/tenant/advertiser IP allowlist.

  • currency not supported: <currency code>: the conversion's currency isn't enabled for this tenant. The actual currency code is appended to the message.

Cleaning up old errors

You can delete error entries older than a chosen date directly from the log. This is useful after fixing an integration so the log only shows ongoing issues. Note that there is no automatic retention; entries stay until you delete them.

Did this answer your question?