Integration Smoke Test

The Integration Smoke Test is the first test to run after you complete your basic integration and tracking setup. It verifies that your platform can connect to Besitos, identify users, display or retrieve offers, and complete the applicable credit or postback test.

The smoke test does not require you to complete a real offer. It uses the Offer Credit Test to verify credit and postback handling.

A passing smoke test does not confirm that a real offer will track successfully. You'll verify the complete tracking journey in the Production Tracking Test.

Make sure you've:

If you haven't completed your basic implementation, start with the Implementation Checklist.

Open your Besitos experience using your test user.

Depending on your integration:

Expected result: Your Besitos experience loads or your API returns the expected data without an integration error.

If the experience doesn't load or your API doesn't return the expected data, review the applicable iFrame Integration Guide or API Integration Guide.

Confirm that the expected user ID is being passed to Besitos.

The user ID should:

Expected result: Besitos receives the user ID associated with your test user.

Confirm that an offer is available for your test user.

Expected result: At least one offer is available to the test user.

If no offers appear, verify your test user's eligibility, offer availability, and integration configuration before continuing.

Select an offer and confirm that the click takes the user through the expected offer flow.

Expected result: The offer opens or redirects successfully to the intended destination without errors.

You don't need to complete the offer for this step. You're confirming that the offer interaction and redirect work as expected.

Do not search for the offer separately or start it from another source. Start a production tracking test through the expected Besitos offer flow.

Use the Offer Credit Test to verify your credit and postback handling. It lets you generate a test credit from the Besitos Admin Portal without completing a real offer.

This step applies to iFrame and API integrations. Wallet integrations that don't use postbacks don't use the Offer Credit Test and should skip this step.

Follow the Offer Credit Test article for the complete procedure.

Expected result: The test credit is generated successfully and, if applicable, your configured postback endpoint receives the test credit.

The Offer Credit Test does not reproduce advertiser install or gameplay attribution. A successful credit test does not confirm that a real offer will track successfully.

If your integration uses postbacks, check your system to confirm that the test postback was received and processed successfully.

Verify the applicable information, such as:

See Postback Data for details about the information included in the postback.

Expected result: Your system receives and successfully processes the test postback.

If the test credit succeeds but your system doesn't receive the postback, see Troubleshooting Postback Delivery Failures.

For integrations that retrieve conversion data through an API instead of receiving postbacks, verify the applicable API behavior according to your integration setup.

Your Integration Smoke Test passes when you can confirm that:

A passing smoke test confirms that your core integration and applicable credit or postback handling are working. It does not confirm that a real offer will track successfully.

Don't move on to production testing until the smoke test passes. Start by identifying the first step that didn't work as expected.

If you can't resolve the issue, contact your Besitos Account Manager or Implementation Team.

Once your smoke test passes, move on to the Production Tracking Test.

The production test uses a real offer, eligible user, and eligible physical device to verify the complete tracking journey from offer activity through conversion.