After completing a production tracking test, verify that the resulting conversion appears correctly in the data and reporting sources available for your integration.
This process helps you confirm that:
Besitos recorded the expected conversion
Your system received the expected data.
Conversion and reward information is consistent across sources.
You can identify and investigate discrepancies before launch.
Depending on your integration, you may verify conversion data using the Conversions Data API, Conversions report in the Besitos Admin Portal, and postbacks.
For a high-level overview of how this fits into the tracking journey, see How Tracking Works.
Before you start
Make sure you have:
Completed a production tracking test.
The test user's user ID.
The offer name and ID.
The goal or conversion you tested, if applicable.
The approximate time of the conversion.
The transaction ID, if available.
Access to the Besitos Admin Portal.
Access to the Conversions Data API, if applicable.
Access to your systems' postback and reward records.
1. Confirm the conversion in Besitos
Start by confirming that Besitos recorded the conversion.
Use the Conversions report in the Besitos Admin Portal and, if applicable, the Conversion Data API. You can also look at postback data to confirm conversions.
Look for the conversion using information from your test, such as:
User ID
Offer
Goal or conversion
Transaction ID
Conversion time
Reward amount
If the conversion isn't recorded
The issue may have occurred earlier in the tracking process.
See Troubleshooting Missing Installs or Game Progress and How Tracking Works to understand the tracking process and identify what to investigate.
2. Verify the conversion data
Compare the conversion information in Besitos with what you expected from your production test.
Check that the applicable information is correct, including:
User
Offer
Goal or conversion
Transaction
Reward
Status
Timestamp
The exact fields available depend on the source and your integration. See Conversion Data API or Postback Data for more details.
3. Verify your postback data
If your integration uses postbacks, compare the postback your system received with the conversion recorded in Besitos.
At minimum, confirm that you can match the postback to the Besitos conversion using identifiers such as the transaction ID and user ID.
If the conversion is in Besitos, but you didn't receive a postback
This is a postback delivery issue. See Troubleshooting Postback Delivery Failures.
4. Verify your system
Confirm that your system processed the conversion data as expected.
Check your own records for:
The expected user.
The expected offer or goal.
The expected conversion.
The expected reward.
The expected transaction.
The correct conversion status.
If your system received the postback, but the data is incorrect
Review your postback processing and postback data.
5. Reconcile the results
Compare the conversion across the applicable sources:
Besitos → Postback → Your system
For API partners, this may also include: Conversions Data API → Your system
The Conversions Data API, Conversions report, and postback can all provide conversion information. Use the sources available to your integration to confirm that the same conversion is represented consistently.
What to compare
Information | What to confirm |
user | The conversion belongs to the expected user. |
offer | The conversion belongs to the offer you tested. |
goal | The expected goal or qualifying action is recorded. |
transaction | The conversion can be matched using its transaction ID, when available. |
reward | The reward amount and status are consistent. |
time | The conversion occurred within the expected timeframe. |
status | The conversion has the expected status. |
Not every source will contain every field. Compare the available and applicable information for your integration.
6. Investigate discrepancies
If information doesn't match, first determine which source differs from the others.
Issue | Next step |
Conversion is missing from Besitos | The issue may have occurred before the conversion was recorded. |
Conversion appears in Besitos, but not in your system | Check whether your system received the conversion data through your postback and processed it. |
Postback was received, but your records don't match | Review how your system processes postback data and compare the received values with the conversion recorded by Besitos. See Postback Data. |
Reward information doesn't match | Confirm the reward amount and status in Besitos and your system. If the conversion is pending or has been reversed, allow for the applicable reward status and validation process. |
Understanding timing differences
The same conversion may not appear in every source at exactly the same time.
Allow for expected processing and reporting delays before determining that a discrepancy exists.
When comparing timestamps, make sure you're using the same timezone. Besitos timestamps are provided in Eastern Time (America/New York).
Record the time of the original user activity as well as the time the conversion appeared in each system. This can help distinguish a normal reporting delay from an actual data discrepancy.
Reconciliation pass criteria
Your verification is complete when you can confirm that:
Besitos recorded the expected conversion.
The conversion information matches the production test.
Conversion data appears in the applicable reporting and data sources.
Your system received and processed the expected postback, if applicable.
Reward information is consistent across the applicable sources.
Any timing or status differences are understood and expected.
A successful reconciliation means you can trace and match the expected conversion across your system and the applicable Besitos systems.
If you can't reconcile the data
Document the discrepancy before escalating.
Include:
Partner ID
User ID
Offer name and ID
Goal or conversion
Transaction ID
Conversion time
Relevant API response
Relevant report information
Postback payload, if applicable
Your system's corresponding record
The specific fields or values that don't match
Any timing differences
What you've already checked
See How to Escalate a Tracking Issue for next steps.