How Tracking Works

When a user starts an offer, Besitos and the advertiser's tracking systems work together to attribute the user's activity. As the user completes the applicable activity, Besitos records conversions and makes the results available through reporting, postbacks, and API.

Tracking and conversion behavior varies by offer type. Games use installs and in-app events, deals use qualifying actions, and surveys use survey qualification and completion. When troubleshooting an issue, start with the offer type to identify the applicable tracking or qualification flow.

The tracking process can vary by offer and integration method. Understanding the basic journey can help you plan your integration, know what to test, and communicate more effectively with the Besitos team when something doesn't work as expected.

Tracking depends on data being recorded and shared accurately between your platform, Besitos, game studios, and attribution providers (MMPs). Each has its own systems, rules, maintenance, and uptime, so delays or gaps can sometimes occur even when your integration and device settings are configured correctly.

Because tracking involves multiple systems, what happens in one part of the journey can affect what you see in another. Besitos works with partners to investigate tracking issues, recover missing activity where possible, and improve the reliability of the overall tracking experience.

At a high level, a user's activity follows this path:

Click → Redirect → Install or Action → Attribution → Event or Goal → Conversion → Postback → Reward

Not every offer type follows the same path. For example, a game may require an install and multiple goals, while a deal uses a different qualifying action, and a survey requires completion.

The key is that the user's activity must stay connected to the correct offer and user throughout the journey.

The user selects an offer.

The click initiates the tracking flow and associates the applicable user and offer information with the activity.

Where to verify: Offer Wall and Traffic reports, where applicable.

The user is sent through the Besitos tracking URL before continuing to the advertiser or offer destination.

The tracking flow associates information such as the partner user ID, offer ID, segment information, and applicable device identifiers with the click.

Where to verify: Besitos records the click but doesn't expose it as a standalone checkpoint.

The user completes the action required to continue the offer. For games, this typically means installing the game through the offer flow.

Users who install through a different path, such as searching for the game in an app store, may not be attributed to the offer.

For deals, the qualifying action may be signing up or making a purchase.

Where to verify for games: After a tracked install, the game can appear in My Games for iFrame partners or in the in-progress state in the API experience for API partners. It should also show up in the Offer Wall report for iFrame partners.

The advertiser's MMP associates the install with the original offer click and determines whether the activity qualifies for attribution.

For game offers, eligibility may depend on whether the user is new to the game.

Where to verify: Attribution itself isn't directly visible to the partner or Besitos in all cases.

See [User & Device Eligibility Checklist for Tracking] for applicable eligibility requirements.

The advertiser's MMP sends applicable activity to Besitos, such as an app launch, install, gameplay event, purchase, or other qualifying action.

For games, an install or activity such as launching the game may itself be a goal. Other games may require multiple goals or milestones.

Where to verify: Users can see applicable progress in their game experience. Partners can use the available reporting and conversion data.

See Troubleshooting Missing Installs or Game Progress when expected progress doesn't appear.

When Besitos receives a qualifying conversion event, it records the conversion and makes the resulting conversion data available through reporting and, where enabled, the Conversions Data API.

Where to verify:

See Reporting Verification & Reconciliation for guidance on comparing these sources.

When postbacks are configured, Besitos sends conversion information to the partner's webhook.

Postbacks are delivered as GET requests that contain the relevant conversion data. A successful delivery requires an HTTP 200 response.

Where to verify:

See Postback Data and Troubleshooting Postback Delivery Failures.

After the conversion is recorded, the reward enters the applicable validation process.

The user may see the reward as pending before it becomes available, depending on the applicable reward rules.

An advertiser may later reverse a conversion if it determines the activity doesn't qualify. Your system should use transaction_id to associate the reversal with the original conversion.

See Troubleshooting Missing, Incorrect, or Reversed Rewards for help with reward issues.

Several identifiers help connect a user's activity to the correct partner, offer, device, and conversion throughout the tracking journey.

These identifiers don't all appear at every stage or in every integration. Their availability depends on the offer and your integration method.

See User ID & Segmentation Guidelines, In-App Tracking Best Practices, and Postback Data for details about specific identifiers.

Several systems and people can be involved in the tracking process.

Exact responsibilities depend on your integration method and the offer type.

Your responsibilities depend on your integration method. In general, Besitos manages offer tracking and conversion processing, while your integration provides the user and offer connections needed to display offers and receive conversion information.

Besitos provides the offerwall and manages the offer experience and underlying tracking.

Your implementation is responsible for:

With an API integration, your team controls how Besitos offers are displayed and incorporated into your experience.

Your implementation is responsible for:

Besitos receives the applicable conversion/activity information through its own tracking and attribution systems and makes the resulting conversion data available to you.

Tracking and reporting work together, but they answer different questions.

Verify both before launch.

See Integration Smoke Test and Reporting Verification & Reconciliation to learn how to verify your integration.

When troubleshooting tracking, identify the last confirmed event and the first missing event. Then use the troubleshooting article for that stage.

For example:

Identifying the first missing or incorrect checkpoint helps you focus your investigation.

See Troubleshooting Missing Installs or Game Progress, Troubleshooting Missing, Incorrect, or Reversed Rewards, or Troubleshooting Postback Delivery Failures for technical details on each checkpoint and help resolving a specific issue.

You don't need to understand every technical detail of tracking to implement and succeed with Besitos.

The most important things to remember are: