> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gameball.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Track Events

> Track customer events and actions at your POS

Event tracking captures customer actions beyond purchases, letting Gameball trigger campaigns, rewards, and personalized experiences based on behavior. Order tracking already captures purchase events automatically, so events are an optional layer for non-purchase activity such as store visits, category preferences, or promotion interactions.

<Note>
  For most POS integrations, [order tracking](/installation-guides/v3/pos/track-orders) is enough. Reach for event tracking only for advanced use cases or specific campaign requirements.
</Note>

## Send an Event

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST 'https://api.gameball.co/api/v4.0/integrations/events' \
    -H 'Content-Type: application/json' \
    -H 'APIKey: YOUR_API_KEY' \
    -H 'SecretKey: YOUR_SECRET_KEY' \
    -d '{
      "customerId": "mobile_966500001234",
      "eventName": "store_visit",
      "metadata": {
        "store_location": "Mall Branch A",
        "visit_date": "2025-09-29T15:00:00Z"
      }
    }'
  ```
</RequestExample>

<ResponseExample>
  ```json Success theme={null}
  {
    "success": true,
    "message": "Event tracked successfully"
  }
  ```
</ResponseExample>

## Tips & Gotchas

* Events can trigger automated campaigns configured in your Gameball dashboard.
* Use descriptive event names that align with your business logic.
* Include relevant metadata to enable advanced targeting and segmentation.
* Events are processed asynchronously and may not reflect immediately in customer profiles.