Send data into Amplitude, organize and clean it, and activate it across your downstream tools. Connect sources, resolve identities across devices, govern your taxonomy, and stream behavioral data to the rest of your stack.

{% outcomes heading="Explore Data" %}
{% outcome icon="Plug" title="Get every event into Amplitude" href="/docs/data/source-catalog" %}
Stream activity from SDKs, servers, warehouses, and pre-built sources so no behavior goes uncounted.
{% /outcome %}
{% outcome icon="Database" title="Activate insights in your stack" href="/docs/data/destination-catalog" %}
Send behavioral data and cohorts to the marketing, ad, and warehouse tools your team already uses.
{% /outcome %}
{% outcome icon="Users" title="See one user, not many" href="/docs/data/profiles" %}
Stitch warehouse profile data to behavioral events so each person is the same user across devices.
{% /outcome %}
{% outcome icon="ShieldCheck" title="Trust the data your team queries" href="/docs/data/create-tracking-plan" %}
Lock in a tracking plan, review changes, and keep events on-spec as your product evolves.
{% /outcome %}
{% outcome icon="Workflow" title="Fix data without redeploying" href="/docs/data/transformations" %}
Rename, redact, or reshape events on the way in instead of waiting on an instrumentation fix.
{% /outcome %}
{% outcome icon="ClipboardList" title="Add the context analysts need" href="/docs/data/lookup-tables" %}
Join reference data like plans, regions, or accounts to events so every chart has the full picture.
{% /outcome %}
{% /outcomes %}

## Plan and collect data

Start with an implementation plan that defines the events, users, and properties your team needs.

- [Plan your implementation](/docs/get-started/plan-your-implementation) to connect product questions to the events you track.
- [Create a tracking plan](/docs/data/create-tracking-plan) to document event names, properties, and ownership.
- [Choose client-side or server-side tracking](/docs/data/client-side-vs-server-side) to match your product architecture.
- [Use Autocapture](/docs/data/autocapture) to collect website interactions before you manually instrument every event.

## Govern and activate data

Keep your taxonomy healthy, then send trusted data to the teams and tools that need it.

- [Configure schema](/docs/data/configure-schema) to monitor event volume, property types, and unexpected changes.
- [Transform incoming events](/docs/data/transformations) to rename, redact, or reshape data after ingestion.
- [Manage data access controls](/docs/data/data-access-control) to limit access to sensitive events and properties.
- [Forward data to destinations](/docs/data/destination-catalog) to activate behavioral data in downstream tools.

{% academy-link
   title="Get Started with Amplitude Data"
   url="https://academy.amplitude.com/getting-started-with-amplitude-data"
   description="Learn the fundamentals of Amplitude Data."
/%}