This article describes how to set up Amplitude and get familiar with the basics.

Amplitude is an event-based analytics tool that tracks user behavior based on in-product interactions and analyzes that behavior in real time.

## Send data

Without a data source, Amplitude can't show you who your customers are or how they behave in your product. Pick one source to start with and add more later if you need to. Send data to Amplitude client-side, server-side, or through a third party.

Amplitude supports two main ways to send data:

1. [Import existing data](#import-existing-data) if you have data stored elsewhere.
2. [Track data](#track-product-data) using Amplitude SDKs and APIs if you're starting from scratch.

After you set up your source, use the [debugging guide](/docs/analytics/debug-analytics) to check your initial setup.

### Import existing data

If you already collect data outside Amplitude, you can stream events directly from your chosen source by adding a [source](/docs/data/source-catalog) or [SDK](/docs/sdks/analytics).

### Track product data

{% callout type="tip" heading="Automate setup with the CLI" %}
Use the [Amplitude setup wizard CLI](/docs/get-started/setup-wizard-cli) to configure your SDK, generate tracking code, and start sending events in minutes.
{% /callout %}

You can track your product data using Amplitude SDKs or APIs:

1. Determine which data source works best for your product. Refer to [client-side vs server-side sources](/docs/sdks/client-side-vs-server-side).
2. Install a data source with an [SDK](/docs/sdks/analytics) or [API](/docs/apis/analytics/http-v2).
3. Tag a few [important events](#what-events-to-track) upfront.

## What events to track

{% callout type="note" heading="Know key concepts before you get started" %}
Go to [What is Amplitude?](/docs/get-started/what-is-amplitude/) for definitions of users, events, and properties.
{% /callout %}

If you're just starting out, resist the urge to track everything upfront. The number of events you should track depends on the complexity of your product.

Consider starting with two important events in your product to give you initial insights.

Use these sample questions to get you thinking:

| Questions                                                                                      | Events                                        |
| ---------------------------------------------------------------------------------------------- | --------------------------------------------- |
| How many daily active users or how many logins per week do I get?                              | **Login** event                               |
| What percentage of users who add an item to their cart successfully check out?                 | **Add to Cart** event and **Checkout** event  |
| What percentage of sign-ups request a demo?                                                    | **Sign Up** event and **Request Demo** event  |
| What's the retention rate? How many users come back to the product two weeks after signing up? | **Sign Up** event and **Session Start** event |

After you successfully track these events, you can [track more](/docs/data/data-planning-playbook).

## Create a tracking plan

As you advance, it's critical to [create a tracking plan](/docs/data/create-tracking-plan) document that outlines what events and properties to track, why you're tracking them, and where they're tracked. A tracking plan should derive from the business outcomes you're trying to measure or improve.

If you're using Amplitude SDKs, Ampli Wrapper is a lightweight wrapper over the Amplitude SDK that provides type safety, supports linting, and enables features such as input validation. Ampli CLI works together with the Ampli wrapper to bring a tracking library into your project. Learn more about [Ampli](/docs/sdks/ampli).