APM for Commerce Action Performance

Note:

This topic applies to SuiteCommerce and the 2020.1.1 release of SuiteCommerce Advanced and later.

Monitor specific actions that users perform on your websites or devices. Application Performance Management (APM) for Commerce features let you view high-level data and the detailed history of each action on various dashboards. For more information, see Action Performance Dashboards.

To analyze the performance of actions, the dashboards available with APM for Commerce features capture a defined list of sensors. They also capture data related to custom scripts and workflows. To learn more, see the following help topics:

Action Sensors
Customization

To start monitoring actions, see the following help topics:

Action Performance Dashboards

The following table describes the dashboards that display action performance data.

APM for Commerce Feature	Dashboards	Description	Navigation
SuiteCommerce APM (SC APM)	SuiteCommerce Action Diagnostics	View information about actions that users performed on the website and domain that you want to investigate. Click a specific point on a timeline to view the history of an action. For more information, see the following help topics: APM Action Diagnostics APM Action History	Choose from the following: On SuiteCommerce Performance Dashboard, click an action tile on the Actions portlet. Go to Customization > SuiteCommerce Performance > SuiteCommerce Action Diagnostics.
SuiteCommerce Action History Detail	View detailed timing and performance data about a specific time when an action was performed. For more information, see APM Action History Detail.	On SuiteCommerce Action Diagnostics, click a point in the timeline to open the Action History table. Locate the performance log, then click the corresponding view detail icon.
SuiteCommerce InStore APM (SCIS APM)	SuiteCommerce InStore Performance Diagnostics	View actions performed by sales associates using SCIS as a point-of-sale solution. Click a specific point on a timeline to view the history of an action. For more information, see the following help topics: APM Action Diagnostics APM Action History	Go to Customization > SCIS Performance > SCIS Performance Diagnostics.
	SuiteCommerce InStore Action History Detail	View detailed timing and performance data about a specific time when an action was performed. For more information, see APM Action History Detail.	On SuiteCommerce InStore Performance Diagnostics, click a point in the timeline to open the Action History table. Locate the performance log, then click the corresponding view detail icon.

APM for Commerce Feature

Dashboards

Description

Navigation

SuiteCommerce APM (SC APM)

SuiteCommerce Action Diagnostics

View information about actions that users performed on the website and domain that you want to investigate. Click a specific point on a timeline to view the history of an action.

For more information, see the following help topics:

Choose from the following:

On SuiteCommerce Performance Dashboard, click an action tile on the Actions portlet.
Go to Customization > SuiteCommerce Performance > SuiteCommerce Action Diagnostics.

SuiteCommerce Action History Detail

View detailed timing and performance data about a specific time when an action was performed.

For more information, see APM Action History Detail.

On SuiteCommerce Action Diagnostics, click a point in the timeline to open the Action History table. Locate the performance log, then click the corresponding view detail icon.

SuiteCommerce InStore APM (SCIS APM)

SuiteCommerce InStore Performance Diagnostics

View actions performed by sales associates using SCIS as a point-of-sale solution. Click a specific point on a timeline to view the history of an action.

For more information, see the following help topics:

Go to Customization > SCIS Performance > SCIS Performance Diagnostics.

SuiteCommerce InStore Action History Detail

View detailed timing and performance data about a specific time when an action was performed.

For more information, see APM Action History Detail.

On SuiteCommerce InStore Performance Diagnostics, click a point in the timeline to open the Action History table. Locate the performance log, then click the corresponding view detail icon.

To view all the other dashboards available with APM for Commerce features, see APM for Commerce Dashboards.

Action Sensors

APM for Commerce features measure performance data for certain actions that occur during daily operations. Each action is displayed on a tile on dashboard pages.

To view the specific actions available for each APM for Commerce feature, see the following help topics:

SuiteCommerce APM Action Sensors
SuiteCommerce InStore APM Action Sensors

SuiteCommerce APM Action Sensors

SuiteCommerce APM captures performance statistics for the following actions:

