Adset.ProAdset.ProKnowledge base
Home/Tracker/Postback

Postback

Postback is an HTTP request for transferring conversions between different systems.

Incoming Postback (from CPA)

URL for the partner network:

https://adset.pro/postback/?clickId={click_id}&status={status}&revenue={payout}

Request Parameters

Parameter

Required

Description

clickId

Yes

Click ID from the partner network

status

Yes

Conversion status (maps to internal events)

revenue

No

Payout amount (revenue)

currency

No

Payout currency (optional)

external_id

No

Conversion ID

accept_status

No

Deposit status (optional, see below)

hold_status

No

Registration status (optional, see below)

redep_status

No

Re-deposit status (optional, see below)

decline_status

No

Deposit cancellation status (optional, see below)

Status Mapping

Statuses are configured in the Partner Networks → Settings → Conversion Statuses section:

Field

Internal Event

Description

FTD (accept)

CPA_ACCEPT

First deposit

Re-Deposit (redep)

CPA_REDEP

Re-deposit

Registration (hold)

CPA_HOLD

Registration

Decline

CPA_DECLINE

Declined conversion

Trash

CPA_TRASH

Trash conversion

In the postback URL, the parameters accept_status, hold_status, redep_status, decline_status can explicitly indicate the corresponding status in the status parameter.

Re-Deposits

There are two ways to transmit Re-Deposit:

  1. Explicit status — the partner network transmits a separate status mapped to the redep field in the CPA settings. It can also be transmitted via a separate query parameter redep_status.

  2. Auto-detection — if a regular accept status is received, but there is already a successful deposit (CPA_ACCEPT) for the given clickId, the system will automatically reclassify the event to CPA_REDEP.

Deduplication of Conversions

By default, the system rejects duplicate conversions (same clickId + event type). Deduplication settings:

  • Accept duplicate conversions — allow accepting duplicates for selected types

  • Accept duplicates for — select conversion types for which duplicates are allowed (e.g., Deposit, Registration)

If external_id is transmitted, deduplication takes it into account: conversions with different external_id are not considered duplicates.

Scenario

externalId

Duplicates for type allowed

Result

1st redep for clickId

—

—

✅ Passes

2nd redep, same clickId

Same/no

No

❌ Duplicate

2nd redep, same clickId

Different

No

✅ Passes

2nd redep, same clickId

—

Yes

✅ Passes