1. Features
  2. Stats: dashboard to monitor your connections

Discrepancy in data between TGX Stats and your own System Stats

We often receive inquiries from our Partners asking us why the data they see on our App Stats don't match with what their own system tells them, for example, they report seeing more or/and less requests per method.  As you know, on TGX we have the following methods in our Booking Flow:

Avail -> Quote-> Reservation

However sometimes, we have to perform more than one method directly to the Seller's system to adapt to the Seller's own API workflow. That means that our data will reflect those extra requests for every RQ from the Buyer, perhaps there’s 2-3 different queries performed to the Seller

For example, there are some integrations developed at TGX (NOT all of them), in which our Valuation/Quote Request, for the Buyer/TGX is just 1 Request, but inside this single Valuation Request to TGX, we send the Seller 1 Avail RQ to ensure that there’s still Availability and ensure that the Rate the Buyer wants is still being returned, and then, we proceed to perform the respective Valuation Request to the Seller.

In case you are not sure about the workflow that it’s done with your integration as a Seller, please contact our CC Team.