Action	Description
Customer Registration	Measures the time it takes to register a customer on the website. The action starts when the user clicks Customer Registration. It ends when the related HTTP response successfully completes.
Save Address	Measures the time it takes to save an address during the checkout process and when editing or creating a new address in the My Account area.
Add to Cart	Measures the time it takes to add an item to the cart in the following pages or instances: Product Detail Product List Quick View Quick Add
Remove From Cart	Measures the time it takes to remove an item from the cart in the Cart page.
Place Order	Measures the time it takes to attempt to place an order from the website. The action starts when the user clicks Place Order. It ends when the related HTTP response completes, which is when the status field indicates if the order was placed or not.
Save Credit Card	Measures the time it takes to save a credit card into the system during the following processes: Creating a new credit card on the Checkout page Adding or editing the card on the My Account page
Request a Quote	Measures the time it takes to place a quote from the website. The action starts when the user clicks Submit Quote Request. It ends when the related HTTP response successfully completes.

Action

Description

Customer Registration

Measures the time it takes to register a customer on the website. The action starts when the user clicks Customer Registration. It ends when the related HTTP response successfully completes.

Save Address

Measures the time it takes to save an address during the checkout process and when editing or creating a new address in the My Account area.

Add to Cart

Measures the time it takes to add an item to the cart in the following pages or instances:

Product Detail
Product List
Quick View
Quick Add

Remove From Cart

Measures the time it takes to remove an item from the cart in the Cart page.

Place Order

Measures the time it takes to attempt to place an order from the website. The action starts when the user clicks Place Order. It ends when the related HTTP response completes, which is when the status field indicates if the order was placed or not.

Save Credit Card

Measures the time it takes to save a credit card into the system during the following processes:

Creating a new credit card on the Checkout page
Adding or editing the card on the My Account page

Request a Quote

Measures the time it takes to place a quote from the website. The action starts when the user clicks Submit Quote Request. It ends when the related HTTP response successfully completes.

SuiteCommerce InStore APM Action Sensors

SuiteCommerce InStore APM captures performance statistics for the following actions:

Category	Action	Description
Customers and Items	Creating a customer with an empty cart	Refers to a customer who has no record in SCIS and has an empty cart. The action starts when a sales associate creates a new customer, taps Create and Add, then adds the customer to a transaction. It ends when the associate can add items.
Creating a customer with items in the cart	Refers to a customer who has no record in SCIS and has items in the cart. The action starts when a sales associate creates a new customer, taps Create and Add, then adds the customer to a transaction. It ends when the associate can add items.
Adding an existing customer to an empty cart	Refers to a customer who has a record in SCIS and has an empty cart. The action starts when a sales associate selects then adds a customer to a transaction. It ends when the associate can add items.
Adding an existing customer to a cart with items	Refers to a customer who has a record in SCIS and has items in the cart. The action starts when a sales associate selects then adds a customer to a transaction. It ends when the associate can add items. Note: When a new customer is created or an existing customer is added to a sales transaction in progress, the application recreates the transaction.
Apply line-item discount, cart ready	Measures the time used to add a discount to an item in the cart. The action starts when a sales associate applies the discount from the discount form. It ends when the associate can resume interacting with the cart.
Apply transaction discount, cart ready	Measures the time used to apply a discount at the transaction level. The action starts when a sales associate applies the discount from the discount form. It ends when the associate can resume interacting with the cart.
Display add customer form	Measures the time used to prepare and display a form for adding a new customer. The action starts when a sales associate taps an option to add a new customer. It ends when the customer form appears.
Display item search results	Measures the time used to display search results. The action starts when the user enters a keyword in the global search bar and ends when the search results appear.
Adding an item to the cart	Measures the time used to add an item to the cart.
Open Product Detail Page (PDP)	Measures the time used to prepare the Product Details page. The action starts after the user clicks the item link. It ends when the user can add the item to the cart or select its options.
Login and Authentication	Authenticate login credentials	Measures the time used to authenticate login credentials. The action starts when the user clicks Log In. It ends when the user selects a role or location or proceeds directly to the open cart.
Payments, Payment Devices, and Refunds	End-to-end payment device processing	Measures the action beginning immediately after initialization and includes the time spent by the customer interacting with the payment device until the payment is processed.
Paying with credit memo	Measures the time to complete payment tendered using a credit memo. The action starts when the user applies payment. It ends when the receipt appears. This action excludes the time, if needed, to manually enter credit memo information. For split payments, it ends when the user is ready to apply the next payment.
Paying with gift card	Measures the time to complete payment tendered using a gift card. The action starts when the user applies payment. It ends when the receipt appears. This action excludes the time spent manually entering gift card information. For split payments, it ends when the user is ready to apply the next payment.
Paying with manual or custom payment methods	Measures the time used to process payments made with cash, with a check, or by entering credit card information directly in SCIS without a payment device. The action starts when the user applies the payment and ends when the receipt appears. Custom payment methods that are part of your SCIS implementation are included in this action.
Priming the payment device	Measures the time spent initializing the PIN pad or other payment device. The action starts when the user enters the payment amount in SCIS. It ends when the device is ready to receive the customer’s credit, debit, or other payment source.
Priming the payment device for refund	Measures the time spent initializing payment device to accept refund information. The action starts when the user applies refund payment. It ends with a prompt that the device is ready to process the refund.
Refunding automatically to original card	Measures the time required to automatically refund payment to the original card used for purchase. The action starts when the payment device is primed to begin refund. It ends when the refund is applied to the card and the receipt appears.
Refunding to specific card	Measures the time required to refund a specific card after payment device is primed. The action starts when the payment device is primed to begin refund. It ends when the refund is applied to the card and the receipt appears. This measurement is different from refunds automatically applied to the original purchase card.
Receipts	Display receipt after NetSuite payment confirmation	Starts when payment confirmation is received from NetSuite and ends when the receipt appears.
Display email receipt status	Shows if the email message sent succeeded or failed. The action starts when the user clicks Send and ends when the success or fail message displays.
Display print receipt status	Shows if printing succeeded or failed. The action starts when the user clicks Print and ends when the print job status is received. If the auto-print feature is enabled, the action starts when the print request is sent to the printer and ends when the print job status is received.
Returns	Submit validated return, cart ready	Measures the time to prepare the cart after submitting a validated return. The action starts when the user clicks Return and ends when the user can interact with the cart again.
Unvalidated return, cart ready after selecting line	Measures the time to prepare the cart after selecting a line for unvalidated return. The action starts when the user clicks Return for the item and ends when the user can interact with the cart again.
Transaction Retrieval	Begin return from transaction details	Measures the time spent preparing a return from transaction details. The action starts when a sales associate initiates return from transaction details. It ends when the return form opens and the associate can begin selecting return options. The associate can start the return by a receipt scan, transaction history list, or customer timeline.
Retrieve transaction from scan	Measures the time spent retrieving transaction information through a NetSuite search initiated by SCIS. The action starts when a sales associate scans the transaction code on receipt. It ends when SCIS receives the information from NetSuite.
Display retrieved transaction	Measures the time used to display scanned transaction information retrieved from NetSuite. The action starts when information is made available to SCIS. It ends when SCIS displays the information to the sales associate.
Display store transaction history	Measures the time used to display a transaction from the store history option. The action starts when a sales associate taps option to display history and ends when the transaction list displays.

