|
1 |
| -## Gameball (Actions) Destination |
| 1 | +--- |
| 2 | +title: Gameball (Actions) Destination |
| 3 | +id: 64d3487dcc68fe039fb6237f |
| 4 | +hidden: true |
| 5 | +beta: true |
| 6 | +--- |
2 | 7 |
|
3 | 8 | {% include content/plan-grid.md name="actions" %}
|
4 | 9 |
|
5 |
| -[Gameball](https://www.gameball.co) 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. Through Gameball, you can increase customer lifetime value, and secure unmatched conversion rates - capturing untapped opportunities. |
| 10 | +[Gameball](https://www.gameball.co){:target="_blank”} 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. |
6 | 11 |
|
7 |
| -This destination is maintained by Gameball. For any issues with the destination, [contact their Support team. ](mailto:[email protected]) |
| 12 | +This destination is maintained by Gameball. For any issues with the destination, [contact the Gameball Support team. ](mailto:[email protected]) |
8 | 13 |
|
9 | 14 | ## Benefits of Gameball (Actions) vs Gameball Classic
|
10 | 15 | Gameball (Actions) provides the following benefits over the classic Gameball destination:
|
11 | 16 |
|
12 |
| -**Fewer settings.** Data mapping for actions-based destinations happens in during configuration, which eliminates the need for most settings. |
13 |
| -**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. |
14 |
| -**Support for Gameball V3 API.** Gameball (Actions) is built on the latest version of [Gameball APIs](https://developer.gameball.co/api-reference/api-reference). |
| 17 | +**Fewer settings**: Data mapping for actions-based destinations happens in during configuration, which eliminates the need for most settings. |
| 18 | +**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. |
| 19 | +**Support for Gameball V3 API**: Gameball (Actions) is built on the latest version of [Gameball APIs](https://developer.gameball.co/api-reference/api-reference){:target="_blank”}. |
15 | 20 |
|
16 | 21 | ## Getting started
|
17 |
| -1. Before you start, go to your [Gameball dashboard](https://app.gameball.co/). Click **Settings** in the bottom left, then click on **Account Integration**. Copy the API Key and Secret Key. |
18 |
| -2. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog) search for Gameball. |
19 |
| -3. Select and click Add Destination. |
| 22 | +1. Go to your [Gameball dashboard](https://app.gameball.co/){:target="_blank”}. Click **Settings** in the bottom left, then click on **Account Integration**. Copy the API Key and Secret Key. |
| 23 | +2. From your Segment workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for Gameball. |
| 24 | +3. Select Gameball (Actions) and click **Add Destination**. |
20 | 25 | 4. Select an existing Source to connect to Gameball (Actions).
|
21 | 26 | 5. Enter the API Key and Secret key in the destination settings in Segment.
|
22 | 27 |
|
23 | 28 | {% include components/actions-fields.html %}
|
24 |
| -[comment]: <> Please add auto-generated content for "Identify Player", "Track Event" & "Track Order" mapping |
25 | 29 |
|
26 | 30 | ## Migration from the classic Gameball destination
|
27 |
| -Keep in mind if you plan to move to Gameball from a classic Gameball destination you will need to map your events to Gameball and please note that Gameball (Actions) uses Gameball's HTTP API v3. |
| 31 | +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. |
0 commit comments