Fields by Sub-Category

Last updated 19 minutes ago

List of fields by sub-category. At the top of each sub-category section, you can find the list of panels where the sub-category appears.

Category table

Category	Sub-categories
BROADCAST INFORMATION	Without sub-category
CAMPAIGN INFO	Without sub-category
CAMPAIGN INFORMATION	Without sub-category
CART CREATION DATE	Without sub-category
CONTACT INFO	Without sub-category
CONTACT INFORMATION	Without sub-category Classification Contact finalization Dates and times General HSM Location information Operator Other services Specific by contact type
CONVERSION EVENTS	Without sub-category
CUSTOMER INFORMATION	Customer identification
DEVICE INFORMATION	Without sub-category
ECOMMERCE INFORMATION	Without sub-category
EVENTS	Without sub-category
GENERAL NPS INFORMATION	Without sub-category
LEAD INFORMATION	Without sub-category
LOCATION INFORMATION	Without sub-category
NO GROUP	Without sub-category
OUTBOUND CAMPAIGN CONTACT INFORMATION	Without sub-category
OUTBOUND CAMPAIGNS	Without sub-category
SEND INFO	Without sub-category
SESSION INFORMATION	Device information General
VISITORS INFORMATION	Without sub-category Segments Visitor identification

BROADCAST INFORMATION > > Without sub-category


Panels	Broadcast Contacts

Fields	Description
Access time	Time between the time of the contact request to access the broadcast and the time that the access is granted.
Bounce time	Amount of time that the visitor spends on the broadcast.
Broadcast Date	TBD
Broadcast ID	Identifier of the broadcast.
Broadcast Name	TBD
Like	One of the following: Yes: The contact liked the broadcast. No: The contact didn't like the broadcast.
Messages	Visitor comments to the streamed video. For example, `I both the product and I am extremelly satisfied witbh it. It's a must have.`
NPS Mood	Mood of the visitor that CoreMedia Experience Platform detected in the interaction.
NPS Score	Net Promoter Score (NPS) value, typically, is a value between 0 and 10, where 0 means that the customer is not happy and will not recommend the business to anyone, and 10 means that the customer is very happy and will recommend the business to everyone.
Rating	Rating that the customer gives to the streamed video. Values between `1` and `5`.
Visits	Number of visits during the broadcast.

CAMPAIGN INFO > > Without sub-category


Panels	Outbound Campaigns Email Outbound Campaigns Push Actions Outbound Campaigns Push Outbound Campaigns SMS Outbound Campaigns Voice

Fields	Description
Campaign	Name of the campaign.
Campaign creation date	Date of creation of the campaign.
Channel	Name of the channel associated with the contact. One of the following: Voice Video Chat Email SMS
From	Email that appears in the sent email. For example, `do-no-reply@amazing-campaign.com`.
Outbound campaign	For outbound campaigns, name of the outbound voice campaign where Engagement Cloud created the contact.
Outbound campaign context	Motivation of the campaign.
Reply to	Email address to where the receiver can reply.
Skill	Name of the skill of the operator or IVR that handled the contact.
Team	Team of the operator that handled the interaction.

CAMPAIGN INFORMATION > > Without sub-category


Panels	Broadcast Contacts Contacts Attempts Contacts Events Outbound Campaigns Actions

Fields	Description
Abandonment element	For onsite campaigns, name of the page element that contains the window from which the customer that visited the site abandoned the contact.
Action date	Date when the campaign action happened.
Action date (YYYYMMDD)	Date when the campaign action happened in format YYYY-MM-DD. For example, `2025-03-19`.
Action day (DD)	Day when the campaign action happened.
Action hour (HH)	Hour when the campaign action happened.
Action quarter	Quarter when the campaign action happened.
Action type	Type of action. One of the following: Email views. Email link click. Browser views. Unsubscribed.
Action week	Week when the campaign action happened.
Action weekday	Week day when the campaign action happened.
Action year (YYYY)	Year when the campaign action happened.
Action year and month (YYYYMM)	Year and month when the campaign action happened.
Active element	For onsite campaigns, name of the active element that contains the window from which the customer requested the contact.
Campaign tags	List of tags associated with the campaign.
External Campaign ID	If it exists, identifier of external campaign from which the customer requested the contact.
External campaign	If it exists, name of external campaign from which the customer requested the contact.
External campaign type	If it exists, type of external campaign from which the customer requested the contact. For example, a Facebook campaign.
External campaigns	List of the names of the external campaigns that handled the customer until the customer requested the contact.
External campaigns IDs	List of the identifiers of the external campaigns that handled the customer until the customer requested the contact.
Link	Visited link.
Onsite campaign	Name of the onsite campaign that contains the window from which the customer requested the contact.
Onsite campaign ID	Identifier of the onsite campaign that contains the window from which the customer requested the contact.
Outbound campaign	For outbound campaigns, name of the outbound voice campaign where Engagement Cloud created the contact.
Placeholder	Identifier of the placeholder that contains the window from which the customer requested the contact.
Widget	Name of the component of the onsite campaign from which the customer requested the contact.
Widget tags	List of tags associated with the component of the onsite campaign from which the customer requested the contact.

