Create your first product
A product in Beacon represents one application you want to track — for example, your desktop app, your web app, or your back-end service. Most customers create one product per application they ship.
This page walks you through creating your first product. It takes about 1 minute.
Why products matter
Every event Beacon ingests is tagged with the product (and version) it came from. Products let you:
- Filter dashboards and reports to a single application.
- Apply different allowlists, properties, and retention rules per product.
- See which application is generating which events when you ship multiple apps under one account.
You can create as many products as you need on every plan — there’s no per-plan product limit.
Step 1 — Open the Products page
In the sidebar, expand Settings and click Products.
If you have permission to manage products (default for the account creator), you’ll see a Create Product button in the top-right.
Step 2 — Fill in the form
Click Create Product. A modal appears with three fields:
| Field | Required | Notes |
|---|---|---|
| Display name | Yes | The human-readable name. Appears in dropdowns and headers throughout Beacon. Example: “Inventory Manager.” |
| Slug | Yes | A URL-safe identifier used in the API and SDK config. Must start with a lowercase letter or number and contain only lowercase letters, numbers, dots, hyphens, or underscores (^[a-z0-9][a-z0-9._-]*$). Example: inventory-manager or inventory.manager. |
| Description | No | Optional notes about what this application does. Helpful when team members are working with multiple products. |
The slug is what your SDK will send as Product (.NET) or product (C++ / JS) when it ingests events — match exactly. The slug cannot be changed after creation, but the display name and description can.
Step 3 — Submit
Click Create. On success:
- A green toast appears: “Product Display Name has been created.”
- You’re navigated to the product’s detail page.
If a product with the same slug already exists in your organization, you’ll see “A product with this slug already exists” inline on the slug field. Pick a different slug.
Step 4 — Note the slug
Write down or copy the slug. You’ll use it when configuring your SDK in Install an SDK — the SDK’s product value must match exactly, otherwise events won’t be associated with this product.
What’s next
You have a product. Next, generate an API key the SDK will use to authenticate when sending events.
Common questions
Should I create one product per application, or one product per release channel?
One per application is the convention. Use the SDK’s product_version field to distinguish releases, and use Beacon’s version-filtered analytics to compare versions side by side.
Can I rename a product after creating it? The display name and description, yes — open the product’s detail page and edit them. The slug, no — pick the slug carefully.
Can I delete a product? Yes, from the product’s detail page. Deletion is non-reversible and removes all events associated with that product. Use Archive instead if you want to soft-disable a product (note: as of this writing the Archive UI has been removed pending redesign — contact support if you need to soft-disable).