IDFA and GAID are device advertising identifiers that help the advertiser's measurement system attribute app installs and in-app activity to the original offer click.
Besitos supports both identifiers for native iOS and Android apps:
IDFA - iOS
GAID - Android
Passing the appropriate identifier at the time of the offer click can improve attribution accuracy, conversion tracking, and revenue performance.
Who needs to use IDFA or GAID
IDFA and GAID apply when you integrate Besitos into a native iOS or Android app.
They are supported for:
iFrame integrations - Games and Offers iFrame
API integrations - Games, Games International, Games User Data, Deals, and Deals User Data APIs
They aren't required for web-only integrations.
How IDFA and GAID work
Your native app reads the device's advertising identifier and adds it to the Besitos offer URL when the user clicks an offer.
Platform | Identifier | URL parameter |
iOS | IDFA |
|
Android | GAID |
|
Besitos uses the identifier as part of the tracking flow, which helps the advertiser's MMP match the user's install and activity to the original offer click.
iFrame integrations
For iFrame integrations, your native app must append the appropriate identifier to the iFrame URL when the user clicks.
iOS
https://wall.besitos.ai/v1/{partner_id}/{subscriber_id}?idfa=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXAndroid
https://wall.besitos.ai/v1/{partner_id}/{subscriber_id}?gaid=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXSee Games iFrame and Offers iFrame for the complete iFrame integration requirements.
API integrations
For API integrations, your native app must append the appropriate identifier to the url returned by the API before sending the user through the offer flow.
Games, Games International, and Deals APIs
iOS
https://wall.besitos.ai/api-redirect/{partner_id}/{offer_id}/{api_hash}?partner_user_id=YYY&sub_id=XXX&idfa=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXAndroid
https://wall.besitos.ai/api-redirect/{partner_id}/{offer_id}/{api_hash}?partner_user_id=YYY&sub_id=XXX&gaid=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Games User Data and Deals User Data APIs
iOS
https://wall.besitos.ai/redirect/{offer_id}/{subscriber_id}?idfa=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXAndroid
https://wall.besitos.ai/redirect/{offer_id}/{subscriber_id}?gaid=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXSee the applicable [API documentation] for complete integration requirements.
What happens on iOS
iOS users may be prompted to allow tracking through Apple's App Tracking Transparency (ATT) permission.
Your app should follow Apple's requirements when requesting permission. Do not promise or offer a reward in exchange for accepting tracking.
If a user declines tracking permission, the user can still participate in offers, but attribution and progress tracking may be affected.
What happens if I don't pass IDFA or GAID
Offers can still be displayed, and users can participate without these identifiers. However, missing device advertising identifiers may reduce the advertiser's ability to accurately match an install or in-app activity to the original offer click.
This can result in missing or delayed attribution, progress, conversions, or rewards.
Who is responsible for collecting the identifier
Your native app is responsible for:
Reading the device's advertising identifier.
Passing the identifier to the Besitos offer URL.
Adding it when the user clicks the offer.
Besitos does not collect the identifier from the device on your behalf.
Troubleshooting
If mobile offers aren't tracking as expected, verify that:
Your app is reading the appropriate advertising identifier.
You're using
idfafor iOS andgaidfor Android.The identifier is appended to the offer URL at the time of the click.
The user completes the offer on the same device used to start it.
iOS users have been given the appropriate tracking permission prompt.
The offer is started through the approved Besitos flow.
See In-App Tracking Best Practices and additional guidance.
FAQ
Do I need IDFA or GAID for every integration?
Do I need IDFA or GAID for every integration?
No. They are relevant to native mobile app integrations. They aren't required for web-only integrations.
Does Besitos collect IDFA or GAID?
Does Besitos collect IDFA or GAID?
No. Your native app is responsible for reading the device identifier and adding it to the offer URL.
Can users participate if they don't allow tracking on iOS?
Can users participate if they don't allow tracking on iOS?
Yes. Tracking permission isn't required to participate in offers. However, declining permission may affect attribution, progress tracking, and reward attribution.
Should I pass both IDFA and GAID?
Should I pass both IDFA and GAID?
No. Pass the identifier that applies to the user's platform: idfa for iOS or gaid for Android.
When should I add the identifier?
When should I add the identifier?
Add it to the offer URL when the user clicks the offer.
Does adding IDFA or GAID guarantee attribution?
Does adding IDFA or GAID guarantee attribution?
No. The identifiers help improve attribution accuracy, but successful attribution also depends on other eligibility, device, installation, and tracking requirements.