CART CREATION DATE > > Without sub-category


Panels	ECommerce

Fields	Description
Date (YYYYMMDD)	Date of creation of the cart with format YYYY-MM-DD. For example, `2025-03-11`.
Day (DD)	Day of the visit.
Hour (HH)	Hour of the visit.
Week	Number of the week of visit.
Weekday	Name of the weekday of the visit. One of the following: Sunday Monday Tuesday Wednesday Thursday Friday Saturday
Year (YYYY)	Year of the visit.
Year and month (YYYYMM)	Year and month of the campaign.

CONTACT INFO > > Without sub-category


Panels	Outbound Campaigns Email Outbound Campaigns Push Actions Outbound Campaigns Push Outbound Campaigns SMS Outbound Campaigns Voice

Fields	Description
Contact ID	Unique identifier of the contact.
Contact creation date	Date of creation of the contact.
Contact list	Name of the contact list that the campaign used.
Device operating system	operating system of the device that the customer used to access the website. For example, `Android`, `Windows`, or `IPhone Osx`.
Email	Email of the contact. For example, `regular.joe@mail.com`.
Email domain	Domain of the contact email. For example, `mail.com`.
External ID	Contact ID in other campaigns.
Name	Name of the contact.
Phone	Phone number of the contact.
Unsubscribe date	Date when the contact unsubscribed the campaign.

CONTACT INFORMATION > > Without sub-category


Panels	Broadcast Contacts Contacts Attempts Contacts ECommerce Events IVR Visitors

Fields	Description
Attempt number	Number of attempts to reach the customer in a contact.
Channel	Name of the channel associated with the contact. One of the following: Voice Video Chat Email SMS
Contact ID	Unique identifier of the contact.
Contact total duration (by intervals)	Total duration of the contact represented as an interval. For example, `16-30` minutes.
Customer review	Customer's evaluation of the operator who handled the contact.
DTMF Success Rate	The percentage of DTMF signals that the IVR successfully detects and processes. For example, `100%` or `72%`. A DTMF Success Rate of 72% means that in every 100 times that the customer pressed a number to navigate a menu, 72 were corrected pressed.
Duration (by intervals)	Contact duration in represented in an interval. For example, `31-45` minutes.
Flow ID	TBD
Flow Name	TBD
Form information	Information retrieved from the contact form.
Forwarded to	Phone number to where the IVR forwarded the interaction. If the IVR status is `Forwarded to sklill`, Forwarded to contains the id of the skill to which the interaction was forwarded.
Has IVR?	One of the following: Yes: An IVR handled the customer during some period of the interaction. No: The interaction with the customer was never routed to the IVR.
IVR duration (s)	Duration of the interaction, in seconds, while in the IVR. If the IVR forwards the interaction to an operator, this duration doesn't include time spent with the operator.
IVR end	Date and time when the IVR interaction ended. For example, `2025-01-09 14:42:06`.
IVR start	Date and time when the IVR interaction started. For example, `2025-01-09 14:41:36`.
IVR status	One of the following: None: Engagement Cloud did not classified the interaction. Disconnected: The customer disconnected the interaction while in the IVS. Finished: The customer or the IVR finished the interaction. Forwarded to skill: The IVR forwarded the interaction to an operator.
Last node	Name of the last node that handled the interaction. For example, node `18` or `forward_to_operator`.
Referrer	Source or link that referred the visitor.
Segment IDs	Identifiers of the segments associated to the visitor. For example, `A1B345C6DEFGH789I0JK`
Segments	Name of the segments associated to the visitor. For example, `January Promo`.
Simplified URL	Simplified URL of the page that the visitor viewed. For example, `https://documentation.coremedia.com/engagement-cloud/analytics`.
Simplified referrer	Simplified URL that contains the link to the page that the visitor viewed. For example, `https://documentation.coremedia.com/engagement-cloud/analytics`.
Skill	Name of the skill of the operator or IVR that handled the contact.
Total of processed nodes	Total number of nodes that handled the interaction. For example, `14`. If you click on a value on this column, the contact window opens.
Trigger point	Instant in the interaction that triggers the IVR. For example, `Beginning of the call` or `Operator transfer`.
URL address	URL address that the customer visited to reach the contact center.
Visitor record	Record of the visitor containing name and email.
Voice Recognition Accuracy	Rate of successful voice recognition. For example, in a voice command, an accuracy of `100%` means that the IVR could understand all words that the customer said. An accuracy of `50%` means that out of 4 words the IVR could only understand and process 2 words.
Voicemail detection result	One of the following: Human: The detected voice was human. Machine: The detected voice was from an answering machine or voicemail. Not Sure: CoreMedia Experience Platform could not classify the answer.
Wait time (until contact center) (by intervals)	Time that the con
Waiting time already in contact (by intervals)	Time that the customer waited while in queue. For example, while waiting for the operator after IVR.
Waiting time in queue (by intervals)	Time that the customer waited while in queue represented in intervals.
Waiting time until contacted (by intervals)	Time that the customer waited after requested to be contacted represented in intervals.

