> For the complete documentation index, see [llms.txt](https://docs.amply.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amply.tools/getting-started/quickstart.md).

# Quickstart

The fastest path from zero to a working Amply integration. Set up a project in the dashboard, then jump to your platform-specific tutorial.

**Prefer not to do it by hand?** Use [AI-assisted integration](/getting-started/ai-assisted-integration.md): connect the Amply MCP and the `amply-integration` skill to your AI coding assistant and have it create the project, wire the SDK, and hand you a diff to review. This page is the by-hand path.

**Prerequisites**

* An Amply dashboard account ([sign in](https://app.amply.tools))
* Your app project on iOS, Android, or React Native

**You'll end with**

* A project and application created in the Amply dashboard
* API keys ready to paste into your app
* A clear next step into the platform tutorial that wires the SDK and sends your first event

## 1. Create a project in the dashboard

A project groups one or more applications (iOS, Android, etc.) under the same set of campaigns and settings.

1. Open the dashboard.
2. Click **New project** and give it a name that matches your product.
3. Inside the project, click **New application**. Enter a name, set **Platform** to **iOS** or **Android**, and enter your app's **Bundle Id**.

Repeat the second step for each platform you ship.

## 2. Get your API keys

Open the application you just created and go to the **API Keys** tab. Click **Add Api Key** to generate a key pair. You'll need three values for the SDK:

* **App ID** — the application's identifier (visible on the application page).
* **Public key** — from the API Keys table.
* **Secret key** — from the API Keys table (the value is masked; use the copy button to grab it).

Hand all three to whoever wires the SDK into the app — typically your engineer.

## 3. Pick your platform tutorial

The next step is platform-specific. Each tutorial installs the SDK, initializes it with the keys from step 2, sends a first event, and verifies it shows up in the dashboard.

* [iOS Quickstart](/developer-guide/quickstart-ios.md) — Swift, UIKit, and SwiftUI.
* [Android Quickstart](/developer-guide/quickstart-android.md) — Kotlin and Gradle.
* [React Native Quickstart](/developer-guide/quickstart-react-native.md) — JS/TS, both Bare and Expo.

The concepts are the same across platforms; the API shapes differ.

## What's next

After your first event reaches the dashboard:

* [Create your first campaign](/user-guide/creating-a-campaign.md) — act on the event you just sent.
* [Set user identity and properties](/developer-guide/user-attributes.md) — target users more precisely.
* [Handle deeplinks from campaigns](/developer-guide/handling-deeplinks.md) — let scenarios navigate inside your app.

## Related

* [How Amply fits](/getting-started/how-amply-fits.md) — what the SDK does with the events you send
* [Installation](/developer-guide/installation.md) — versions, deployment targets, and package managers per platform
* [User Guide](/user-guide/overview.md) — build and manage campaigns


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.amply.tools/getting-started/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.