---
id: "integrations/attribution/reference/asapty"
title: "Asapty Event Delivery Reference"
description: "Use this page as a readable reference for the event delivery request RevenueCat sends to Asapty. For setup steps, see Asapty."
permalink: "/docs/integrations/attribution/reference/asapty"
slug: "docs/integrations/attribution/reference/asapty"
version: "current"
original_source: "docs/integrations/attribution/reference/asapty.mdx"
---

> **AI agents:** This is the Markdown version of a RevenueCat documentation page. For the complete documentation index, see [llms.txt](https://www.revenuecat.com/docs/llms.txt).

Use this page as a readable reference for the event delivery request RevenueCat sends to Asapty. For setup steps, see [Asapty](https://www.revenuecat.com/docs/integrations/attribution/asapty).

RevenueCat sends Asapty events as a GET request with top-level query parameters and a compact, URL-encoded `json` parameter. This page shows the same request in a readable shape so you can understand what appears in Customer History.

| Delivery type | Required identifiers |
| :------------ | :------------------- |
| **Asapty MMP events** | Asapty ID and configured event name. RevenueCat also requires customer-level Apple Ads attribution data before creating a delivery attempt. |

## Example event delivery request

The `json` value is shown as an object for readability. In the actual GET request, RevenueCat sends it as a compact string query parameter.

```json
{
  "params": {
    "source": "revenuecat",
    "asaptyid": "<asapty_id>",
    "event_name": "<configured_event_name>",
    "conversiondate": <event_timestamp_ms>,
    "campaignid": "<apple_ads_campaign_id>",
    "adgroupid": "<apple_ads_ad_group_id>",
    "keywordid": "<apple_ads_keyword_id>",
    "ad_id": "<apple_ads_ad_id>",
    "claim_type": "<apple_ads_claim_type>",
    "install_time": <first_open_timestamp_ms>,
    "json": {
      "revenue": "<usd_revenue>",
      "af_currency": "USD",
      "transaction_id": "<transaction_id>",
      "original_transaction_id": "<original_transaction_id>",
      "purchase_date": <purchase_timestamp_ms>,
      "environment": "PRODUCTION",
      "store_country": "<store_country>",
      "profile_country": "<apple_ads_country_or_region>"
    }
  }
}
```

## RevenueCat source to Asapty request mapping

| Asapty request element | RevenueCat source and behavior |
| :--- | :--- |
| Endpoint | Sends `GET` requests to Asapty's MMP events endpoint. |
| `source` | Sends `revenuecat`. |
| `asaptyid` | Sends the Asapty ID configured in RevenueCat. |
| `event_name` | Sends the configured Asapty event name for the RevenueCat event. Events with no configured name are not sent. |
| `conversiondate` | Sends the RevenueCat event time in milliseconds. |
| `campaignid`, `adgroupid`, `keywordid`, `ad_id` | Sends Apple Ads campaign, ad group, keyword, and ad identifiers from the customer's stored Apple Ads attribution data. These are customer-level attribution fields, not transaction-level attribution decisions. Values are stringified. Blank values and Apple's `-1` sentinel are omitted. |
| `claim_type` | Sends Apple's raw Apple Ads claim type, such as `Click` or `Impression`, when available. |
| `install_time` | Sends the customer's first-open time from the Apple Ads attribution context. This is not the Apple ad click time. |
| `json.revenue`, `json.af_currency` | Sends gross revenue as a two-decimal USD string and `USD` as the currency. |
| `json.transaction_id`, `json.original_transaction_id`, `json.purchase_date` | Sends RevenueCat transaction identifiers and purchase time when available. |
| `json.environment` | Sends `PRODUCTION`. Asapty only receives production events because RevenueCat filters out sandbox purchases before delivery. |
| `json.store_country` | Sends the store country from the RevenueCat event as an ISO 3166-1 alpha-2 code when available. |
| `json.profile_country` | Sends the Apple Ads country or region as an ISO 3166-1 alpha-2 code when available. |
| Success response | Treats the request as successful only when Asapty returns HTTP `200` and `result.status` is `OK`. |

## Delivery requirements

RevenueCat sends Asapty events only for iOS App Store production purchases from customers with stored Apple Ads attribution data. Apple Ads attribution is stored on the customer and attached to eligible Asapty event deliveries; it doesn't attribute each individual transaction. Events are skipped when the customer doesn't have Apple Ads attribution data, the event is sandbox, the Asapty ID is missing, or the event name is not configured.