CONTACT INFORMATION > Classification


Panels	Contacts Attempts Contacts

Fields	Description
# Bundles	Packages that include multiple RGUs. Number of packages sold during the contact with the customer.
# RGUS	Revenue Generating Unit. Number of products or services sold during the contact with the customer.
Classification Date	Date when the contact was classified.
Has Sale?	One of the following: Yes: The contact ended with a sale. No: The contact ended without sales.
Sale value	Value of the sale. It can be expressed in monetary units like € or $ or in RGUs.

CONTACT INFORMATION > Contact finalization


Panels	Broadcast Contacts Contacts Attempts Contacts

Fields	Description
Classification status	Status of the classification of the contact after finalization. One of the following: Classified by Operator Not Classified Not Classified - Transferred Not Classified - Expired Time
Credits	Number of credits attributed to the operator that handled the contact.
Disconnection origin	For chat interactions, entity responsible for ending the communication. One of the following: Operator Customer Note that in older data you can find Visitor as a disconnection origin. This origin is being replaced by Customer.
External wrapup code	TBD
Hangup cause	Cause of hangup for chat interactions with the customer. One of the following: Visitor disconnection Ended by operator Visitor inactivity Ended by visitor Note that each client can add more hangup causes.
Hangup cause (contact center)	Cause of hangup for voice interactions with the contact center. One of the following: Completed transfer Failed transfer Canceled transfer Busy Note that each client can add more hangup causes.
Has conversion?	One of the following: Yes - If the contact ends with a conversion. No - If the contact doesn't end with a conversion. Note that the definition of conversion depends on the campaign purpose. For example, the customer bought a product or the customer filled in a survey giving information to the campaign.
Is it classified?	One of the following: Yes - Engagement Cloud automatically classified the contact or the operator manually classified the contact. No - Engagement Cloud failed to classify the contact or there is no classification available.
Wrapup code	Code that the client defined to wrapup the contact. For example, `Sale`.

CONTACT INFORMATION > Dates and times


Panels	Broadcast Contacts Contacts Attempts Contacts

