# Overview A high-level tour of what you can do in the Amply dashboard without writing code. Use this to find the right screen for the task, then click through to the deep page. **Use this when** you're new to Amply and want to know where things live, or when you're orienting a new teammate. **Don't use this when** you already know what you want to do — go straight to the task-specific page. ## Starting point After you sign in, the dashboard is organized around four things, top to bottom: 1. **Projects** — the workspace for an app or a group of apps 2. **Applications** — the individual iOS or Android apps inside a project 3. **Campaigns** — what you actually ship to users 4. **Events** — what users and the SDK report back Billing, team members, and profile settings live alongside these, under the same admin area. ## Projects A project is the container for everything else. Each project has its own applications, campaigns, and event history. Most teams keep one project per product. * **Create or switch project:** project list in the admin area * **Rename, archive, or configure:** project edit screen See: [Dashboard tour — Create your first project](/user-guide/dashboard-tour.md#create-your-first-project) ## Applications An application represents a shipping app binary — typically one per platform. A project can have several applications (for example, an iOS build and an Android build of the same product). The application is also where the SDK's API key lives. If a developer needs credentials to wire the SDK into an app, you'll generate them here and hand them over. * **List / add / edit applications:** applications screen inside the project See: [Dashboard tour — Add your iOS or Android application](/user-guide/dashboard-tour.md#add-your-ios-or-android-application) ## Campaigns Campaigns are the main unit of work in Amply. A campaign decides who sees something in the app, when it fires, and what happens when it does — a deep link, a rate-and-review prompt, or (soon) a blocking screen. From the Campaigns screen you can: * Filter by state: **All**, **Draft**, **Active**, **Cancel** * Create a new campaign via **New campaign** * Open a campaign to view, edit, change state, or delete it A campaign is built in steps: **Who** (audience), **When** (trigger event and frequency), and for Deep Link campaigns, **What** (the URL to open). See: [Creating a campaign](/user-guide/creating-a-campaign.md), [Campaigns](/user-guide/campaigns.md), [Targeting an audience](/user-guide/targeting-an-audience.md) ## Events The Events screen is a catalog of every event name the SDK has seen for this project, across all devices — both SDK-generated events and your own custom events. You'll use it for three things: * Confirming that a new event your engineer just added is actually arriving * Checking when an event was last seen on iOS vs Android * Turning an event on or off for campaign use, per event Events are the raw material for campaign triggers and for audience rules that look at past behavior. See: [Sessions and events](/user-guide/sessions-and-events.md) ## Team and access Under team settings you can: * Invite teammates to the organization * Manage who has access to which project See: [Dashboard tour — Invite teammates](/user-guide/dashboard-tour.md#invite-teammates) ## Billing Billing covers your organization's plan, payment method, invoices, and plan upgrades. If you're on a free plan, some advanced features (for example, price management tooling) are hidden until you upgrade. See: [Dashboard tour — Upgrade the plan](/user-guide/dashboard-tour.md#upgrade-the-plan) ## Price management If your plan includes it, a **Price Management** entry appears in the navigation. Use it to plan, preview, and submit price changes for your in-app subscriptions and one-time products across every country the app sells in — right from the dashboard, no code required. See: [Price management](/user-guide/price-management.md) ## Profile and organization The profile screen holds your personal details and password. The organization screen holds your organization name and org-wide settings. See: [Dashboard tour — Two areas](/user-guide/dashboard-tour.md#two-areas) ## Recurring tasks Day-to-day work in the dashboard usually involves: 1. Opening **Campaigns** to review what's Active. 2. Creating or editing a campaign — audience, trigger, content — and moving it from Draft to Active. 3. Checking **Events** to confirm the triggering event is arriving from real devices. 4. Adjusting targeting or frequency when a campaign fires too often or too rarely. ## Related * [Creating a campaign](/user-guide/creating-a-campaign.md) — end-to-end walkthrough * [Targeting an audience](/user-guide/targeting-an-audience.md) — the rule builder, explained * [Campaigns](/user-guide/campaigns.md) — campaign types and options * [Sessions and events](/user-guide/sessions-and-events.md) — what the events screen tells you --- # 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/overview.md?ask= ``` 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.