Gameball Destination

Gameball is a gamified loyalty platform, offering growth, retention, and referral-management programs; and providing self-serve predictive analytics for growth marketers using machine learning to automate audience insights and recommendations.

This destination is maintained by Gameball. For any issues with the destination, contact Gameball support.

Getting Started

Before you start, make sure Gameball supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.

1. From the Segment app Destinations page click “Gameball”.
2. Search for “Gameball” in the Destinations Catalog and confirm the Source you’d like to connect to.
3. Copy and paste in your “API Key” from your Account Integration page into your Segment Settings UI.

Segment’s track and identify events can only update the following properties in Gameball:

• email
• birthday
• name
• number
• gender

Identify

If you’re not familiar with the Segment Specs, take a look to understand what the identify method does. An example call would look like:

analytics.identify('userId123', {
  email: 'ahaddad@example.com',
  name: 'ahmad'
});

Segment sends identify() calls to Gameball as an identify event.

All events must contain a userID property.

Segment identify events create or update user/player object records in Gameball. If a record with the same userId exists, that record is updated; otherwise, Gameball creates a new customer record with that userId.

Track

If you’re not familiar with the Segment Specs, take a look to understand what the track method does. An example call would look like:

analytics.track('View Product')

Set up your custom track events in Gameball before you send them from Segment to Gameball.

All track events must contain a userID property.

Segment sends track calls to Gameball as a track event.

Personas

You can send computed traits and audiences generated using Segment Personas to this destination as a user property. To learn more about Personas, contact us for 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, Personas 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), Personas sets that value to false.

When you first create an audience, Personas 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.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

API Key

OqXWwPPY7wyNXJtWKgIo4U5LyEufJAkF