Fields	Description
Contact date (YYYYMMDD)	Date when the contact started. For example, `2025-01-15`.
Contact duration (in operation)	One of the following: If the customer calls the contact, this represents the time when the operator or the IVR answers the call until the call ends. If the contact center calls a customer, this represents the time from when the customer answers the call until it ends. If the Contact Type = `Chat`, this represents the time when the customer receives the first message until the chat ends due to one of the following reasons: The operator ended the chat. The chat was inactive. Lack of persistence.
Contact total duration	The total duration of the contact from the time the interaction reaches the contact center until it finishes. For voice calls, it also includes time spend in the IVR.
Date and time of contact	Date and time when the contact started.
Date of contact request	Date when the customer requested the contact.
Date of initial scheduling	Date of the first scheduling to contact the customer.
Day of contact (DD)	Day when the contact started.
Hangup contact date	For voice interactions, date when the contact hung up and ended the interaction.
Hour of contact (HH)	Hour when the contact started.
Initial date of 1st attempt	For outbound contacts, date of the first attempt to contact the customer.
Initial date of success	For outbound contacts, date of the first attempt that the customer answered.
Wait time (until contact center)	Waiting time from the beginning of the contact until the customer reaches an operator.
Waiting time already in contact	Time that the customer waited while on hold or, while waiting for information from the operator, or while waiting to reach an operator after an IVR transfer.
Waiting time in queue	Waiting time while the contact is in queue.
Waiting time until contacted	Time since the costumer requested the contact until the first attempt to contact the customer happened.
Week of contact	Number of the week when the contact started
Weekday of contact	Number of the weekday when the contact started. One of the following: 1 for Monday 2 for Tuesday 3 for Wednesday 4 for Thursday 5 for Friday 6 for Saturday 7 for Sunday
Year and month of contact (YYYYMM)	Year and month when the contact started. For example, `January 2025`.
Year of contact (YYYY)	Year when the contact started. For example, `2025`.

CONTACT INFORMATION > General


Panels	Broadcast Contacts Contacts Attempts Contacts Leads

Fields	Description
Billing Status	If the contact resulted in a sale, shows the billing status of the customer. One of the following: Success: The customer already payed the product. Un-success: The customer had not payed for the product.
Caller ID	For inbound voice contacts, phone number of the calling customer.
Contact channel	Channel of the interaction with the customer. One of the following: Default Voice Video Chat Email SMS
Contact hangup origin	Who ended the interaction. One of the following: Operator Customer System
Contact initial skill	Skill of the first operator that handle the contact.
Contact language	Preferred language for inter with the customer. For example, `Portuguese`.
Contact request IP	IP from which the customer requested the contact.
Contact request domain	URL from where the visitor requested the conctact.
Contact status	One of the following: Success Un-success Note that the Status per contact type field contains details about each contact status.
Contact subtype	If Contact Type = `Voice`, one of the following: Click2Call: Contact created from a call that the customer requests using Click2Call. Outbound: Contact created from a call to a phone number of a customer in a contact list without the intervention of an operator. For example, to play a promotional recording. Callcenter Outbound: Contact created from a call to a phone number of a customer in a contact list that the CoreMedia Contact Center delivers to an operator, possibly, after playing a recording. For example, a call that the CoreMedia Contact Center delivers to an operator to allow the customer to buy a product after hearing the promotional recording. Inbound: Contact created from a call that the customer makes to an operator. Calltracker: Contact created from an inbound call with calltracker. API: An API endpoint created the contact. Workflow: A workflow function created the contact. Active Manual: Contact created from an outbound call that the operator made manually. Active Schedule: Contact created from an outbound call previously scheduled. If Contact Type = `Video Broadcast`, one of the following: Video broadcast: Outbound call that plays a video to the customer. Video2Call: Voice call with video. If Contact Type = `Chat`, one of the following: Live Chat: Contact created from a chat conversation with a live operator. Chatbot: Contact created from an interaction with a chatbot.
Contact type	One of the following: Voice: Contact where the customer talks with an operator through a voice call. The voice call can be inbound, outbound, or Click2Call. Video Broadcast: Voice calls that include video. Chat: Contacts where customers use messaging to communicate with the contact center. Forms: Voice, video, or chat contacts that the customer started using a form. External: Contacts where the operator talks with the customer outside the CoreMedia Contact Center. After finishing, the operator creates the contact manually in the CoreMedia Contact Center. Note that the Contact Subtype field contains details about each contact type.
CoreMedia CID	Contact unique identifier according to the contact type. For example, a voice contact can have CID = `154242` and a chat contact can also have CID = `154242`.
CoreMedia Main ID (Ticket ID)	Contact unique identifier.
Creation reason	Reason why the contact was created. For example, `Blind transfer` or `External campaign`.
Destination	Destination of the interaction. For example, `Click2Call`.
Direction	Direction of the interaction. One of the following: None Inbound Outbound
Operator ID	Unique identifier of the operator that handled the interaction with the customer.
Operator name	Name of the operator that handled the interaction with the customer.
Operator tags	Tags associated to the operator that handle the interaction.
Organization	Name of the company that provides the Internet service to the visitor. For example, `Vodafone`.
Origin contact ID	Identifier of the contact that cause the creation of this contact. For example, the visitor ends an interaction with an operator and the operator transfers the interaction to another department. In this case, the first operator ends the contact and a new contact is created.
Phone	Phone number of the contact.
Skill	Name of the skill of the operator or IVR that handled the contact.
Source	Source of the interaction. For example, `Phone`.
Status per contact type	One of the following: If Contact Type = `Success`, one of the following: Normal: Every contact from the customer that reaches an operator. Finished on IVR: Contacts where the customer is able to solve the problem or complete the intended task using just the IVR. For example, a call to the electric company to communicate monthly consumptions. Template sent: Contacts that end with a template sent to WhatsApp. If Contact Type = `Un-Success`, one of the following: Contact Center did not answer Customer did answer, but the Contact Center didn't answer Abandonment in queue Scheduled contact Customer did not answer Disconnected on IVR Contact Center didn't answer after IVR success Impossible to sent
Sub status	Contact sub status. For example, `Normal`.
Team	Team of the operator that handled the interaction.
Time on node	Time spent in the IVR node.
Voice contact subtype	For voice interactions, one of the following: Inbound Outbound API Calltracker Click2Call

