# Dashboard tour

The first 20 minutes after sign-up: create a project, register your app, hand the SDK key to your engineer, build a campaign, and verify it's firing. Each step links to a deeper how-to.

**Use this when** you're new to Amply and want a guided path from empty dashboard to first live campaign. **Don't use this when** you already know the workflow — jump straight to [Creating a campaign](/user-guide/creating-a-campaign.md) or [Price management](/price-management/price-management.md).

## Two areas

The dashboard is split in two:

* **Project sidebar** (left) — project-scoped: **Dashboard**, **Campaigns**, **Events**, **Price Management** (gated), **Builder** (gated). Switching projects swaps the contents.
* **Avatar menu** (top right) — organization-scoped (**Organization settings**, **Projects**, **Teams & Members**, **Billing**) plus your personal **Profile settings**. Stays the same wherever you are.

## Create your first project

A project is the workspace for one product. Create more projects when you need to keep separate apps' data, campaigns, and events apart.

1. From the avatar menu, open **Projects**.
2. Click **New project** in the top right. The form heading reads **Create a new project**.
3. Fill in **Project name** and click **Create Project**.

You can switch between projects from the same Projects screen.

## Add your iOS or Android application

Each binary you ship is one **application**. A project can hold several — typically one iOS and one Android.

1. From the Projects list, click your project to open it.
2. On the **Applications** screen, click **New application**. Heading: **Create a new application**.
3. Fill in:
   * **Application Name** — what you'll see in dropdowns later.
   * **Bundle Id** — the iOS bundle identifier or the Android package name (e.g. `com.example.app`).
   * **Platform** — **iOS** or **Android**.
4. Click **Create Application**.

Repeat for the second platform. Both end up in the same Applications list.

## Hand the SDK key to your engineer

Each application has its own pair of API keys (public + secret) that the SDK uses to identify the device and authenticate calls.

1. From the Applications list, click your application to open the edit screen. Heading: **Edit "\<app name>"**.
2. Open the **API Keys** tab (third tab, alongside General and Integrations).
3. The table shows **Public key**, **Secret key**, and **Last used**. Each row has a copy icon and a toast confirms when the value is on your clipboard.
4. If the table is empty, click **Add Api Key** in the top right of the page (only visible while you're on this tab).
5. Send the public + secret pair to your engineer. They'll need both for the SDK config — see [Installation](/developer-guide/installation.md).

You can rotate keys later — the row menu offers a **Revoke** action; just generate a new pair first so the SDK never has zero valid keys.

## Create your first campaign

A campaign decides who sees something in the app, when it fires, and (for Deep Links) what URL opens.

1. From the project sidebar, open **Campaigns**.
2. Click **New campaign**. The form has two steps for **Rate & Review** (**Who** and **When**) and three steps for **Deep Link** (adds **What**).
3. On the last step, click **Finish**. The campaign saves as **Draft**.
4. Open the new campaign and click **Start campaign** to activate it.

Full walk-through: [Creating a campaign](/user-guide/creating-a-campaign.md). For options each campaign type supports, see [Campaigns](/user-guide/campaigns.md).

A campaign saved as Draft does nothing until you start it.

## Verify it's firing in Events

Events is where you confirm the SDK is reporting what you expect — useful both right after wiring up the SDK and after every campaign change.

1. Open **Events** from the project sidebar.
2. The table lists every event name the SDK has reported, with **Last Seen** per platform (iOS / Android icon + timestamp) and an **available** toggle.
3. After you trigger your campaign on a test device, refresh and check that the event row's Last Seen updated.
4. If a custom event isn't in the list yet, the SDK hasn't sent it from any device in this project — trigger it in the app first.

The **available** toggle controls whether an event appears in the campaign trigger dropdown — flip it off for noisy or internal events you never want to target.

## Invite teammates

To add someone to the organization, open **Teams & Members** from the avatar menu. The screen shows everyone in the org, filterable by **All / Active / Pending / Banned / Rejected** status, with **Name**, **Role**, and **Status** columns.

The exact invitation flow depends on how your account was set up — if you don't see an obvious **Invite** action, contact Amply support.

## Upgrade the plan

Some features (Price Management, Builder) only appear once your plan includes them. To change plans:

1. Open **Billing** from the avatar menu.
2. On the free plan you'll see the available **plans** alongside your current one. On a paid plan you'll see your current plan and **Invoices**, with an **Upgrade** action that takes you to a separate plan-change view.
3. Pick the new plan and follow the checkout to confirm.

After the change goes through, the gated sidebar items become available.

## Related

* [Overview](/user-guide/overview.md) — what each area is for, conceptually
* [Creating a campaign](/user-guide/creating-a-campaign.md) — the next deep dive
* [Price management](/price-management/price-management.md) — if your plan includes it
* [Sessions and events](/user-guide/sessions-and-events.md) — what the Events screen is for
* [Installation](/developer-guide/installation.md) — what your engineer does with the API key


---

# Agent Instructions: 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/user-guide/dashboard-tour.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.