Gameball (Actions) Destination
Gameball is an all-in-one customer loyalty marketing platform that empowers brands to create personalized retention campaigns, helping them grow and monetize their customer base using cutting-edge gamification strategies. Using Gameball, you can increase customer lifetime value and secure unmatched conversion rates - capturing untapped opportunities.
This destination is maintained by Gameball. For any issues with the destination, contact the Gameball Support team..
Gameball (Actions) provides the following benefits over the classic Gameball destination:
Fewer settings: Data mapping for actions-based destinations happens in during configuration, which eliminates the need for most settings. Clearer mapping of data: Actions-based destinations enable you to define the mapping between the data Segment receives from your source, and the data Segment sends to the destination. Support for Gameball V3 API: Gameball (Actions) is built on the latest version of Gameball APIs.
- Go to your Gameball dashboard. Click Settings in the bottom left, then click on Account Integration. Copy the API Key and Secret Key.
- From your Segment workspace's Destination catalog page search for Gameball.
- Select Gameball (Actions) and click Add Destination.
- Select an existing Source to connect to Gameball (Actions).
- Enter the API Key and Secret key in the destination settings in Segment.
Go to help center to learn how to find your API Key.
Gameball (Actions) has the following presets
| Preset Name | Trigger | Default Action |
|---|---|---|
| Track Orders | Event type = "track" and event = "Order Completed" | Track Order |
| Create Or Update Players | Event type = "identify" | Identify Player |
| Track Events | Event type = "track" and event != "Order Completed" | Track Event |
Build your own Mappings. Combine supported triggers with the following Gameball-supported actions:
Mapping limits per destination
This Action used to create or update a player in Gameball with the provided attributes.
Identify Player is a Cloud action. The default Trigger is type = "identify"
Unique identifier for the player in your database.
Optional
Player's unique mobile number.
Optional
Player's unique email.
Optional
Player's display name
Optional
Player's first name
Optional
Player's last name
Optional
Player's gender.
Optional
Player's date of birth
Optional
Player's join date at your system.
Optional
Player's country.
Optional
Player's city
Optional
Player's zip code
Optional
Player's preferred language
Optional
A boolean value indicating if the customer who placed this order is a guest. The default is false.
Optional
Player's utms
Optional
Player's used devices
Optional
Player's total spent amount
Optional
Player's last order date
Optional
Player's total orders
Optional
Player's average order amount
Optional
Comma separated string of tags to be attached to the player.
Optional
Key value pairs of any extra player attributes.
Optional
Referring player’s referral code. This is used in case of referral, where the player to be created is referred by the player having this code.
Optional
The level order to place the player in. IMPORTANT: manual player leveling is available under special circumstances and is not available by default. Contact us for more info.
Optional
The FCM token (Firebase Cloud Messaging) needed for sending mobile push notifications. (Used only in case of mobile app)
This action allows you to track and send your players' events to Gameball.
Track Event is a Cloud action. The default Trigger is type = "track"
The name of the event
Optional
The event metadata to send to Gameball
Unique identifier for the player in your database.
Optional
Player's unique mobile number.
Optional
Player's unique email.
This action used to track orders. They are designed specifically for E-Commerce Solutions.
Track Order is a Cloud action. The default Trigger is event = "Order Completed"
Unique identifier for the player in your database.
Optional
Player's unique mobile number.
Optional
Player's unique email.
Unique order ID which identifies the underlying order in your system, e.g. order number, invoice number. It will be used for reversing any reward or redemption transaction on Gameball.
The date this order was placed, as an ISO8601 timestamp. Defaults to now if not provided.
The sum of all order items' prices, including discounts, shipping, taxes, and tips. (Note: totalPaid is part of the totalPrice). Must be positive.
The actual paid amount to the store. (Based on this amount, the player will be rewarded. Also, According to the Cashback Configuration). Must be positive.
Optional
The total shipping price of the order. Must be positive.
Optional
The sum of all the taxes applied to the order in the shop currency. Must be positive.
Optional
Total discount applied on this order. Must be positive.
Optional
A list of line items, each containing information about an item in the order.
Optional
An array of discount codes.
Optional
Monetary value of the redeemed points to be used by that player while placing his order. Note: If this field is set, then the holdReference value should be null. Also, both fields could be null.
Optional
Hold reference ID received after calling Hold Points API. This is used in case you want to use already held points. Note: If this field is set, then the redeemedAmount value should be null. Also, both fields could be null.
Optional
A boolean value indicating if the customer who placed this order is a guest. The default is false.
Optional
Key value pair(s) of any extra information about the order. The key values must be of type string or number
Optional
Merchant unique id or code
Optional
Merchant name
Optional
Branch unique id or code
Optional
Branch name
Keep in mind if you plan to move to Gameball (Actions) from a classic Gameball destination that Gameball (Actions) uses Gameball's HTTP API v3.
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.
When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Real-time to batch destination sync frequency
Real-time audience syncs to Gameball (Actions) may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Segment lets you change these destination settings from the Segment app without having to touch any code.
Go to help center to learn how to find your API Key.