Add a feedback widget to a Glide app

Can you add a script to a Glide app?

Glide apps are usually built from components, not from pages you can edit with code. If your app has no area for custom scripts, the feedback widget cannot run inside it. The alternative is the hosted feedback page, a standalone form at a link you control. A button in your app opens that link, and the visitor sends feedback without leaving your product's design for long.

The hosted page uses your product's accent color and works in any browser, so it suits a Glide app well. It is not indexed by search engines, which is what you want for an internal form.

How do you set up the hosted feedback page for a Glide app?

1. Create a product for this app in Escuta Produto. Keep the name short and recognizable, because it shows in the inbox filter.
2. Note the product slug. The hosted address follows this pattern: https://escutaproduto.com/f/your-product-slug.
3. Pick a language. Add ?lang=en for English or ?lang=pt for Portuguese.
4. In the app editor, add a button to the screen where feedback belongs, such as a help or settings screen.
5. Set the button action to open a link, then enter the full address:

https://escutaproduto.com/f/your-product-slug?lang=en

Use the link action rather than a navigation action that stays inside the app. The form needs a web page to load, so the link must point to the hosted address.

How do you prefill the email from the signed-in user?

Add the email parameter to the end of the address, and fill it with the email column from your users table. The hosted page reads the value and fills the email field, so the visitor does not type it again. The full address then looks like this:

https://escutaproduto.com/f/your-product-slug?lang=en&email=USER_EMAIL

Replace USER_EMAIL with the value from your app's dynamic data, using the app's value picker rather than typing a name. Build the link from the column so each user gets an address with their own email in it.

Two details prevent surprises. A plus sign in a query string can be read as a space, so an address such as name+tag@example.com may arrive wrong. Encode the value when you build the link. Also, guest users have no email, so the link still works and the field simply stays empty.

If your app has users in more than one language, create one link per language. Keep the same product slug in both addresses, and change only the lang value, so both languages feed the same inbox and the same filters.

Why should each Glide app have its own product?

The inbox filters by product, so each product is a clean stream of feedback. If you run three Glide apps and send them all to one product, a bug in the scheduling app sits next to a request for the expense tracker, and you cannot tell which team should act on it.

One product per app also keeps the hosted addresses simple. Each button carries the slug of the app it belongs to, so feedback always lands in the right place without any extra logic in the app.

Keep the button where people already look for help. A link on a settings or help screen works better than a button buried on a deep screen, because a user who is stuck tends to look for help near the place they got stuck. You can also place a second link on the screen where users first sign in, so new users know feedback is welcome from the start.

How do you check the Glide feedback button on a phone?

Glide apps are most often used on phones, so test there rather than in a desktop browser.

1. Open the app on a phone, using the same version your users see.
2. Tap the feedback button and confirm the hosted page opens with your product name.
3. Check that the email field is filled when you are signed in, and empty when you test as a guest.
4. Send a test message with the words "test from Glide" so you can find it in the inbox.
5. Open the item in the inbox and confirm the saved page information matches what you tested.

If the page does not open, check that the address starts with https and that the slug matches the product exactly. A typo in the slug sends visitors to an error instead of your form.

Doing Glide feedback in Escuta Produto

Each Glide product gets its own inbox. Use the type filter to separate bugs from ideas and praise, and the status filter to show what you have planned or closed. Because the hosted page has no script, the feedback arrives as a plain form submission with the message, the type and the email the visitor used.

Write private internal notes when you decide something. A note such as "planned for the next release, asked by three teams" helps the next person understand the decision without asking you.

Related

• The hosted page and its parameters are described in the hosted page docs.
• For apps that do allow a script, the widget docs cover the floating button and the JavaScript API.
• Other no-code builders have their own steps. See Softr and Webflow.
• To compare a structured form with a plain email link, read feedback widget vs a mailto link.