CONTACT INFORMATION > HSM


Panels	Contacts

Fields	Description
Provider name (HSM)	TBD
Template description (HSM)	TBD
Template message (HSM)	TBD
Template name (HSM)	TBD

CONTACT INFORMATION > Location information


Panels	Broadcast Contacts Contacts Attempts Contacts Leads

Fields	Description
Country	Country of the customer. For example, `Portugal`.
Internet provider	Name of the Internet provider of the customer. For example, `Vodafone Portugal`.
Region	Name of the city of the customer. For example, `Lisbon`.

CONTACT INFORMATION > Operator


Panels	Contacts Attempts Contacts

Fields	Description
Operator device	Name of the device of the operator. For example, `Apple MacBook`.

CONTACT INFORMATION > Other services


Panels	Broadcast Contacts Contacts Attempts Contacts

Fields	Description
AI Classification	Automatic classification of the contact.
Contact Scope	TBD
Contact Summary	Summary of the contact.
Has Bidireccional Video?	One of the following: Yes: The contact used bidirectional video. No: The contact didn't use bidirectional video.
Has Video?	One of the following: Yes: The contact used video. No: The contact didn't use video.
Has cobrowse?	One of the following: Yes: The contact used cobrowsing. No: The contact didn't use cobrowsing.
Has recording?	One of the following: Yes: The interaction of the contact was recorded. No: The interaction of the contact was not recorded.
Has transcript?	One of the following: Yes: The interaction of the contact a transcript. No: The interaction of the contact doesn't have a transcription.
Have on-demand recording?	One of the following: Yes: The contact has on-demand recording associated. No: The contact doesn't have an on-demand recording associated.
Human verified	One of the following: Yes: The contact classification was manually verified. No: The contact classification was not verified manually.
Recording	Name of the recording.
Recording On-demand	Name of the recording.
Sentiment Analysis	Evaluation of the mood of the contact.
Transcript	Name of the transcript.

CONTACT INFORMATION > Specific by contact type


Panels	Broadcast Contacts Contacts Attempts Contacts

Fields	Description
Bot name	If the Contact Type = `Chat`, name of the chatbot that handled the interaction.
Callback canceled	One of the following: Yes No
Chatbot session id	TBD
Contact Center number	Number of the contact center that the customer used. For example, `351211212121`.
Has triggered a schedule?	One of the following: No: The contact did not triggered a call schedule. Scheduled: The contact triggered a the scheduled of a call to the customer.
Inbound number	Number that the customer used to call the contact center. For example, `351221234567`.
Is short call?	One of the following: No Yes
Last interaction date	Date of the last interaction of the customer with the contact center.
Last interaction sender	If the Contact Type = `Email`, the sender of the last email.
Last node	Name of the last node that handled the interaction. For example, node `18` or `forward_to_operator`.
Nodes used	Number of the IVR nodes that handled the interaction before it was ended or delivered to an operator.
Number of attempts	If Contact Subtype is `API` or `Click2Call`, contains the number of call attempts that the contact center made until the customer answers or until it reaches the maximum number of attempts.
Number of interactions	Number of interactions associated with the contact.
Operator identification method	One of the following: API (A) DTMF (D) Console (T) System (S) Transfer (F)
Virtual inbound number	Virtual phone number that the customer used to call the contact center. Typically, mobile phone numbers.
Voice actions sequence	Name of the

