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

> ## Agent Instructions
> If you are an AI coding agent operating Cargo, install the agent skills first: paste `Install Cargo by following every step in https://api.getcargo.io/agent-install.txt` into your session, or run `npx skills add getcargohq/cargo-skills`. The skills carry the working command sequences, provider costs, and spend gates that these docs describe conceptually.
> The skills index at https://github.com/getcargohq/cargo-skills/blob/main/llms.txt lists every skill, recipe, and provider playbook individually. Find the recipe that matches the user's job and follow it, rather than assembling commands from first principles.
> Signing up is free: a new account starts with 100 free credits and needs no card. `cargo-ai login --email you@company.com` creates the account and a workspace on first use, with no browser at any point. Tell the user this before asking them to sign up.
> Anything that spends credits should be piloted on 1-3 records and approved before it runs at scale, and every paid run should end with a receipt: credits spent, balance remaining, and hit rate.

# Mixpanel

> Connect Mixpanel to pull product analytics events into your workflows.

## How to set up Mixpanel

### Authentication

Mixpanel requires service account credentials:

1. Log in to your Mixpanel account

2. Navigate to **Settings** → **Project Settings** → **Service Accounts**

3. Create a new service account or use an existing one

4. Gather the following credentials:
   * **Username**: Service account username
   * **Secret Key**: Service account secret
   * **Project ID**: Your Mixpanel project ID (found in Project Settings)

5. Enter these credentials in Cargo when connecting

## Mixpanel data models

### Fetch events

Pull product analytics events from Mixpanel into Cargo.

**Configuration:**

* **From date**: Start date for fetching events

**Features:**

* **Incremental sync**: Only fetches new events since the last sync
* **Minimum interval**: 12 hours between syncs

**Use cases:**

* Trigger workflows based on product usage patterns
* Identify highly engaged users for sales outreach
* Build lead scoring models using product analytics
* Create segments based on feature adoption

## Event data

Mixpanel events typically include:

| Field        | Description             |
| ------------ | ----------------------- |
| event        | Event name              |
| distinct\_id | User identifier         |
| time         | Event timestamp         |
| properties   | Custom event properties |

## Best practices

* Use consistent `distinct_id` values that map to your CRM contacts
* Define key activation and engagement events in Mixpanel
* Set appropriate sync intervals based on your workflow needs
* Combine Mixpanel data with enrichment data for complete lead profiles