Skip to main content
My app connects your product to Project Echo so end-users are identified as portal members. You install an embed script, pass user attributes from your backend-rendered page, and open the feedback portal with a pe_token when needed.

Open My app

  1. Go to Integrations in the Workspace nav.
  2. Select My app.
  3. Create an embed key with a label and allowed origins (your app’s HTTPS origins).
  4. Copy the embed token when shown — it is revealed once.

Install the embed snippet

Paste the snippet from Integrations → My app into pages where users should be identified. Replace placeholders server-side with the signed-in user’s id, email, and profile fields.
Typical attributes include external user id (required), email/name/avatar, and optional company external id. Identify runs quietly on load. data-pe-portal-link merges ?pe_token= when users open the portal. If you use a verified custom domain (Pro), point data-pe-portal-base-url and portal hrefs at that same origin everywhere.

Member tokens and pe_token

The embed flow mints short-lived member tokens so the portal knows who is signed in. Links that include pe_token keep member-only portal behavior (submit feedback, vote, etc.) aligned with your product’s user.

Checklist

  • Serve the snippet only from allowed origins you configured.
  • Never expose embed secrets in a public git repo.
  • After changing custom domain settings, update deployed embed attributes so origins match.
CDN / embed script details are shown live on Integrations → My app. Support: [email protected] · Help Center.