Category

Action

Description

Customers and Items

Creating a customer with an empty cart

Refers to a customer who has no record in SCIS and has an empty cart. The action starts when a sales associate creates a new customer, taps Create and Add, then adds the customer to a transaction. It ends when the associate can add items.

Creating a customer with items in the cart

Refers to a customer who has no record in SCIS and has items in the cart. The action starts when a sales associate creates a new customer, taps Create and Add, then adds the customer to a transaction. It ends when the associate can add items.

Adding an existing customer to an empty cart

Refers to a customer who has a record in SCIS and has an empty cart. The action starts when a sales associate selects then adds a customer to a transaction. It ends when the associate can add items.

Adding an existing customer to a cart with items

Refers to a customer who has a record in SCIS and has items in the cart. The action starts when a sales associate selects then adds a customer to a transaction. It ends when the associate can add items.

Note:

When a new customer is created or an existing customer is added to a sales transaction in progress, the application recreates the transaction.

Apply line-item discount, cart ready

Measures the time used to add a discount to an item in the cart. The action starts when a sales associate applies the discount from the discount form. It ends when the associate can resume interacting with the cart.

Apply transaction discount, cart ready

Measures the time used to apply a discount at the transaction level. The action starts when a sales associate applies the discount from the discount form. It ends when the associate can resume interacting with the cart.

Display add customer form

Measures the time used to prepare and display a form for adding a new customer. The action starts when a sales associate taps an option to add a new customer. It ends when the customer form appears.

Display item search results

Measures the time used to display search results. The action starts when the user enters a keyword in the global search bar and ends when the search results appear.

Adding an item to the cart

Measures the time used to add an item to the cart.

Open Product Detail Page (PDP)

