> 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/measure-performance/track-custom-widget-events.md).

# Track custom widget events

Use custom events to measure widget interactions that standard widget reporting cannot describe. For example, track a feedback choice, a product interest signal, or a multi-step campaign outcome.

Create the event before assigning **Fire Event** to a widget button or image.

### Before you start

<table><thead><tr><th width="185.46484375">You need</th><th>Why it matters</th></tr></thead><tbody><tr><td>An event definition</td><td><strong>Fire Event</strong> can trigger only an event created in <strong>Developers → Events</strong>.</td></tr><tr><td>A button or image</td><td>Click actions, including <strong>Fire Event</strong>, are available on these elements.</td></tr><tr><td>Clear identifiers</td><td>Identifiers let you map widget content to event attributes reliably.</td></tr><tr><td>A test user</td><td>Event Insight shows events only after Netmera receives them.</td></tr></tbody></table>

### Create the event

Open **Developers → Events** and select **Create New Event**. Define the event before configuring the widget action.

Provide a clear event name, user-facing label, and description. Names should describe the interaction, such as `FeedbackSubmitted` or `OfferAccepted`.

Add attributes when the event needs context. Each attribute has a name, label, data type, and optional mandatory, array, or private-information settings. Use attributes for values such as a selected rating, product ID, campaign name, or response text.

Save the event definition before assigning it to the widget. For complete event-definition guidance, see [Events](/netmera-user-guide/panel-settings/settings/app-configuration/events.md).

### Assign Fire Event

Select the button or image that should record the interaction. Then open the ⚡ **lightning** icon and choose **Fire Event**.

1. Select the existing event from the event list.
2. Add any required attribute mappings.
3. Save the widget after reviewing the action.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FmPIsmo3WgNDQI0GmyEfe%2FScreenshot%202024-12-19%20at%2017.35.54.png?alt=media&amp;token=722b1e3d-5215-45d6-b76c-1cabc392869b" alt="Fire Event action settings" width="375"><figcaption><p>Select the custom event that this widget interaction should trigger.</p></figcaption></figure>

### Map widget values to event attributes

Map a value only when the event includes an attribute that needs widget content. Assign a clear identifier to the source element first. Then select **Content** in the mapping options and choose the matching component.

For example, a feedback button can trigger `FeedbackSubmitted` and map the user’s selected rating into a `rating` attribute. Check every required attribute before saving. An incomplete mapping can prevent the event from carrying the expected context.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FfCN8P0hyMQKJE2zaZD18%2FScreenshot%202024-12-19%20at%2014.04.33.png?alt=media&amp;token=a6fc6f95-c1e7-4e70-9398-eaa3441c7e3c" alt="Fire Event mapping options" width="375"><figcaption><p>Use widget identifiers when mapping component values to event attributes.</p></figcaption></figure>

For full action setup, see [Configure widget actions and validation](/netmera-user-guide/omnichannel-engagement/widgets/build-a-widget/configure-widget-actions-and-validation.md).

### Test the event

Preview the widget and trigger the action with a test user. Confirm the click follows the expected path and sends each required attribute.

Events appear in reporting only after the configured interaction occurs. If the event is missing, confirm the event definition, selected action, attribute mappings, and test interaction.

### Analyze custom event results

Open **Analytics → Event Insight** after the event is received.

1. Select a time period and target audience.
2. Search for the custom event.
3. Add event properties to narrow the matching records.
4. Choose a view such as **Total Event Count** or **Unique User Count**.
5. Add dimensions, such as time, platform, or a custom event attribute.

Use **Total Event Count** when repeated interactions matter. Use **Unique User Count** when you need the number of people who interacted. Custom attributes become available as dimensions when they are defined for the selected event.

For advanced filters, breakdowns, and exports, see [Event Insight](/netmera-user-guide/reports-and-analytics/analytics/event-insight.md).

### Choose the right event type

| Use standard widget events for                  | Use custom widget events for                                                       |
| ----------------------------------------------- | ---------------------------------------------------------------------------------- |
| Widget impressions and eligible linked actions. | Specific business interactions, multiple actions, and attribute-rich reporting.    |
| Delivery and basic engagement reporting.        | Feedback selections, offer choices, form outcomes, and campaign-specific behavior. |

See [Analyze widget performance](/netmera-user-guide/omnichannel-engagement/widgets/measure-performance/analyze-widget-performance.md) for standard widget shown and action events.


---

# 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://user.netmera.com/netmera-user-guide/omnichannel-engagement/widgets/measure-performance/track-custom-widget-events.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.