Request Workflow Overview

This article overviews a request workflow in the Gamoshi platform up to it being sent to an advertiser.

After setting up Inventories and Advertisers in your account, incoming requests will start incoming from your publishers and will be sent to the relevant advertisers. The RTB auction will run and bids will be made on the traffic, the winning bids will be sent back to the publishers. Along the way, there are a lot of processes and filters that will come into work on the incoming inventory requests up to them being sent to the relevant advertisers. These processes will be reviewed here in this article in general lines.

1. Step 1 - Requests incoming into your account from your inventory partners.

2. Step 2 - Validation processes - checking the incoming requests by the RTB protocols guidelines.

3. Step 3 - Inventory filters and capping processes - implementing capping and filters defined on inventories.

4. Step 4 - SCHAIN and PCHAIN system automatic processes. If the original request contained SCHAIN then we are adding a node if not we are creating a new SCHAIN object with one node taking the values from the Business partner sellers info if exists and from the inventory sellers info if it does not exist on the business partner.

5. Step 5 - Processing Inventory allow lists and block lists.

6. Step 6 - Processing Inventory mapping rules which are defined as an allow list.

7. Step 7 - Processing inventory mapping rules, first rules defined for all Inevntories and then specific inventory rules.

8. Step 8 - Checking which are the valid campaigns for the request.

9. Step 9 - For all valid campaigns and advertisers processing filters, allow lists, mapping rules allow lists and block lists.

10 Step 10 - For all advertisers which stayed relevant after lists and filtering, we will process mapping rules that are defined for all advertisers and then specific advertisers mapping rules.

11. Step 11 - The request is sent after all processing to the advertiser.