> For the complete documentation index, see [llms.txt](https://docs.feedbackly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feedbackly.com/website-widgets/getting-started.md).

# Getting started

## Installing the website widget

Get the embed script from the Dashboard and integrate it into your website code directly or utilize GTM or a similar tool. The code should look like this:

```
<!-- UNIVERSAL FBLY WEBSITE SCRIPT -->
<script async src="https://embed.feedbackly.cloud/widget.js"></script>
<script>
window.fblywc = window.fblywc||[];function fblytag(){fblywc.push(arguments);}
fblytag("oid", "<OID>");
fblytag("dmn", "<DMN>");
</script>
<!-- Eo UNIVERSAL FBLY WEBSITE SCRIPT -->
```

### Verifying installation

Go to your website and open up the developer console in your browser. In Chrome, this can be done via the command `⌘ + option + J`

Find the console from the bottom of the developer tools. Type in `FBLY` and press enter. If your plugin is installed properly, the command should return `true`. Your plugin is all set up!

![](/files/-M-Q827NQawL9lZh-cQ2)

If the script is not installed, you'll get an error like so:

![](/files/-M-Q8CgSlMkWOg8azyTH)

If this is the case, please verify that the plugin is installed properly on your website.\
\
**See also:**&#x20;

{% content-ref url="/pages/-M-Q6Tr\_hu3vTvq0S7V5" %}
[Debugging website widgets](/website-widgets/debugging-website-widgets.md)
{% endcontent-ref %}

### Async script loading and custom actions

Because **FBLY.actions** may not be available when trying to use custom actions and properties because of a late async loading of the main script, please load this script before your custom code:

```
<script src="https://embed.feedbackly.cloud/actions.js"></script>
```

or alternatively use the code found from that file as inline.

**See also:**

{% content-ref url="/pages/-M-Q6GpmiWQ8R3Z\_8Hd9" %}
[Attaching custom metadata to responses](/website-widgets/adding-custom-metadata-to-responses.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M-Q6Me2\_7ND8sZq9xAH" %}
[Triggering surveys via custom properties](/website-widgets/adding-custom-triggering-properties-to-widget.md)
{% endcontent-ref %}

{% content-ref url="/pages/SA0UbUFRx6orgFtYMDMn" %}
[Widget Hooks](/website-widgets/widget-hooks.md)
{% endcontent-ref %}

{% content-ref url="/pages/q9MzKxE4jaXB8cbYEZ2G" %}
[Setting the language](/website-widgets/setting-the-language.md)
{% endcontent-ref %}

### Custom configurations

For embedded survey widget, instead of inserting manually DIV tag to the website (found from Feedbackly dashboard) to mark a place where widget should be rendered, you can use these script configurations to define the position.

For \<ID>, use ID found from the original DIV tag: **fbly-embedded-\<ID>.**

```
fblytag("embedid", "<ID>"); //for auto tag generation for embedded survey widgets.
fblytag("appendto", "footer"); //optional: <element name> | #<div id>. Example: footer | #mydivid
fblytag("position", "top"); //optional: top | inside
```