Measures the time used to prepare the Product Details page. The action starts after the user clicks the item link. It ends when the user can add the item to the cart or select its options.

Authenticate login credentials

Measures the time used to authenticate login credentials. The action starts when the user clicks Log In. It ends when the user selects a role or location or proceeds directly to the open cart.

Payments, Payment Devices, and Refunds

End-to-end payment device processing

Measures the action beginning immediately after initialization and includes the time spent by the customer interacting with the payment device until the payment is processed.

Paying with credit memo

Measures the time to complete payment tendered using a credit memo. The action starts when the user applies payment. It ends when the receipt appears.

This action excludes the time, if needed, to manually enter credit memo information. For split payments, it ends when the user is ready to apply the next payment.

Paying with gift card

Measures the time to complete payment tendered using a gift card. The action starts when the user applies payment. It ends when the receipt appears.

This action excludes the time spent manually entering gift card information. For split payments, it ends when the user is ready to apply the next payment.

Paying with manual or custom payment methods

Measures the time used to process payments made with cash, with a check, or by entering credit card information directly in SCIS without a payment device.

The action starts when the user applies the payment and ends when the receipt appears. Custom payment methods that are part of your SCIS implementation are included in this action.

Priming the payment device

Measures the time spent initializing the PIN pad or other payment device. The action starts when the user enters the payment amount in SCIS. It ends when the device is ready to receive the customer’s credit, debit, or other payment source.

Priming the payment device for refund

Measures the time spent initializing payment device to accept refund information. The action starts when the user applies refund payment. It ends with a prompt that the device is ready to process the refund.

Refunding automatically to original card

Measures the time required to automatically refund payment to the original card used for purchase. The action starts when the payment device is primed to begin refund. It ends when the refund is applied to the card and the receipt appears.

Refunding to specific card

Measures the time required to refund a specific card after payment device is primed. The action starts when the payment device is primed to begin refund. It ends when the refund is applied to the card and the receipt appears.

This measurement is different from refunds automatically applied to the original purchase card.

Receipts

Display receipt after NetSuite payment confirmation

Starts when payment confirmation is received from NetSuite and ends when the receipt appears.

Display email receipt status

Shows if the email message sent succeeded or failed. The action starts when the user clicks Send and ends when the success or fail message displays.

Display print receipt status

Shows if printing succeeded or failed. The action starts when the user clicks Print and ends when the print job status is received.

If the auto-print feature is enabled, the action starts when the print request is sent to the printer and ends when the print job status is received.

Returns

Submit validated return, cart ready

Measures the time to prepare the cart after submitting a validated return. The action starts when the user clicks Return and ends when the user can interact with the cart again.

Unvalidated return, cart ready after selecting line

Measures the time to prepare the cart after selecting a line for unvalidated return. The action starts when the user clicks Return for the item and ends when the user can interact with the cart again.

Transaction Retrieval

Begin return from transaction details

Measures the time spent preparing a return from transaction details. The action starts when a sales associate initiates return from transaction details. It ends when the return form opens and the associate can begin selecting return options. The associate can start the return by a receipt scan, transaction history list, or customer timeline.

Retrieve transaction from scan

Measures the time spent retrieving transaction information through a NetSuite search initiated by SCIS. The action starts when a sales associate scans the transaction code on receipt. It ends when SCIS receives the information from NetSuite.

Display retrieved transaction

Measures the time used to display scanned transaction information retrieved from NetSuite. The action starts when information is made available to SCIS. It ends when SCIS displays the information to the sales associate.

Display store transaction history

Measures the time used to display a transaction from the store history option. The action starts when a sales associate taps option to display history and ends when the transaction list displays.

Customization

Based on how your organization has configured NetSuite, there may be custom scripts that run in the background while users perform various actions. User event scripts, client scripts, and workflows are captured in performance data as customizations. APM for Commerce features also show performance data from custom scripts included in other SuiteApps or bundles installed in your NetSuite account, so you can see how these affect performance.

Data related to customizations are available only after the SuitApp has finished processing them. To view the date when customization data was last updated, go to SuiteCommerce Action Diagnostics or SuiteCommerce Instore Performance Diagnostics and view the note that precedes the action tiles.

Action Performance Dashboards

Action Sensors

SuiteCommerce APM Action Sensors

SuiteCommerce InStore APM Action Sensors

Customization

Related Topics