Aglet

Make your first problem actionable.

Start with a Work Item for something you want to improve. Or try the included sample to see how a Signal becomes work. You can do either before connecting another service.

Create an account

Start with a problem you already know.

A slow screen, a confusing checkout, or a repeated customer question is enough. You do not need an ingestion key to create a Work Item.

  1. Choose a workspace and project

    Open your workspace, then create or choose the project for the product you want to improve. Keep related Signals and Work Items in that project.

  2. Create a Work Item

    Open Work items in the project navigation and choose Create Work Item. Use a title that describes the problem, then add what happens and what you expected.

  3. Give it an owner and a next step

    Choose an owner and priority in the form, then save. Use the Work Item’s discussion to record the next check or decision. You can refine the details later.

  4. Leave a result someone can check

    Keep the observations and decisions with the Work Item as it progresses. A status change records progress; it does not by itself prove the problem is fixed.

Need help framing the problem? Find a relevant playbook.

Try a Signal and linked Work Item.

The built-in check creates labeled sample records in a test environment. It does not send customer data or test delivery from your app.

  1. Open the workspace setup guide

    Create or choose a project, then follow the guide to create a non-production test key. Save the secret when it is shown; it is displayed only once.

  2. Queue the sample

    Open the project’s Event intake page from its overview or setup guide. Choose the test key and select Queue sample error. This step requires a workspace owner or administrator.

  3. Follow the result

    Check the request status on Event intake. When the check finishes, open its Signal and linked Work Item. The project overview also links to the sample result.

Ready to send an event from your own app? Event intake includes request examples for your project. Review the available connection paths before choosing a provider.

Get unstuck.

I cannot see the action described here

Check the workspace and project names in the header. Available actions depend on your role. Ask a workspace owner or administrator if you need access; the sample sender is available only to those roles.

The sample has not produced a result

Return to Event intake and check the request status before queuing another sample. A queued request has not finished. If it failed, read the reported error and use the page’s available recovery action. If the sender is unavailable, you can still start with a Work Item.

Feedback is empty

Automatic feedback collection and grouping are not available yet. An empty view does not mean setup is still running. Record a known customer problem as a Work Item while collection is unavailable.

I saved a connection but no data arrived

A saved provider mapping records setup details; it does not activate access to the provider. Review the connection’s current state and the project’s Event intake instructions. The GitHub sample does not connect your GitHub account.

I cannot find work I created

Check the workspace and project in the header, then open Search. Search a phrase from the title or description. Work Items search includes archived work; the Work items list normally shows active work.

Still stuck? Contact us with the step you reached and the error message. Keep passwords, keys, and customer data out of your message.

Choose one problem to work on.

You can add connections after the first Work Item has an owner and a clear next step.

Create an account