> 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

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.
* After creation, use **Survey builder** to add extra questions, and **Appearance** to brand the form.

**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` or `data-myra-survey-inline`).
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 ready-to-use HTML snippets for collecting feedback. In the **Sharing & embed** tab, copy **one** of:

* **Popup button** — place this on a button or link. Clicking it opens the survey in a popup.

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

* **Inline form** — place this container where the form should appear on the page. No click is required; the survey renders in place.

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

No custom JavaScript is required. You can mix popup and inline embeds on the same site (and across surveys) as long as the shared script is installed once.

![Popup survey](https://cdn.sandbox.getmyra.app/public-frontend/via-storyboard/popups/survey-open.glossy.png)

![Inline survey](https://cdn.sandbox.getmyra.app/public-frontend/via-storyboard/inline/survey.glossy.png)

**5. (Optional) Pass hidden context with embed fields**

If you added **Embed field** questions in Survey Builder, put matching keys on the same popup or inline element:

```html
<button
  data-myra-survey="<encrypted-payload>"
  data-myra-fields='{"tenantId":"acme"}'
  type="button"
>
  Rate us
</button>
```

Respondents never see these values. They appear in reports and CSV. Full limits and setup: Embed fields.

**6. (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. Score widgets keep a neutral background; roundness and rating symbols follow the survey's Appearance settings.

{% 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.

![Public feedback after a survey is visible](https://cdn.sandbox.getmyra.app/docs/sharing/public-link-and-embed.glossy.png)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