CONVERSION EVENTS > > Without sub-category


Panels	Events

Fields	Description
Conversion Type	Type of the conversion. One of the following: assisted: A conversion has type `assisted` if the visitor needed the help of an operator to end the conversion. For example, the customer had to talk to an operator to purchase a mobile phone or to submit a form. direct: A conversion has type `direct` if the customer was able to finalize the conversion without further help from an operator.
Conversion value	If applicable, value of the conversion. For example, `730€`.
Days until conversion	Number of days necessary for the customer to do the conversion. For example, `29`.
Sessions until conversion	Number of sessions that the customer opened before converting. For example, `10`.

CUSTOMER INFORMATION > Customer identification


Panels	Contacts Attempts Contacts Visitors

Fields	Description
Customer ID	TBD
Email	Email of the contact. For example, `regular.joe@mail.com`.

DEVICE INFORMATION > > Without sub-category


Panels	ECommerce Events Outbound Campaigns Actions Visitors

Fields	Description
Browser	Browser that the using is using. For example, `Chrome Android`.
Browser resolution	Graphical resolution of the browser in pixels. For example, `1536x864`.
Device family	Brand family of the device that the customer used to access the website. For example, `Galaxy A12`, `IPhone`, or `Macintosh`.
Device model	Model of the device that the customer used to access the website. For example, `SM-A125f`, `Iphone 11`, or `MacBook Pro`
Device operating system	operating system of the device that the customer used to access the website. For example, `Android`, `Windows`, or `IPhone Osx`.
Device type	Type of device. One of the following: Smartphone Tablet Desktop Console
Device vendor	Vendor of the device that the customer used to access the website. For example, `Samsung`, `Apple`, or `HP`.
Email client	Email client that the visitor used.
Mobile device	One of te following: No - The visitor didn't use a mobile device to make the visit. Yes - The visitor used a mobile device to make the visit.

ECOMMERCE INFORMATION > > Without sub-category


Panels	ECommerce

Fields	Description
App Context	Context in the application where the activity occurred.
Cart value	Total value of the cart. For example, `€787`.
Checkout	One of the following: Yes: The customer made checkout of the cart. No: The customer didn't make checkout of the cart yet.
Creation date	For Leads, creation date of the lead. For Ecommerce, creation date of the cart.
Current step number	Status of the cart. Number of the step in the checkout workflow that the cart is in. For example, the user is adding the shipping address which corresponds to step `3`.
Items number	Number of items in the cart. For example, `7`.
Last update	Date and time of the last update of the cart in the format YYYY-MM-DD hh:mm:ss. For example, `2025-03-11 17:51:33`.
Max step number	Size of the checkout workflow. Maximum number of steps in the checkout workflow. For exaample, `4`.
Shipping cost	Cost of the associated shipping. For example, `€ 4.99`.
Shopping cart ID	Unique identifier of the shopping cart. For example, `123456789`.
Status	Status.

EVENTS > > Without sub-category


Panels	Events

Fields	Description
Browser resolution	Graphical resolution of the browser in pixels. For example, `1536x864`.
Domain	Accessed domain.
Event date	Date of the event.
Event name	Name of the event.
Event type	Type of event in the page. One of the following: Active Elements Abandonment Elements
Internet provider	Name of the Internet provider of the customer. For example, `Vodafone Portugal`.
Organization	Name of the company that provides the Internet service to the visitor. For example, `Vodafone`.
Referrer domain	Domain of the page that contains the link that the visitor used to open the page. For example, `https://www.google.com`.
Search terms	Sequence of terms that the visitor used in the last search. For example, `kitchen knive`.

GENERAL NPS INFORMATION > > Without sub-category


Panels	Visitors

