In-app tracking helps record user activity so progress can be attributed to the correct offer and rewards can be delivered. When tracking permissions are declined, disabled, or interrupted, activity may not be attributed correctly—even if the user completes the required goals.
Tracking behavior differs between iOS and Android. On iOS, users may be prompted to allow app tracking through Apple's App Tracking Transparency (ATT) framework. You can explain why you use tracking, but you should not promise or offer a reward or other incentive in exchange for accepting tracking.
On both platforms, device settings, privacy tools, connectivity, and how users start and complete an offer can affect attribution.
What tracking does
Tracking allows apps and websites to record activity related to installs, gameplay, and goal completion.
For game and deal offers, device advertising identifiers such as IDFA on iOS and GAID on Android can help the advertiser's measurement partner attribute installs and in-app activity to the original offer click.
Your implementation should make identifiers available as required by your integration. See What are IDFA and GAID? for implementation details.
Tracking helps Besitos and advertisers:
Confirm installs and other qualifying activity
Record progress toward goals and milestones
Verify completion of earning requirements
Attribute eligible activity to the correct offer
If required tracking information isn't available, we may not attribute activity successfully.
Why tracking matters
Tracking helps connect a user's activity to the offer they started so their progress and qualifying activity can be recognized.
Without the expected tracking signals:
Installs may not be attributed to the offer.
Game progress may not be recorded.
Completed goals may not generate a conversion.
Rewards may be delayed or not credited.
Tracking also helps provide a more consistent user experience by allowing your app to display progress and offer status based on the activity recorded by Besitos.
Common causes of tracking issues
Most tracking issues fall into a few categories.
Tracking and privacy settings
iOS users decline the App Tracking Transparency prompt.
Device or app settings restrict tracking or advertising-ID access.
VPNs, proxies, privacy tools, or other network settings interfere with attribution.
Ad blockers or browser extensions interfere with the offer or tracking flow.
Device and connection factors
Users switch devices after starting an offer.
Users install on one device and play on another.
Internet connectivity is unstable or interrupted.
Users participate on unsupported, rooted, jailbroken, or virtual devices.
Eligibility and installation source
The user starts or installs the offer outside the approved flow.
The user previously installed, signed up for, or played the game.
The user doesn't meet the offer's eligibility requirements.
Best practices
You can reduce tracking issues by setting clear expectations and avoiding interference with the offer flow.
Explain tracking clearly
Explain that tracking records progress and verifies completed goals.
Tell users that tracking should remain available throughout the offer.
For iOS, explain why your app requests tracking permission before showing the ATT prompt.
Don't promise or offer rewards, discounts, or other incentives in exchange for accepting iOS tracking permission.
Minimize interference
Advise users to avoid VPNs, proxies, and privacy tools while participating in offers.
Let users know that ad blockers or browser extensions may interfere with tracking.
Recommend a stable internet connection while completing offers.
Don't modify or interrupt the offer flow in ways that could prevent tracking information from being passed.
Reinforce device consistency
Instruct users to install and complete offers on the same device.
Tell users to start the offer through the provided offer link or CTA.
Don't direct users to install the game separately from the offer flow.
Set eligibility expectations
Clearly state that users must meet the offer's eligibility requirements.
Explain that previous installs, sign-ups, or gameplay may make a user ineligible for a game offer.
Avoid suggesting that users can switch devices or accounts to participate in the same offer.
Pass required tracking information
For API partners and partners using the iFrame in a mobile app, pass available IDFA or GAID values at click time as required by your integration.
See What are IDFA and GAID? for the requirements for each integration type.
Platform-specific guidance
Tracking behavior and device settings differ between iOS and Android.
For troubleshooting specific device settings, see [User & Device Tracking Requirements].
Key takeaway
The best way to reduce tracking issues is to make the expected offer flow clear and avoid interfering with it.
Tell users why tracking matters, help them understand the eligibility and device requirements, and make sure your implementation passes the required tracking information. These practices can reduce missing installs, progress, and rewards while providing a more predictable user experience.