이벤트 전송

post https://api2.appsflyer.com/inappevent/{app_id}

To properly measure installs with AppsFlyer, it is required that
the following API is made on the app's first launch

⚠️
JSON payload limitation JSON payload size: up to 1KB
Rate limitation POST limitation volume: 60,000 POSTs per minute. To increase this limit, contact your CSM

📘
Encode URLs - Encode (percent) code reserved characters before forming the method URL.

FAQ

What if I can't send a device identifier?

You may be unable to send an identifier for a reason out of your control. For example, because the user has limited ad tracking (LAT) or uses iOS 14 and did not give ATT consent.

Not sending an advertising ID/device identifier can result in:

Postback issues: The media source receives the postback but without a device identifier. Therefore, the media source can't associate it with a user.
Audience segmentation and rule failure: Audience rulesets require identifiers. The recommended practice is to send a device ID or customer user ID for according to the ID type your ruleset uses for every S2S event. However, if AppsFlyer identifiers have been sent via other means (SDK or a past S2S event), new in-app events are matched to the correct users even if no identifiers are sent with the events.

language

인증

헤더

여기에서 요청을 시작하고 응답을 보려면 Try It!를 클릭하십시오!