MCR Meta Data

This help page is for Desktop Studio. This information is also available for CXone Studio.

MCR Meta Data action icon.

Allows a script to pass metadata into CXone Recording business data fields during a call. This lets you enrich your interaction metadata, make your recordings more searchable, create more nuanced quality plans, and so forth.

This action takes metadata as key/value pairs from a dynamic data object and passes it to CXone Recording. Use a SNIPPET action to create the object to contain the metadata you want to pass, demonstrated with the example script on this page. Be sure to use the same names as the business data fields you created in CXone.

You can also use the business data API to enrich recording metadata. The API and this action work alongside each other. The key difference is that you cannot push data with the action outside of an active call.



  • This action must be placed in the script so that it fires during a live call. It won't work if it fires after a call is over.

  • If you want to push data about a call that ended, you must use the business data APIs.

Supported Script Types

The icon for the Phone script type - an old-style phone handset with curved lines indicating sound coming out of it.

The icon for the Digital script type - a computer monitor with a smartphone next to it.

Phone Digital

Input Properties

These properties define data that the action uses when executing.




Enter a short phrase that uniquely identifies this action in the script. The caption appears on the script canvas under the action icon. The default is the action name.

Key Value Pairs Determines from which DynamicData object metadata will be taken to pass along to CXone Recording. Metadata must be defined as key:value pairs in a DynamicData object within a Snippet action.

Result Branch Conditions

Result branch conditions allow you to create branches in your script to handle different outcomes when an action executes.




Path taken unless the script meets a condition that requires it to take one of the other branches. It is also taken if the action's other branches are not defined.

Script Example

This is an example to show how this action can be used in scripts. It is not intended to be a complete script. Additional scripting may be required.

n this example script, after the call is answered, the Snippet action creates a DynamicData object with several custom fields and passes the dynamic object to MCR Meta Data. Then, when the call disconnects, MCR Meta Data passes these custom fields to CXone Recording to be included as metadata with the recording.

Would you like to download this script?