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

You need	Why it matters
An event definition	Fire Event can trigger only an event created in Developers → Events.
A button or image	Click actions, including Fire Event, are available on these elements.
Clear identifiers	Identifiers let you map widget content to event attributes reliably.
A test user	Event Insight shows events only after Netmera receives them.

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.

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.

Select the custom event that this widget interaction should trigger.

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.

Use widget identifiers when mapping component values to event attributes.

For full action setup, see Configure widget actions and validation.

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.

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 for standard widget shown and action events.