Add a feedback widget to a Podia site

Can you add a script to a Podia site?

Podia sites can inject custom code site-wide, which is the place for the feedback widget. Paste the script tag once, publish, and a floating Feedback button appears on the pages that use that code. Custom code may depend on your Podia plan, so confirm that your site allows it before you start.

When you cannot inject code, or when a page type ignores site-wide code, the hosted feedback page is a reliable alternative. It is a standalone form at a link, so it works anywhere you can place a link, including product pages, downloads and community posts.

How do you inject the widget site-wide?

Podia calls the setting by different names over time, so look for the code injection, custom code or header and footer area in your site settings. The field you want runs on every page.

1. Open your site settings and find the code injection area.
2. Paste the script tag from your product's install page:

<script src="https://escutaproduto.com/widget.js" data-key="pk_your_product_key" defer></script>

3. Save the change and publish the site. Injected code reaches visitors only after the site is live with the new version.
4. Open a page in a private window and check that the button appears.

The script is about 5 KB compressed and has no dependencies. It loads with defer, so it does not hold up the page, and it renders inside a Shadow DOM so the button keeps its own styling. Use data-color with any CSS color if you want the button to match your brand.

Does the widget work on digital product pages?

Product pages are where buyers notice problems first. A download link that returns an error, a file that will not open or a step in a guide that does not match the product all show up there. A floating button on the product page lets a buyer report the problem at the moment they hit it.

Check the layout on the live product page. Some product templates place their own buttons near the bottom of the screen, and the floating button should not cover the add-to-cart or download controls. The position option lets you move the button to the left if the right side is crowded.

How do community pages fit in?

If your Podia site includes community or member areas, check whether they use the same site-wide code. Many members will report bugs or ask for features from inside those pages, so a button there is useful. If a community area does not load the injected code, add a link to the hosted feedback page in the community guidelines or the welcome post.

Set a clear expectation for members. A pinned post that says what to report, and where, keeps the feedback focused. A question such as "Did a download fail or a lesson break?" gives members a sensible starting point.

When should you use the hosted page instead?

Use the hosted feedback page when any of these apply:

• Your plan or site setup does not allow custom code.
• A page type you need does not load site-wide code.
• You want a link in a course email, a receipt or a support reply.
• You are sending feedback requests to customers who may not browse the site.

The address follows this pattern, with a language option if your buyers read Portuguese:

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

The hosted page uses your product's accent color and is not indexed by search engines, so it works as a private form rather than a public page.

How do you test the widget on a live Podia site?

Test from a private window so you see the site as a buyer would.

1. Open a product page and confirm the Feedback button appears.
2. Send a test message that starts with "test from Podia", so you can find it later.
3. Open the item in the inbox and check that the page URL points to the product page.
4. Test on a phone, scrolling to the bottom of the page to check the button does not overlap the footer or a purchase control.
5. Open the hosted page link too, so you know the fallback works before a customer needs it.

Why does the Podia button not appear?

• The code may have been saved without publishing the site.
• The page may use a template that does not load injected code. Check a second page type to confirm.
• A blocked script is common with ad blockers and strict Content Security Policies. The browser console names the blocked file.
• A submission rejected with a 403 response means your site address is not in allowed origins. Add the full https address, and include the www version if visitors reach the site both ways.

Keeping Podia feedback in Escuta Produto

Create one product for the site, so product and community feedback sit together with a clear origin. Filter by type to separate bugs, ideas and praise, and by status to show what you are working on. The saved page URL tells you which product or community page a message came from.

Use internal notes to record why you chose a status, such as a bug you could not reproduce on your own machine. Notes are private to your team, so you can be direct about what happened, then reply to the buyer from your own email.

Related

• Every widget option, including identify and the JavaScript API, is in the widget docs.
• The hosted page parameters are in the hosted page docs.
• Other site builders are covered in Kajabi and Ghost.
• For ideas on where to ask for feedback inside a product, read feedback widget best practices.