The Events API allows you to pass revenue data allowing you to track your Return on Ad Spend directly through the Gamesight dashboard. There are two different types of revenue that can be attached to events.

Currency conversion is handled as described in our Currency Handling documentation.

Once Per User Revenue

The once_per_user revenue type is to be used when you are tracking revenue in situations where you intend to send the event more than once but only want to count the revenue once. This should be used in situations such as:

• Attaching revenue to game launch events for premium games
• Attaching revenue to DLC/expansion ownership events that fire every game launch

Here is an example request

curl https://api.ingest.marketing.gamesight.io/events \
    -X POST \
    -H 'Authorization: SOMEAPIKEYHERE' \
    -H 'X-Api-Version: 1.1.0' \
    -H 'Content-Type: application/json' \
    -d "$(cat <<-EOF
  {
    "user_id": "b91f8k5r",
    "type": "game_launch",
    "revenue_currency": "usd",
    "revenue_amount": 10.00,
    "revenue_type": "once_per_user",
    "identifiers": {...}
  }
EOF
)"

Cumulative Revenue

The cumulative revenue type is to be used when you are tracking revenue in situations where you want revenue to be incremented every time the event is seen. This should be used in situations such as:

• Attaching revenue to an in-game purchase upon completion of the transaction

curl https://api.ingest.marketing.gamesight.io/events \
    -X POST \
    -H 'Authorization: SOMEAPIKEYHERE' \
    -H 'X-Api-Version: 1.1.0' \
    -H 'Content-Type: application/json' \
    -d "$(cat <<-EOF
  {
    "user_id": "b91f8k5r",
    "type": "skin_purchase",
    "revenue_currency": "usd",
    "revenue_amount": 5.00,
    "revenue_type": "cumulative",
    "identifiers": {...}
  }
EOF)"