S2S Conversion

AdPriva supports server-to-server (S2S) postbacks for purchases, installs, signups or custom events.

Unlike cookies or client-side pixels (easily spoofed), every conversion in AdPriva is cryptographically linked to a valid click.

Why S2S Conversions?

  • Fraud-resistant → Blocks cookie stuffing, pixel spoofing and fake postbacks.
  • Privacy-first → Only proof IDs transmitted, no personal data.
  • Accurate → Server-side validation prevents tracking loss.
  • Compliant → Conversions tied to Consent Receipts, respecting user opt-ins.

How It Works

  1. ClickProof Generated → Created when a user clicks an ad.
  2. Conversion Event → Advertiser server records a purchase, signup or install.
  3. S2S Postback → Advertiser sends a signed payload to AdPriva’s API.
  4. Validation → HMAC signature, timestamp and click_proof_id are checked.
  5. ConversionProof Issued → Logged in the AdPriva Explorer.
  6. Settlement → Advertiser billed → Publishers and Users rewarded in stablecoins.

API Example

Request

POST /conversions
Content-Type: application/json
Authorization: Bearer YOUR_API_KEY

{
  "click_proof_id": "PRF_12345",
  "event": "purchase",
  "value": 49.99,
  "currency": "USD",
  "timestamp": "2025-09-25T14:12:00Z",
  "signature": "hmac_sha256_signature"
}

Response

{
  "conversion_id": "CNV_55555",
  "status": "verified",
  "proof_id": "PRF_12345",
  "explorer_url": "https://explorer.adpriva.com/CNV_55555"
}

Required Fields

  • click_proof_id → ID of the valid click.
  • event → Conversion type (purchase, install, signup, custom).
  • value → Monetary value (if applicable).
  • currency → ISO code (USD, EUR, etc.).
  • timestamp → UTC ISO timestamp.
  • signature → HMAC-SHA256 signature with your campaign secret key.

Generate campaign secret keys in the AdPriva Dashboard. Sandbox keys available for testing.

Fraud Protection

  • Replay Prevention → Each click can only generate one ConversionProof.
  • HMAC Signatures → Spoofed postbacks automatically rejected.
  • Consent Linkage → Conversions only logged if user consent exists.
  • Tamper Evidence → ConversionProofs batch-anchored on-chain.

With S2S conversions, AdPriva makes affiliate and performance marketing fraud-proof and privacy-preserving, so advertisers only pay for real outcomes.

{% @mermaid/diagram content="sequenceDiagram
participant U as User
participant P as Publisher Site/App
participant A as Advertiser Server
participant API as AdPriva API
participant V as Validation Layer
participant X as AdPriva Explorer
participant S as Settlement
U->>P: Clicks Ad
P->>API: Generates ClickProof (PRF_12345)
API-->>A: ClickProof ID returned
A->>API: Sends S2S Postback (purchase/signup/install)
API->>V: Validate (HMAC, timestamp, consent, linkage)
V-->>API: Conversion verified
API->>X: Logs ConversionProof
API->>S: Trigger settlement
S-->>P: Stablecoin payout (publisher)
S-->>U: Stablecoin reward (user)" %}