---
name: kixo-sdk-integration
description: Integrate or audit the Kixo SDK in a customer web, iOS, or Android app.
---

# Kixo SDK Integration

Use this skill when asked to integrate, audit, or fix Kixo SDK usage.

## Workflow

1. Inspect the app stack and choose exactly one SDK.
2. Configure Kixo once at app startup.
3. Add only product-specific custom events.
4. Add identity only after a stable product user ID exists.
5. Call reset on logout.
6. Verify one auto event and one custom event.

## SDKs

- Web: `https://cdn.kixo.io/kixo.min.js` (script embed; npm `@kixo.io/web`)
- iOS: Swift Package `https://github.com/kixoio/kixo-ios-sdk`, `import Kixo`
- Android: Maven repo `https://raw.githubusercontent.com/kixoio/kixo-android-sdk/main/repo`, dependency `io.kixo:kixo-android-sdk:0.1.17`, `import io.kixo.sdk.Kixo`

## Rules

- Kixo is B2B. Customer team members use Kixo; end users do not log in to Kixo.
- Use placeholders unless the user provides Project ID and SDK API key values.
- Do not commit real keys.
- Never use dashboard/admin tokens in client apps.
- Do not duplicate auto-tracked events.
- Use snake_case, object_verb, past-tense event names.
- Put context in properties.
- Include stable entity IDs.
- Prefer standard events: `signup`, `activation`, `purchase`, `subscribe_start`, `subscribe_renewed`, `trial_start`, `cancel`, `upgrade`, `downgrade`, `share`, `invite`.
- Do not expose internal Kixo dev-routing flags.