Skip to documentation

Collect your first feedback

Create a workspace, choose a collection method, and verify your first real response.

Updated Read as Markdown

Pollenate has two collection workflows: widgets and custom interfaces send feedback events to an inbox; Feedback Pages collect a complete set of answers in a form. Start with the workflow you want to test.

Set up your workspace

  1. Create an account or sign in at Pollenate. Email sign-in uses a verification code. Social sign-in appears when a provider is available; passkeys can be configured from your account.
  2. Complete your profile. Join through a team invitation or request access if your email domain matches an organization that has verified it. Otherwise, create an organization and its first brand.
  3. Select the organization and brand you intend to use. A brand can represent an application, product, website or customer-facing identity.

Account creation does not imply a particular paid plan. Review current plans and Settings → Billing for the active plan and daily usage.

Option A: put a widget in your product

  1. Open Inboxes and create an inbox for the experience you want to measure.
  2. Create an organization API key with the collect scope in Settings → API Keys. A personal API key is not accepted by the widget collection endpoint.
  3. Open the widget builder, choose the inbox and widget type, then copy the generated installation code.
  4. Install it on a test page and submit a rating with a recognizable comment.
  5. Open the inbox and confirm that the new event, score and comment arrived.

Follow the script installation guide or React guide for complete examples.

Option B: share a feedback form

  1. Open Feedback Pages, choose a brand and create a form.
  2. Add a rating question and an optional text question, or draft questions with AI and review them.
  3. Set the form status to Published and save.
  4. Copy its link from Share & Embed, open it in another browser tab and submit a sample response.
  5. Return to the form's responses and analytics to verify the answer set.

An editor draft or an autosaved respondent draft is not a submitted response. See Build a Feedback Page.

If nothing arrives

Check the selected organization, brand and inbox or form. For a widget, verify the API key, inbox key and browser Network response. For a form, confirm that it is published and submissions are open. A success animation alone is not a substitute for checking the saved response.