Skip to content

Conversion rejection

The conversion rejection endpoint lets advertisers send a server-to-server request to Integr8 to reject a conversion that was previously approved, or to update the rejection reason on an already-rejected conversion. Use it when fraudulent or invalid conversions are detected after the initial attribution.

https://INTEGRATION_DOMAIN/?new_rejected_reason=REASON&transaction_id=TRANSACTION_ID
Parameter Required Description
transaction_id Yes The unique ID of the conversion to reject
new_rejected_reason Yes The rejection reason code, for example fraud, chargeback, or duplicate
Conversion state Result
Approved Status changes to Rejected with the supplied reason.
Already Rejected Rejection reason is updated to the new value.
transaction_id not found No action taken, no error returned.

Offer-level rejection URL is tied to a single offer:

  1. Go to Offers > Offers Management and open a specific offer.
  2. Select Revenue & Payout and click the default Conversion row’s webhook icon to open its Postbacks tab.
  3. Select Reject Conversion in the left navigation.
  4. Review the tracking domain and rejection parameters, then click the output URL to copy it.

The offer’s Overview > Conversion Tracking accordion also provides Reject Conversion. For a custom event, open its row’s webhook action and choose Reject Event on the Event page.

Global rejection URL works for every offer in the account:

  1. Go to Offers > Global Tracking.
  2. Select Conversion Global Postback, then Reject Conversion in the left navigation.
  3. Review the domain and parameters, copy the URL, and share it with the advertiser.

No copyable URL is shown when the tracking domain is missing or invalid. Generating the URL does not send a rejection request.

The global URL is the better default for advertisers running multiple offers; one URL handles rejections across every offer without generating separate URLs.

  • Share the rejection endpoint only with trusted advertisers.
  • All requests must use HTTPS.
  • Watch postback logs for unexpected rejection patterns.
  • There is no undo for status changes made via this endpoint. Confirm the integration is correct before sharing the URL.