> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/widgets.md).

# Widgets

Build no-code widgets for apps and websites, such as pop-ups, announcements, coupon reveals and spin-to-win games, then publish them and measure results.

{% columns %}
{% column width="58.333333333333336%" %}
Widgets are no-code UI components you add to apps and websites to engage users through announcements, promotions, and gamified flows.

* Deliver tailored content.
* Engage with coupon reveals, pop-ups, and banners.
* Launch quickly with precise targeting.
* Reflect your brand with dynamic content.
* Measure user engagement in real-time.

Widgets turn every interaction into an opportunity to convert and retain users.
{% endcolumn %}

{% column width="41.666666666666664%" %}

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FXihq6icIm30UdxHzZmBW%2Fimage.png?alt=media&amp;token=f405fccc-a53a-4caf-95d5-607f4d3c62df" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

### Choose your task

* [Build a widget](/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget.md) — create, configure, design, and add behavior.
* [Publish and target](/netmera-user-guide/omnichannel-engagement/widgets/target-and-publish.md) — set channel-specific rules, audiences, and launch settings.
* [Measure performance](/netmera-user-guide/omnichannel-engagement/widgets/measure-performance.md) — measure impressions, interactions, and outcomes.
* [Spin to Win campaigns](/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/spin-to-win-campaigns.md) — build goal-specific campaigns with rewards and coupon codes.

### Channel guides

<table data-view="cards"><thead><tr><th>Channel or pattern</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td>Mobile widgets (inside your mobile app)</td><td><a href="/netmera-user-guide/omnichannel-engagement/widgets/target-and-publish/publish-a-mobile-widget.md">Publish a mobile widget</a></td></tr><tr><td>Web widgets (on your website)</td><td><a href="/netmera-user-guide/omnichannel-engagement/widgets/target-and-publish/publish-a-web-widget.md">Publish a web widget</a></td></tr><tr><td>Spin to Win campaigns (mobile and web)</td><td><a href="/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/spin-to-win-campaigns.md">Spin to Win campaigns</a></td></tr></tbody></table>

### How-to videos

{% embed url="<https://youtu.be/7XIZGV0rj1I?si=8Mzh1IBLQBoseYrz>" %}


---

# 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://user.netmera.com/netmera-user-guide/omnichannel-engagement/widgets.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.