Fields	Description
Mood	Mood detected and recorded for the visitor.
NPS value	Net Promoter Score (NPS) value, typically, is a value between 0 and 10, where 0 means that the customer is not happy and will not recommend the business to anyone, and 10 means that the customer is very happy and will recommend the business to everyone.

LEAD INFORMATION > > Without sub-category


Panels	Contacts Attempts Contacts Events Leads

Fields	Description
Channel	Name of the channel associated with the contact. One of the following: Voice Video Chat Email SMS
Closing date	Closing date of the lead.
Creation date	For Leads, creation date of the lead. For Ecommerce, creation date of the cart.
Customer ID	TBD
Duration	For IVRs, duration of the interaction in the IVR. If the IVR forwards the interaction to an operator, this duration doesn't include time spent with the operator. For Leads, sum of the durations of all the contacts associated with the lead.
Lead ID	TBD
Lead number	Unique identifier of the lead.
Lead status	Status of the lead.
Lead type	Type of the lead.
Provider	Provider of the SMS service. For example, `Vodafone`.
RGUS	Number of RGUS that were realized in the lead.
Sale	One of the following: Yes: If the lead had a sale. No: If the lead did not had a sale.
Sale Date	If the lead resulted in a sale, contains the date when the sale was completed.
Time to conversion	TBD
Total associated contacts	Total number of contacts associated with the lead.

LOCATION INFORMATION > > Without sub-category


Panels	ECommerce Events Outbound Campaigns Actions Visitors

Fields	Description
City	City from where the visitor used the site.
Country	Country of the customer. For example, `Portugal`.
Region	Name of the city of the customer. For example, `Lisbon`.

NO GROUP > > Without sub-category


Panels	Events

Fields	Description
Visitors by page	Number of visitors by requested page.

OUTBOUND CAMPAIGN CONTACT INFORMATION > > Without sub-category


Panels	Outbound Campaigns Actions

Fields	Description
Contact ID	Unique identifier of the contact.
Contact creation date	Date of creation of the contact.
Contact list	Name of the contact list that the campaign used.
Email	Email of the contact. For example, `regular.joe@mail.com`.
Email domain	Domain of the contact email. For example, `mail.com`.
External ID	Contact ID in other campaigns.
Name	Name of the contact.
Organization	Name of the company that provides the Internet service to the visitor. For example, `Vodafone`.
Phone	Phone number of the contact.

OUTBOUND CAMPAIGNS > > Without sub-category


Panels	Outbound Campaigns Actions

Fields	Description
Bcc	Email blind copy.
Campaign	Name of the campaign.
Campaign creation date	Date of creation of the campaign.
Cc	Email copy.
Channel	Name of the channel associated with the contact. One of the following: Voice Video Chat Email SMS
External campaign	If it exists, name of external campaign from which the customer requested the contact.
From	Email that appears in the sent email. For example, `do-no-reply@amazing-campaign.com`.
Offsite campaign type	Type of the offsite campaign responsible for the action: Email Outbound SMS Outbound Voice Outbound
Reply to	Email address to where the receiver can reply.
Skill	Name of the skill of the operator or IVR that handled the contact.

SEND INFO > > Without sub-category


Panels	Outbound Campaigns Actions Outbound Campaigns Email Outbound Campaigns Push Actions Outbound Campaigns Push Outbound Campaigns SMS Outbound Campaigns Voice

Fields	Description
Call context	Context of the call.
Call skill	Skill of the operator that handled the call.
Contact creation date	Date of creation of the contact.
Contact datetime	Date and time when the email was sent.
Credits	Number of credits attributed to the operator that handled the contact.
Date of contact creation	Date of creation of the contact.
Date the contact was added to the campaign	Date the contact was added to the campaign.
Error message	If the SMS was not delivered, contains the message explaining the error.
Last contact date	Date of the most recent recorded contact of the visitor.
Last status update date	Date in which the campaign updated the status of the contact.
Operator	Operator tha handled the contact.
Operator ID	Unique identifier of the operator that handled the interaction with the customer.
Operator tags	Tags associated to the operator that handle the interaction.
Provider	Provider of the SMS service. For example, `Vodafone`.
Sent date	Date in which the SMS was sent.
Sent date (YYYYMMDD)	Email sending date.
Sent day (DD)	Email sending day.
Sent hour (HH)	Email sending hour.
Sent month (MM)	Email sending month.
Sent quarter	Email sending quarter.
Sent week	Email sending week.
Sent weekday	Email sending weekday.
Sent year (YYYY)	Email sending year.
Status	Status.
View Date	Date when the contact viewed the email or SMS.

