After your Integration Smoke Test passes, run a production tracking test with a real offer, an eligible test user, and an eligible physical device.
A production tracking test follows real user activity through installation, progress, conversion, and reward status. After you record the conversion, verify the result using the data and reporting available for your integration.
Production testing uses a real offer and can create real conversion and reward activity. Follow the steps carefully and record your test information in case you need to troubleshoot or escalate an issue.
Before You Start
Complete these steps before you begin your production test:
Pass the Integration Smoke Test.
Set up your production integration. Configure your postback, if applicable, and confirm your endpoint is live.
Coordinate with your Besitos Account Manager. Share your testing dates, number of testers, devices, and tester countries. Register each test user ID and wait for confirmation before testing.
Prepare your test environment. Assign one test user ID to each tester, use one test account per device, and confirm that your offer is available to the test user.
Review tracking requirements. Confirm that your test environment meets the User & Device Tracking Requirements.
Prepare your verification tools. Confirm that you have access to the reporting you need to verify the test.
Why Test Account Setup Matters
Besitos uses automated fraud-prevention checks to protect rewards for genuine users. New accounts, multiple accounts on one device, VPNs or proxies, and testing from unsupported countries can flag test activity.
Register your test accounts with your Besitos Account Manager before testing to help prevent your test activity from being blocked.
Wallet partners
This procedure is written primarily for iFrame and API partners because some verification steps involve postbacks or API retrieval. Wallet partners should complete the test using the end-user experience and applicable reporting, including planning the test, preparing the test user and device, running the offer, verifying the conversion, and verifying the reward. Skip any postback or API retrieval steps that don't apply to your integration.
1. Plan Your Test
Choose your offer and define what you expect to happen before you start.
Choose an Offer
For your first production test, choose an offer with an early, achievable conversion or goal. For games, a low-friction first goal is generally easier to test than one that requires extensive gameplay. When possible, choose a goal that doesn't require a purchase.
If you're testing a survey or deal, follow the applicable requirements for that offer type.
Choose Your Test User & Device
Use the User & Device Tracking Requirements to confirm that your test environment is ready.
Your test user and device should meet the offer's eligibility requirements before you begin.
Use a consistent user ID throughout testing. Keep the user ID you pass to the offer wall the same for the test user across sessions. Creating a new user ID for each click or session can affect reward tracking and make test activity harder to identify.
Record Your Test Information
Before starting the offer, record:
Offer name
Offer ID
Offer type
Platform
Required user/device eligibility
First conversion or goal you intend to complete
Goal ID, if applicable
Expected reward
Test start date and time
Timezone
Recording this information makes it easier to compare results and troubleshoot if something doesn't work as expected.
Define Your Expected Results
Know what you're looking for before you run the test.
User activity | Expected result |
Install or initial action | Activity is recorded for the test user. |
Progress or goal | The expected progress or goal is recorded. |
Conversion | The expected conversion is recorded. |
Reward | The expected reward is credited or shown as pending, depending on the applicable reward rules. |
2. Prepare Your Test User & Device
Use the User & Device Tracking Requirements to confirm that your test environment is ready.
Before you start, confirm that:
Your test user is eligible. The game must be new to the device—never installed or downloaded. Only new users are accepted, even if the tester has never played it or is using a different account.
Your device is eligible. Use a real physical device that meets the applicable platform requirements. Don't use emulators, simulators, headless browsers, or automated scripts unless your Account Manager has arranged testing for them.
Your tracking settings are ready. Complete the platform-specific tracking requirements, including turning off iCloud Private Relay on iPhone.
Your network is ready. Avoid VPNs and proxies when possible. If a tester is outside the US, contact your Besitos Account Manager before testing. VPNs don't change the tester's actual location and can trigger fraud-prevention checks.
Your integration passes the expected device identifiers, if applicable.
Do not begin the test until your user and device are confirmed eligible.
3. Run the Test
Once your user and device are ready, follow the normal user journey.
Important: The game must be new to the test device. Only new users are accepted. If the game has been downloaded or installed on the device before, don't use that device for the test.
Start the Offer
Open your Besitos experience as the test user and locate the selected offer. For API integrations, retrieve the offer via your API.
Click the offer from the Besitos experience to begin the test. Do not search for the offer separately or start it from another source. The test needs to begin through the expected Besitos offer flow.
Record the time you started the offer and the time zone.
Complete the Install or Initial Action
Follow the offer's expected flow and complete the initial qualifying action.
For a game:
Install the game through the offer link.
Use the same device throughout the test.
Launch the game.
Complete the initial action or install-related goal.
Record when the install or initial activity occurs.
Complete the Goal
For game or deal offers, complete the goal you're testing.
Record:
Goal completed
Goal ID, if applicable
Time the goal was completed
Time zone
Allow Time for Tracking to Process
Allow time for the activity to appear. Game installs can take up to 6 hours to appear in My Games for iFrame integrations, and most game progress appears within a few hours, although some activity may take longer.
For API integrations, verify the game's in-progress state in the API experience.
Use the timing stated in the offer and the applicable reporting period to determine whether an event is late.
Do not reinstall the game, reset the advertising ID, clear app or browser data, or create another account to repeat the test. These actions do not establish new-user eligibility and can make the original tracking path harder to investigate.
4. Verify the Results
Once the expected conversion is recorded, verify it using the sources available for your integration.
The conversion is the result you're testing. The Conversions Data API, Conversions report, and postback are different ways to verify that result—they aren't separate tracking checkpoints.
Verify the Conversion
First, confirm the expected conversion occurred. Then use the applicable sources below to verify the result.
Conversions Data API
If you're using the Conversions Data API, confirm that the expected conversion appears in the API response.
Compare the applicable information, including:
User ID
Offer
Goal or conversion
Transaction ID
Reward amount
Conversion status
Conversions Report
In the Besitos Admin Portal, confirm that the conversion appears in the Conversions report.
When checking the report:
Use a date range that covers the test activity and applicable reporting period.
Record the date range and timezone used.
Search for the full user ID.
Match the offer, event, and goal.
Compare the transaction ID, reward, and status with your other records.
An empty report does not automatically mean tracking failed. Timing, filters, activity type, and whether the event produces a reportable conversion can affect what appears.
Postback
If your integration uses postbacks, confirm that your system received the conversion data.
Compare the postback data with the conversion Besitos recorded.
A successful HTTP response from your endpoint only confirms that the request was acknowledged. It does not confirm that your system credited the user correctly.
API Retrieval
If your integration retrieves conversion data through an API rather than receiving postbacks, verify that you can retrieve the expected conversion and that your system processes it correctly.
Reconcile the Results
Where applicable, the same conversion should be identifiable across:
Conversions Data API ↔ Conversions report ↔ Postback or API retrieval ↔ Your system
The exact sources you use depend on your integration and configuration.
For the complete reconciliation process, see Reporting Verification & Reconciliation.
5. Verify the Reward
Confirm that the expected reward appears correctly in your system or the user's experience.
A reward may remain pending during its applicable validation period. A pending reward does not indicate a tracking problem.
If the reward is missing, incorrect, or later reversed, see Troubleshooting Missing, Incorrect, or Reversed Rewards.
Testing Tools vs. Production Testing
Besitos provides tools that can help you test different parts of your integration. They do not all test the same thing.
Test | What it tells you |
iFrame or API Preview | Checks the displayed configuration or sample experience. It does not establish that a real install was attributed. |
Offer Credit Test | Generates a test credit to check credit and postback handling. It does not reproduce advertiser install or gameplay attribution. |
Eligible real install and goal | Tests the actual user path through the offer, installation, progress reporting, conversion, and expected reward state. |
The Offer Credit Test is available to iFrame and API partners, not Wallet partners. Use its dedicated result and receiver evidence when testing credit and postback handling.
A manual credit is not evidence that the original attribution path worked.
If you need to retest after an attribution issue, use another eligible offer rather than reinstalling the same game.
Record Your Results
Keep a record of the test results. This information can help you troubleshoot an issue or provide evidence if you need to escalate it.
Field | Value |
Test date/tester |
|
Partner ID |
|
Partner user ID |
|
Device/OS |
|
Offer name/ID |
|
Goal/conversion tested |
|
Test start time and timezone |
|
Click time and timezone |
|
Install time and timezone |
|
Install visible in My Games (iFrame) or in-progress state in API experience (API) |
|
Goal completed time and timezone |
|
Conversion recorded |
|
Postback received, if applicable |
|
Transaction ID |
|
Reward |
|
Reporting verified |
|
Reward status |
|
Result | Pass / Unresolved |
Notes |
|
Production Test Pass Criteria
Your production tracking test passes when you can confirm that:
The test user and device were eligible.
The offer was started through the expected Besitos flow.
The expected install or initial activity was tracked.
The expected goal or qualifying action was recorded.
Besitos recorded the expected conversion.
You can verify the conversion through the applicable data or reporting source.
Your system received and processed the expected postback or API data, if applicable.
The conversion and reward information are consistent across the applicable sources.
The reward was credited or is correctly shown as pending.
A passing production tracking test confirms that the tested offer activity can be tracked through conversion and that the resulting data can be verified across the applicable systems.
Next, complete Pre-Launch Tracking Certification.
If the Test Doesn't Pass
Don't repeat the entire test immediately. Start by identifying the first checkpoint that didn't occur as expected.
Don't create a new test account to work around an issue. New, unregistered accounts can trigger fraud-prevention checks and make the original test harder to investigate. Instead, use your test log and contact your Account Manager with the test user ID, approximate test time, device details, and any other relevant information.
Issue | Next steps |
Install or progress isn't recorded | Review User & Device Tracking Requirements first, then see Troubleshooting Missing Installs or Game Progress. |
Conversion isn't recorded | See Troubleshooting Missing Installs or Game Progress and verify the applicable reporting period before escalating. |
Conversion is recorded, but no postback arrives | |
Postback arrives, but information is incorrect | Review Postback Data and your postback processing. |
Reporting doesn't match | |
Reward is missing, incorrect, or reversed |
If you still can't determine what went wrong, use your completed test log to help you escalate the issue using How to Escalate a Tracking Issue.
What's Next
Once your production tracking test passes, go to Pre-Launch Tracking Certification.
Certification confirms that you've completed the required tests and that your integration is ready to launch.