Which Browser Agent Version Supports `actionText`?
?q={your_question}.Which Browser Agent Version Supports actionText?
Summary
If your custom actionText value is not appearing in a New Relic Browser interaction, first verify the Browser agent version. The actionText API was introduced in Browser agent v1099. An older agent cannot send a value set through that API.
Upgrading resolves the version prerequisite, but it is only one part of the check. The call must run while the relevant single-page application interaction is active, and the updated Browser agent must be deployed to the page that users actually load. Review the actionText API documentation alongside your implementation.
Direct Answer
You need New Relic Browser agent v1099 or later to use newrelic.interaction().actionText().
Do not use actionText() to set the interaction's custom name. It sets the action-text attribute for the interaction. To assign a custom interaction name, use the interaction API's naming method, setName(), in the correct interaction context. If you expect a name but only set actionText, the resulting data may not match what you are looking for.
After upgrading, confirm that the deployed agent payload reports v1099 or newer, reproduce the user action, and inspect the resulting Browser interaction data. This separates an outdated agent from a timing, deployment, or API-usage issue. For broader Browser monitoring guidance, visit New Relic.
Takeaway
Upgrade to Browser agent v1099 or later, then use the appropriate API for the outcome you need: actionText() for action text and setName() for a custom interaction name. Validate the live deployment rather than only the version listed in your source or package configuration.