SESSION INFORMATION > Device information


Panels	Broadcast Contacts Contacts Attempts Contacts Leads

Fields	Description
Browser	Browser that the using is using. For example, `Chrome Android`.
Browser resolution	Graphical resolution of the browser in pixels. For example, `1536x864`.
Device family	Brand family of the device that the customer used to access the website. For example, `Galaxy A12`, `IPhone`, or `Macintosh`.
Device model	Model of the device that the customer used to access the website. For example, `SM-A125f`, `Iphone 11`, or `MacBook Pro`
Device operating system	operating system of the device that the customer used to access the website. For example, `Android`, `Windows`, or `IPhone Osx`.
Device type	Type of device. One of the following: Smartphone Tablet Desktop Console
Device vendor	Vendor of the device that the customer used to access the website. For example, `Samsung`, `Apple`, or `HP`.

SESSION INFORMATION > General


Panels	Broadcast Contacts Contacts Attempts Contacts

Fields	Description
FID (external ID)	External identifier of the visitor.
Referrer	Source or link that referred the visitor.
Referrer domain	Domain of the page that contains the link that the visitor used to open the page. For example, `https://www.google.com`.
Search terms	Sequence of terms that the visitor used in the last search. For example, `kitchen knive`.
Session IP	IP of the session.
Simplified URL	Simplified URL of the page that the visitor viewed. For example, `https://documentation.coremedia.com/engagement-cloud/analytics`.
Simplified referrer	Simplified URL that contains the link to the page that the visitor viewed. For example, `https://documentation.coremedia.com/engagement-cloud/analytics`.
URL address	URL address that the customer visited to reach the contact center.

VISITORS INFORMATION > > Without sub-category


Panels	ECommerce Events Visitors

Fields	Description
Cookie	ID of the cookie of the visitor.
First contact date	Date of the first recorded contact of the visitor.
First visit date	Date of the first recorded access of the visitor.
ID	Unique identifier of the visitor that CoreMedia Digital Experience Platform attributes to the visitor using visitor information like IP address and browser type, among others.
Identification type	Type of visitor identification. For example, `2031253224`. One of the following: FId: The Digital Experience Platform generated the visitor identifier. Cookie ID: Digital Experience Platform read the visitor ID from a Cookies.
Internet provider	Name of the Internet provider of the customer. For example, `Vodafone Portugal`.
Last contact date	Date of the most recent recorded contact of the visitor.
Last visit date	Date of the last access of the visitor.
Mobile device	One of te following: No - The visitor didn't use a mobile device to make the visit. Yes - The visitor used a mobile device to make the visit.
Organization	Name of the company that provides the Internet service to the visitor. For example, `Vodafone`.
Phone	Phone number of the contact.
Referrer	Source or link that referred the visitor.
Remote IP	IP address of the visitor. For example, `192.0.2.24`.
Search expression	Last expression that the visitor wrote in the search of the website. For example, `creating a campaign`.
Segment IDs	Identifiers of the segments associated to the visitor. For example, `A1B345C6DEFGH789I0JK`
Segments	Name of the segments associated to the visitor. For example, `January Promo`.
Total contacts	Total number of contacts associated with the visitor. For example, `4 contacts`.
Total visits	Total number of times a visitor accesses the site during a specified period.
Visitor id	Unique identifier of the visitor.

VISITORS INFORMATION > Segments


Panels	Broadcast Contacts Contacts Attempts Contacts

Fields	Description
Segment IDs	Identifiers of the segments associated to the visitor. For example, `A1B345C6DEFGH789I0JK`
Segments	Name of the segments associated to the visitor. For example, `January Promo`.

VISITORS INFORMATION > Visitor identification


Panels	Broadcast Contacts Contacts Attempts Contacts

Fields	Description
Cookie	ID of the cookie of the visitor.
CoreMedia VID	Visitor unique identifier.
External ID	Contact ID in other campaigns.
Identification type	Type of visitor identification. For example, `2031253224`. One of the following: FId: The Digital Experience Platform generated the visitor identifier. Cookie ID: Digital Experience Platform read the visitor ID from a Cookies.

Is this page useful?