After your Integration Smoke Test passes, use this quick start to run a production tracking test with a real offer, an eligible test user, and a physical device.
For detailed testing, verification, and troubleshooting guidance, see Production Tracking Test.
Before You Test
1. Register Your Test Account
Contact your Besitos Account Manager before testing, and share:
Testing dates
Number of testers
Devices you'll use
Tester countries
Test user IDs
Use one test user ID per tester and one test account per device.
To register your test accounts:
Open the offerwall, or your app where offers are hosted, with each test user ID.
Send the test user IDs to your Account Manager.
Wait for confirmation before starting your test offers.
Keep the same user ID throughout testing. Creating a new user ID for each click or session can affect reward tracking and how your test account is recognized.
2. Check Your Test User & Device
Before you start, confirm that:
The test user is eligible. Only new users are accepted.
The game is new to the device. The game must never have been previously downloaded or installed on the test device. If it has, use a different eligible device.
You're using a real device. Use a standard browser or your production app. Don't use emulators, simulators, headless browsers, or automated scripts unless testing has been arranged in advance.
Your tracking settings are ready. Complete the applicable tracking requirements. On iPhone, turn off iCloud Private Relay before testing.
Your network is ready. Avoid VPNs and proxies when possible. If a tester is outside the US or another supported country, contact your Account Manager before testing. A VPN won't change the country we detect and can trigger fraud-prevention checks.
You stay on one network. Avoid switching between Wi-Fi, mobile data, or VPN locations during the test.
Your integration passes device advertising IDs when available. Pass IDFA on iOS with user consent and GAID on Android.
If Besitos has provided a test environment or test partner setup, use it so test activity stays separate from live traffic.
Keep a simple test log with the test user ID, device, offer, date and time (including timezone), and network. This information can help your Account Manager investigate an issue.
See User & Device Tracking Requirements for more details.
Run the Test
3. Start the Offer
Open the Besitos experience as your test user and find the offer you're testing.
For API integrations, retrieve the offer through your API.
Start the offer from the Besitos experience. Don't search for the offer separately or start it from another source.
Record the time you started the offer and the timezone.
4. Complete the First Goal
Follow the offer's normal user journey:
Install the game through the offer link.
Launch the game on the same device.
Complete the first goal or qualifying action.
Record when the install and goal occur.
5. Wait for Tracking
Most installs are credited within minutes. If the install or activity doesn't appear after an hour, contact your Account Manager rather than retrying the test.
For iFrame integrations, some game installs can take up to 6 hours to appear in My Games. For API integrations, check the game's in-progress state in the API experience.
Don't reinstall the game, reset the advertising ID, create another account, or repeat the test on the same device.
Verify the Test
6. Confirm the Conversion
Once the expected conversion is recorded, verify it using the sources available for your integration.
Check the applicable:
Conversions report in the Besitos Admin Portal
API retrieval
Confirm that the user, offer, goal or conversion, transaction ID, reward, and status match where applicable.
7. 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.
Your Test Passes When
You can confirm that:
The test user and device were eligible.
The offer was started through the Besitos experience.
The expected install or initial activity was tracked.
The expected goal 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 reward was credited or correctly shown as pending.
If Something Doesn't Work
Don't create a new test account or repeat the install. Start by identifying the first step that didn't occur as expected.
If your test account is blocked, send your Account Manager the test user ID, approximate test time, and device details. If the account is restored, continue testing with the restored account rather than replacing it.
For detailed troubleshooting steps, see Production Tracking Test.