Get attributed results by Device UUID.
The Attribution Result API can receive AIRBRIDGE-API-KEY and AIRBRIDGE-SDK-TOKEN as authorization headers. When using AIRBRIDGE-API-KEY, use the API Token, and when using AIRBRIDGE-SDK-TOKEN, use the SDK Token.
An example of the call is shown below.
curl -H "Authorization: AIRBRIDGE-API-KEY {API-TOKEN}" https://api.airbridge.iohttps://api.airbridge.io/attribution-result/v1/apps/{app_name}/mobile-app
Get attribution results for mobile devices using device_uuid
可以指定用于 API 请求和结果返回的语言。遵守 ISO-639-1 格式。
表示资源的媒体类型。默认使用 application/json。
用于 API 请求的键值。参阅 密钥的生成及查询方法 来获取该键值。
Airbridge App 名称（App Name）。
Device UUID from Android or iOS.
This is the device UUID obtained through the app SDK. Please refer to the guides below to learn how to get it for each OS.
curl -X GET 'https://api.airbridge.io/attribution-result/v1/apps/{app_name}/mobile-app?device_uuid=f3fab994-baea-4b52-b190-5f023b6ae638' \
-H 'Accept-Language: ko' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer {AIRBRIDGE-API-TOKEN}'If no attribution result is found, the API returns a 204 No Content response. This indicates that the request was valid, but no matching attribution data exists.
{
"at": "2023-01-01T09:30:00.123Z",
"data": {
"attributedTerm": null,
"attributedAdGroup": "TEST_ADGROUP",
"attributedChannel": "website",
"attributedContent": null,
"attributedCampaign": "TEST_CAMPAIGN",
"attributedAdCreative": "TEST_ADCREATIVE",
"attributedSubPublisher": null,
"attributedSubSubPublisher1": null,
"attributedSubSubPublisher2": null,
"attributedSubSubPublisher3": null
}
}{}{
"result": "Invalid device_uuid"
}{
"result": "invalid authorization header"
}Was this helpful?