Android SDK Integration
Follow the steps below to integrate the ByteBrew SDK:
Import ByteBrew Android Library to your project
To import the aar file go to File -> New -> New Module and click import .jar/.aar package.
Make sure to add the package as a dependency to your project and implement the imported package.
Add these required dependencies to support ByteBrew:
implementation 'com.google.android.gms:play-services-ads-identifier:17.0.0'
implementation 'com.google.firebase:firebase-messaging:23.0.0'
implementation 'com.android.installreferrer:installreferrer:2.2'
Go to your ByteBrew Dashboard
Go to your Game Settings page on the ByteBrew dashboard and locate your app keys listed on the dashboard. After finding your app keys, copy them.
Initialize ByteBrew with your Game ID and Game Key
Initialize ByteBrew using the code below at the first activity of your game or app to start capturing sessions and events.
Input the corresponding Game ID and Game Key from the ByteBrew dashboard into their parameter fields.
// Initialize ByteBrew
ByteBrew.InitializeByteBrew("GAME_ID", "GAME_KEY", "ENGINE/PLATFORM (ex. Android Native)", this);
Custom Events Tracking
Custom Events in ByteBrew enable you to deep dive across all of our extensive analytics dashboards. Continue below to learn how to integrate custom events.
Custom Events on ByteBrew allow for an unlimited number of key_name=value; sub-parameters under the custom event. For example, you can have a custom event called “level” that has a subparameter under the event named “levelnumber” and the values of that Level Number subparameter could be “1, 2, 3, 4, 5, etc.”. Additionally you could add in other subparameters for attributes inside the levels of your game, such as "powerups", to show the different equipment used in levels with parameter values "fireball, revive, doublepoints, etc.". The world is your oyster with custom events, so build as complex of an event system as you need for your game. To illustrate our custom event structure visually, see the following diagram:
Custom Events
See samples below to see how to code Custom Events:
Basic Custom Event:
//Basic Custom Event without any sub-parameters
ByteBrew.NewCustomEvent("eventName");
//Basic Custom Event with a sub-parameter
ByteBrew.NewCustomEvent("CustomEventName", "key_name=value;");
//Examples
ByteBrew.NewCustomEvent("GamePurchaseVC", "currency=GOLD;amount=500;character=viking;");
ByteBrew.NewCustomEvent("LevelCompleted", "level=25;character=viking;");
Dictionary Custom Event Tracking Method:
To easily add additional custom sub-parameters to an event with a dictionary method using string "key_name=value;" pairs shown below:
//Key Value format "key_name=value;"
//Custom Events can take multiple pairs, "key_name1=value1;key_name2=value2;key_name3=value3;"
ByteBrew.NewCustomEvent("level_started", "weapon=megablaster;powerup=extralife;");
Remote Configs & A/B Tests
Remote Configs allow you to make updates to your app remotely without having to update your game's app store. Adding remote configs to your games are a fantastic way to be agile and send updates or patches to players instantly. Remote Configs are also utilized for creating A/B Tests on the platform.
When planning to integrate Remote Configs, We recommend implementing remote configs throughout all parts of your game to allow you to tweak and tune as you analyze your game performance data. See how to implement remote configs in your game by following the steps below:
Loading the Remote Configs
To use Remote Configs, you must first call for the config to get updated. You can call the below code whenever you want to update the configs:
//Call the handler
ByteBrew.LoadRemoteConfigs(new RemoteConfigListener() {
@Override
public void RetrievedConfigs(boolean b) {
//Do Whatever you want here once the config is updated
}
});
//Check if the remote configs are ready and set
ByteBrew.HasRemoteConfigsBeenSet();
Retrieve the Configs
Once the handler has finished, you can call the remote config method below:
//Call to get the key specific value and if the key doesn't exist it will return the default variable specified, like if the AB test user is in the control group
String value = ByteBrew.RetrieveRemoteConfigValue("dailyWeapon", "goldRevolver");
Push Notifications
Using ByteBrew you can send cross-platform push notifications to your players around the globe. To get started with push notifications follow the steps below.
Integrate Push Notifications
Integrating Push Notifications with ByteBrew is super simple and only requires one line of code after initializing the ByteBrew SDK. See the Push Notification integration code line below:
ByteBrew.StartPushNotifications(this);
Create Push Notification App on the ByteBrew Dashboard
Go to the Push Notification dashboard on ByteBrew and create a new Push Notification App. See our Push Notification Dashboard documentation for step by step walkthroughs about this.
Push Notification Extra Settings (Optional Android Only)
Add a Custom Small Icon and Large Icon for push notifications.
Push Notification Android Manifest (Required Android Only)
<uses-permission android:name="android.permission.POST_NOTIFICATIONS"/>
Track Purchases
In ByteBrew SDK you can track all your game or apps in-app purchases to analyze your monetization performance on the dashboard. There are two ways to track purchases on ByteBrew. The first way is to use basic in-app purchase events. The second way is to use our real-time server-side purchase validation to validate real purchases vs. fraudulent transactions. See below to learn how to implement either method.
Track Basic In-App Purchases
To track in-app purchases in your game, use the below method:
ByteBrew.TrackInAppPurchaseEvent("Google Play Store", "USD", 5.99, "currencyPack01", "Currencies");
Track Validated Purchases
On ByteBrew, we offer a real-time server-side purchase validation to stop purchase fraud from client-side purchase receipt tampering that takes place in mobile games and apps. To utilize this validation you have two options: (1) a method with a callback to retrieve if a purchase was valid and (2) a method just to validate purchases without a callback. Follow below sections for code snippets for each function:
Purchase Validation with Callback
To track validated in-app purchases utilize the platform specific method. Using this method will create a purchase callback that will return a payload with the purchases details and verification status. See below for the Return Results and message definitions:
//Retrieve the Android receipt and Signature from the purchase event that occurs. We will validate it server side so you can view valid purchases in you dashboard.
String googleReciept = "...";
String googleSignature = "...";
ByteBrew.ValidateGoogleInAppPurchaseEvent("Google Play Store", "USD", 5.99, "currencyPack01", "Currencies", googleReciept, googleSignature, new PurchaseResponseListener() {
@Override
public void purchaseValidated(ByteBrewPurchaseResult byteBrewPurchaseResult) {
Log.d("Purchase Processed: ", String.valueOf(byteBrewPurchaseResult.isPurchaseProcessed())); //Boolean telling if the purchase even went to the server to get checked
Log.d("Purchase itemID: ", byteBrewPurchaseResult.getItemID()); //Product/Item ID of the purchase processed
Log.d("Purchase is Real: ", String.valueOf(byteBrewPurchaseResult.isPurchaseValid())); //Boolean signaling if the purchase is real or fake
Log.d("Process Message: ", String.valueOf(byteBrewPurchaseResult.getMessage())); //Message from the server telling the explaination behind the decision
}
});
Returned Results:
The following table are the possible returning results:
Returned Results Message:
In addition to the Return Result you will also recieve a message. See below for possible output messages and their definition:
"Validation Successful, real purchase.": This means that the message as a real purchase.
"Validation Failed, fake purchase.": This means that the purchase is fake or fraudulent.
"Error validating receipt, check game configs.": This message means that there might be an issue with the implementation. Check to make sure that the purchaseProcessed boolean is True and go to your game settings on the ByteBrew dashboard to update your Apple App Shared Secret and Google Play License Key.
Purchase Validation without Callback
To track in-app purchases using our validation system without looking for the purchase callback, utilize the platform specific method code snippets below:
//Retrieve the Android receipt and Signature from the purchase event that occurs. We will validate it server side so you can view valid purchases in you dashboard.
String googleReciept = "...";
String googleSignature = "...";
ByteBrew.TrackGoogleInAppPurchaseEvent("Google Play Store", "USD", 5.99, "currencyPack01", "Currencies", googleReciept, googleSignature);
Ad Tracking Event
Using ByteBrew you can track your game's or app's ad events. Tracking Ad Events will enable you to see breakdowns of your ads in the monetization dashboard. See the code snippets below to learn how to track ad events:
// Record the Placement Type, Location of the placement, ad unit ID, and Network
ByteBrew.TrackAdEvent("Interstitial", "EndOfLevel", "3253k3302-3r3j4i343-3nij343-405403", "AdMob");
//Some ad event paramters can be ommited like so
ByteBrew.TrackAdEvent("Interstitial", "EndOfLevel");
ByteBrew.TrackAdEvent("Interstitial", "EndOfLevel", "3253k3302-3r3j4i343-3nij343-405403");
Custom User Data Attributes
Data attributes are tags in the SDK that you can give a user to define them more specifically on the dashboard when filtering. For example, you can use data attributes to tag to users to build player segments to send targeted push notifications. If you are looking to update values on users at certain locations of your game, then use Custom Events with subparamters to track that type of update. See the following code snippets for examples on how to use Custom User Data Attributes:
ByteBrew.SetCustomData("dundees", 3);
ByteBrew.SetCustomData("loves_the_office", true);
Progression Event Tracking
Progression events are a great way to track linear event stages in your game to measure how players are transitioning through levels or worlds. See below for the list of progression event parameters and code snippets for progression events.
ProgressionType
The type of progression event. Must be one the following options:
Environment
Area or World in the game the event is located such as: Tutorial, Arena, or Level. You can choose how to define the environments in your game or app.
Stage
The stage of the environment that the event takes place in such as: king_arena, jungleLevel, or level_02. You can define how to define the stages in your game or app.
Value
The value of the event. This can be a string or float value attached to the event.
//Example Progression event where the user started a tutorial in arena 0 or first arena
ByteBrew.NewProgressionEvent(ByteBrewProgressionType.Started, "Tutorial", "arena0");
//Example progression event where the user has completed the kings arena and could be rewarded with 3 crowns
ByteBrew.NewProgressionEvent(ByteBrewProgressionType.Completed, "Arena", "kings_arena", 3);
Get User ID
GetUserID method in the SDK enables you to grab the current User ID of the user in your game. This is a handy method for finding the ID for a user you want to send a specific push notification to.
// Get the string userID
ByteBrew.GetUserID();
Stop Tracking Current User
In the ByteBrew SDK, you have the option to stop tracking any user in your game by calling the ByteBrew StopTracking method. This will immediately stop and disable any tracking for a user. As another alternative method to disabling tracking, you can build your own consent pop-up prompt screen in your game or app and delay the initialization of ByteBrew SDK until your user has consented/agreed to your prompt.
ByteBrew.StopTracking();
SDK FAQs
ByteBrew supports Android 5.1 and above.
No, you can only use one push notification service or provider to send notifications at one time. However, if you are only using ByteBrew for our other services, then you can use another platform's push notifications SDK while still using ByteBrew SDK without any issues.
No, Push Notifications has it's own internal callback, so no other callback is necessary.
API Level 22 (Android 5.1)
A/B Tests deliver configs using your Remote Configs integration. Remote Configs delivered in milliseconds to your players after the ByteBrew SDK is initialized.
Need some help?
Join the ByteBrew Discord community to chat with our team and other developers on the platform.