> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/myra-master-your-ratings/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/myra-master-your-ratings/cookbook/collect-feedback-on-your-website-with-myra.md).

# Collect Feedback on Your Website with Myra

## Collect Feedback on Your Website with Myra

You can capture valuable customer insights directly from your own external website. With Myra, customers never have to log into the Atlassian ecosystem to share their thoughts, but all their feedback flows securely and instantly right into your Jira instance.

Here is how to set up your embedded feedback collection:

**1. Create a Public Survey**

First, you need to build a survey designed specifically for external web use.

* Navigate to the **Settings** tab and click **+ New**.
* Set the survey's **Scope** to **Public**.
* Define your **Calculation Strategy** (such as Average or NPS) and your preferred **Field Type** to dictate exactly how you want to receive the feedback.

**2. Enable Collection**

Once your survey is created, you must activate it to generate your unique sharing options.

* Open your newly created survey's **Settings** page.
* Go to the **Collection** tab and switch the **Enable Collection** toggle to the **On** position.

**3. Install the Myra Script (once per website)**

Myra now uses a single shared embed script per website. You only need to install it once, even if you embed multiple surveys or score widgets.

* Open the **Sharing & embed** tab in your survey settings.
* Copy the **Website embed prerequisite** script tag.
* Paste it into the `<head>` section of your website.

Example:

```html
<script src="https://<your-forge-app>.hello.atlassian.net/widget-embed.js" async></script>
```

{% hint style="warning" %}
**Breaking change — migration from older embeds**

If you previously embedded Myra using per-survey JavaScript objects (for example `window.myra_widget_<id>.open()`), you must migrate to the new model:

1. Add the shared `widget-embed.js` script to your site `<head>` (once).
2. Replace old trigger buttons with the **Collection embed markup** from the Sharing & embed tab (`data-myra-survey` attribute).
3. Replace old score widgets with **Public score display** markup (`data-myra-widget` attribute).

The old per-survey `onclick` API is no longer used.
{% endhint %}

**4. Add Collection Embed Markup**

With collection enabled, Myra generates a ready-to-use HTML snippet for opening the feedback form.

* In the **Sharing & embed** tab, locate **Collection embed markup**.
* Copy the snippet and place it anywhere in your page body — typically on a button or link.

Example:

```html
<button data-myra-survey="<encrypted-payload>" type="button">Rate us</button>
```

When a visitor clicks the element, Myra opens the survey in a popup. No custom JavaScript is required.

**5. (Optional) Embed a Public Score Display**

To show your live score on the same website, enable **Public score display** on the **Display & scoring** tab, then copy the widget markup from **Sharing & embed**.

Example:

```html
<div data-myra-widget="<encrypted-payload>"></div>
```

You can place multiple score widgets on different pages, including widgets from different surveys.

{% hint style="warning" %}
**Content Security Policy (CSP) Requirements**

If your website enforces a Content Security Policy (CSP), copy the exact directives shown in the **Sharing & embed** tab when collection is enabled. You typically need to allow the Myra script origin for `script-src`, `connect-src`, and `style-src` (including `'unsafe-inline'` for embedded survey styles).

Without these directives, your browser may block the widget script, styles, or form submissions.
{% endhint %}

You are officially live! Your website visitors can now submit feedback seamlessly, and your team can track, measure, and act on those responses directly inside Jira.

<figure><img src="https://3520262872-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkIFt9YZMR8h3a9n0Km6u%2Fuploads%2Fu2Tg09ELLeJGTqUGNDFv%2FPublic_feedback_after_survey_visible.png?alt=media&#x26;token=be99c5db-fa72-438d-b3b8-93977c67ff5a" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.meta-inf.hu/myra-master-your-ratings/cookbook/collect-feedback-on-your-website-with-myra.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
