Skip to content

Third-Party Rejection

What it detects

Advertisers and third-party fraud platforms sometimes identify invalid conversions — bots, duplicate installs, chargebacks — after the fact. The Third-Party Rejection filter lets those external systems pass rejection reasons back to Integr8 via postback, automatically marking conversions as rejected and attributing them with the reason provided.

How it works

When an external system identifies a conversion as invalid, it sends the rejection reason back to Integr8 by appending &third_party_rejected_reason=VALUE to the postback URL. Integr8 receives this signal, marks the conversion as rejected, and logs the reason for reporting and publisher accountability.

The filter must be enabled in your filter group settings before Integr8 processes the parameter.

Configuration

Step 1: Add the rejection parameter to your postback URL

In your offer or global postback URL, append the rejection reason parameter using the macro from your third-party system:

&third_party_rejected_reason={rejection_reason}

Replace {rejection_reason} with the actual macro your third-party system provides. For example, if your fraud vendor uses {fraud_signal}:

&third_party_rejected_reason={fraud_signal}

Step 2: Enable the filter in Integr8

  1. Navigate to Offers > Fraud Detection Groups.

  2. Select the filter group you want to configure.

  3. Go to the Conversion tab within the filter group settings.

  4. Enable Third-Party Rejection.

  5. Click Save.

What happens when triggered

When a postback arrives with a non-empty third_party_rejected_reason value:

  • The conversion is marked as rejected with fraud_reason: third_party_rejection.
  • The rejection reason string is stored and visible in Reports > Conversion and Events Report.
  • Publisher payouts for rejected conversions are not issued.

Standardize rejection reason values with your third-party system before going live. Consistent naming makes it easier to filter and group rejections in reports.