> For the complete documentation index, see [llms.txt](https://sdk-doc.tyrads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk-doc.tyrads.com/getting-started/tyrads-fraud-suite-v2-sdk.md).

# TyrAds Fraud Suite V2 (SDK)

To ensure optimal traffic integrity and maximize campaign perf, TyrAds employs a multi-layered security system for our SDK partners.

Fraud Suite v2 Documentation:

{% file src="/files/8kvtbEhAULRWjsY68WTa" %}

#### 1. The Two-Layer Defense

* Layer 1: User Risk Scoring (Proactive): An automated system that scores every user at the moment they enter the SDK. Using 200+ data sources (including device fingerprints, location, and multi-accounting patterns), it blocks "High Risk" users before they can engage with any offers.
* Layer 2: Anomaly Detection (Reactive): A machine-learning system that monitors in-game activity. If a user bypasses Layer 1 but exhibits abnormal behavior patterns, their progress is rejected in real-time.

#### 2. For Anomaly Detection Layer

Our system analyzes post-install event patterns. If a user’s behavior is flagged as non-human or anomalous, the system triggers an automatic rejection.

Standardized Lookback Rules:

* **14-Day Window**: All conversions are subject to a 14-day lookback window, aligning with industry MMP standards.
* **CPI Model**: If an anomaly is detected within 14 days, both the install and all associated events are retroactively rejected.
* **CPE Model:** The specific anomalous event is rejected, and the user is flagged to prevent all future payouts on that campaign.
* **Post-14 Days**: The initial install remains approved, but specific anomalous events are rejected and non-payable.

## Technical Integration (Rejected Postback Macros)

If you needed to be notified on the rejections to your platform, please do consult Tyrads team to setup a rejected type Postback URL  \[**especially for CPI campaigns where we retroactively reject the install together with the event and make the install non-payable as well]**

| Macros                | Description                                                                                                                                                                         | Example or Expected Value |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------- |
| `{conversion_status}` | The state of conversion                                                                                                                                                             | `rejected`                |
| `{reject_reason}`     | The rejection reason for the conversion                                                                                                                                             | `Anomoly%20Detection`     |
| `{conversion_id}`     | Unique ID of a specific conversion                                                                                                                                                  | `2563391781`              |
| `fraud`               | `true` when the conversion was rejected for a fraud reason (for example Anomaly detection, Purchase fraud). `false` for other rejections and for approved conversions.              | `(Boolean)true/false`     |
| `reversal`            | `true` only when an event we previously approved is now rejected. Deduct anything you credited for that `conversion_id`. `false` in every other case.                               | `(Boolean)true/false`     |
| `payable`             | `true` when the conversion is approved and has a payout greater than 0. `false` for rejected and flagged conversions. Use this, not `cost`, to decide whether a conversion is paid. | `(Boolean)true/false`     |

Example of suggested rejected postback URL:

{% tabs %}
{% tab title="Rejected Postback Format Example" %}
[https://your-api-endpoint.com/postback?id={conversion\_id}\&conversion\_status={conversion\_status}\&reject\_reason={reject\_reason}\&fraud={fraud}\&reversal={reversal}\&payable={payable}](https://your-api-endpoint.com/postback?id={conversion_id}\&status={conversion_status}\&reason={reject_reason}\&fraud={fraud}\&reversal={reversal}\&payable={payable}) + all existing macros setup in Ad Unit that is required
{% endtab %}
{% endtabs %}

***

Rejected postback Integration Checklist

* [ ] Ingest rejected type postback in your system if needed
* [ ] Map rejections using `conversion_id`&#x20;

{% hint style="warning" %}
**Do not reward the user on a rejected postback.** If it has `reversal=true`, also deduct what you credited for that `conversion_id`.
{% endhint %}

#### Handling rejected postbacks

A rejected postback always means the conversion is not paid (`payable=false`). Use `reversal` to tell whether you need to deduct:

| `reversal` | What it means                                                             | What to do                                                   |
| ---------- | ------------------------------------------------------------------------- | ------------------------------------------------------------ |
| `true`     | We approved this conversion earlier, so you may already have rewarded it. | Deduct what you credited for this `conversion_id`.           |
| `false`    | This conversion was never approved.                                       | Keep as a record. Do not reward the user. Nothing to deduct. |

`fraud=true` means our fraud checks rejected the conversion. `fraud=false` means another reason, for example Duplicate Event. In both cases, do not reward the user.

**CPI campaigns:** when we reject an install after it was approved, every event of that install gets its own rejected postback. The events we had approved come with `reversal=true`. Deduct each one by its `conversion_id`.

Example rejected postback URL:

`https://exampleURL.com?id={conversion_id}&conversion_status={conversion_status}&reject_reason={reject_reason}&fraud={fraud}&reversal={reversal}&payable={payable}`

For the full rules, see [Suggestion for postback handling ](https://sdk-doc.tyrads.com/getting-started/postback-payout-s2s-and-setup.md#suggestions-on-postback-handling).
