At a glance: This article will guide you through the process of setting up the B2Tech integration in the Affnook panel.
B2Tech integration in Affnook is used to connect the B2Tech gaming platform (operator side) with the Affnook affiliate tracking system so that player activity and revenue data can be tracked automatically for affiliate campaigns.
What is B2Tech Integration?
It is a server-to-server integration between B2Tech and Affnook that allows data such as:
Player registrations
Deposits (FTD/STD)
Bets or gaming activity
Revenue or commissions
to be sent directly from B2Tech to Affnook in real time.
Why is it Used? (Purpose)
The main purpose is to ensure accurate affiliate attribution and reporting without manual uploads. It helps operators track which affiliate brought which player and how much revenue that player generated.
Steps to Configure B2Tech Integration in Affnook
Step 1: Navigate to Integration Settings
From your dashboard, go to the Automation section. Then select the Integration tab, where you will find the B2Tech Configuration option. Click on the Config button to proceed with the setup.
Step 2: Add Credentials from B2Tech
In this step, you need to enter the Secret Key and Brand ID obtained from your B2Tech panel for the specific brand you want to integrate. These credentials are required to establish a secure connection between the two platforms.
Step 3: Map Brand IDs
Next, you can map the Brand ID from the B2Tech panel to the corresponding Brand ID in the Affnook panel. This mapping ensures that activities received from B2Tech are correctly attributed to the appropriate brand within Affnook.
Step 4: Map Product IDs (Optional)
Additionally, if required, you may map the Product ID from the B2Tech panel to the respective Product ID in Affnook. This step is optional but recommended for more accurate product-level tracking and reporting.
Note
When an activity is received with a Brand ID that is not mapped in the B2Tech integration configuration, the system is unable to pass that Brand ID to the Affnook API, so it is sent as empty. In such scenarios, if the account type is an operator account, the API automatically applies a fallback logic where the activity gets mapped to the brand associated with the campaign instead. This prevents activity loss and ensures the conversion is still attributed within the system.
For example, if an activity is received for Player ID 123456 (Transaction ID 78901234) with Brand ID 999, and Brand ID 999 is not configured in the integration, the Brand ID will be sent as empty. The system will then map the activity to the campaign brand linked with Campaign ID 55 (Example Campaign), which may have Brand ID 10 (Example Brand). As a result, the activity will appear under Brand ID 10, even though Brand ID 999 itself was not mapped.
We are delighted to have assembled a world-class team of experienced professionals who are ready to take care of your queries and answer any questions you may have. Feel free to reach out to us at anytime by emailing us at [email protected] or by using the in-platform chat feature. We'd love to hear from you!
