Skip to content

Server-side Conversions API — Business plan, Phase 2 (coming soon)

For orders confirmed on your server (or from a payment webhook), send the conversion with the click_id you captured:

For orders confirmed on your server (or from a payment webhook), send the conversion with the click_id you captured:

curl -X POST https://api.urlcrop.com/v1/conversions \
  -H "Authorization: Bearer $URLCROP_API_KEY" -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-SHOP-10045" \
  -d '{
    "event": "purchase",
    "click_id": "clk_01JB59XQ0P1N2M3L4K5J6H7G8F",
    "order_id": "SHOP-10045",
    "value": { "amount": 249900, "currency": "INR" },
    "coupon_code": "PRIYA10",
    "customer": { "external_id": "cust_41", "email_hash": "5d41402abc4b2a76b9719d911017c592ab1c7a6f2c3d4e5f60718293a4b5c6d7" }
  }'

Response 202 { "id": "cnv_…", "object": "conversion", "status": "queued" }. Attribution tries click_id, then coupon_code, then hashed customer identifiers (90-day window). (event, order_id) is deduplicated for 7 days. Up to 500 at once via POST /v1/conversions/batch. Cancelled orders: DELETE /v1/conversions/{id} marks them rejected.