In this article
In this article
Install your web button to start collecting feedback on your site. This guide helps you get started installing your web button, creating active feedback campaigns, integrating with your data layer, and troubleshooting the implementation.
Even if you don’t want to use the web button, you need to install it on your website. Active feedback campaigns won’t work if the web button isn’t installed. You can use our JavaScript API to hide the button on certain pages.
Using GetFeedback, you’ll set up a feedback button so users can provide feedback on your website.
This feedback button needs to be implemented once on your website. After this, you can manage the button right from your GetFeedback account. Your button will automatically be updated when you make changes.
To get started with feedback buttons:
You can easily install your feedback button using a tag management system. Tag management systems let you control page load rules, use tags and triggering, and add other conditions.
GetFeedback is compatible with any standard tag manager. Here are links to implementation instructions for common tag management systems:
If you're using multiple buttons (e.g. different sized buttons for mobile and desktop) on a responsive website, contact us for a code snippet that will show the correct button to your visitors based on their screen size or device.
If you don’t use a tag management system, you can install your web button directly on your site. The snippet allows the GetFeedback code to run on your website using an <iframe>.
To implement GetFeedback for Web on your website:
Your button will now be displayed on every page where you added the code. If you don't wish to show your button yet, turn it OFF in Setup.
If your website uses a Content Security Policy (CSP), you’ll need to add a hash to your website’s script-src. To find this hash, go to Setup. Find your feedback button. Then, select Options > Installation. Copy the hash below your button code and add it to your site.
Once you install your web button, you can use campaigns. Web campaigns allow you to actively target surveys to a specific group of visitors on your website.
To get started with web campaigns:
You can push data from your web button to your data layer. This allows you to send data to third-party tools, such as Google Analytics, or bring data from your data layer into GetFeedback. Learn more
When implementing GetFeedback for Web, keep the following in mind:
When a user leaves feedback on your page using the GetFeedback feedback button a screenshot will be created that’ll be attached to the feedback item. This screenshot is generated by using the HTML of your page. You must verify that your site code is valid to make sure your screenshots generate correctly.
You can also modify or stop generating screenshots, if needed. Learn more
You can do a markup validation by using the Markup Validation Service of W3C. Common issues that could cause errors are:
Markup validation is the process of checking a Web document against the grammar (generally a DTD) it claims to be using.
Web pages are written in a markup language (e.g. HTML). Markup language must comply with certain rules. You can check this compliance by doing markup validation.
Pages on local servers, or servers in a closed environment, may cause issues with your web feedback button.
GetFeedback won’t work when your page uses files that are located within the same computer, such as a page using the File URI scheme. The GetFeedback code mirrors the scheme and protocol that is used for the page it’s installed on.
On locally-hosted pages (for example, on a staging environment or an intranet website), the screenshot feature doesn’t work correctly. In most cases, our server isn’t able to access the resources needed to create the screenshots.
To resolve this issue, you can either:
In some cases, you’ll want to combine GetFeedback with other software, like Google Tag Manager, to get the most out of your customer feedback. Below is a list of common tools that may be helpful when troubleshooting or testing your GetFeedback implementation: