> ## 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.

# Amplitude

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

## How to set up Amplitude

### Authentication

Amplitude requires API credentials:

1. Log in to your Amplitude account
2. Navigate to **Settings** → **Projects** → Select your project
3. Find your credentials:
   * **Region**: US or EU (based on your data location)
   * **API Key**: Your project API key
   * **Secret Key**: Your project secret key
4. Enter all credentials in Cargo when connecting

## Amplitude data models

### Fetch events

Pull product analytics events from Amplitude into Cargo.

**Configuration:**

* **Start date**: Begin fetching events from this date

**Features:**

* Incremental sync (only new events since last sync)
* Minimum 12-hour sync interval
* Unifies as contact events

**Data includes:**

* Event name
* User ID
* Event properties
* Timestamp
* Session data

## Event data structure

Amplitude events typically include:

| Field             | Description             |
| ----------------- | ----------------------- |
| event\_type       | Name of the event       |
| user\_id          | User identifier         |
| event\_time       | When the event occurred |
| event\_properties | Custom event data       |
| user\_properties  | User attributes         |
| platform          | Device platform         |
| country           | User's country          |
| city              | User's city             |

## Best practices

* Define key activation events in Amplitude
* Use consistent user IDs that map to your CRM
* Set meaningful sync intervals based on your use case
* Combine Amplitude data with enrichment for complete profiles
* Build lead scoring models using product engagement signals

## Use cases

* **Lead qualification**: Score leads based on product usage
* **Sales enablement**: Surface product usage data to sales
* **Customer success**: Monitor account health
* **Marketing**: Trigger campaigns based on behavior