Information collected by Coupa for product improvements

For Coupa to identify improvement areas for Data Guru, non-personally identifiable information is gathered and sent to Coupa. Under no circumstance does information gathered contain personally identifying information. Coupa follows the NIST standards on what can be construed as personally identifying information.

Collected Events

The following events are sent by Data Guru to Coupa:

  • ApplicationOpened

    This event is triggered when a user opens the application.

  • ProjectOpened

    This event is triggered when a user successfully opens a project.

  • HelpRequested

    This event is triggered when a user presses F1 within Data Guru.

  • UnhandledException

    Data Guru generates an unhandled exception.

Collected Fields

The following is a list of the fields in the metrics that Data Guru collects from users.

Event: (All)

Type: String

Description: Name of the specific collected event, to aid in reporting.

Example: "ApplicationOpened"

Event: (All)

Type: DateTime 

Description: The time at which the event occurred.

Example: May 15th, 2017

Event: (All)

Type: String

Description: A randomized unique identifier representing a single launch of the application.

Example: f68e76b1-6715-4ded-9add-8692f8d98765

Event: (All)

Type: String 

Description: The version of Data Guru that is sending the event. 

Example: 3.2.0.100

Event: (All)

Type: String

Description: The name and version of the operating system of the user's machine.

Example: "Microsoft Windows 8.1 Enterprise (6.3.9600)"

Event: (All)

Type: String

Description: The model name of the CPU of the user's machine.

Example: "Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz"

Event: (All)

Type: Double

Description: The total physical RAM of the user's machine, in GB.

Example: 12

Event: (All)

Type: String

Description: The type of the primary hard drive of the user's machine.

Example: "SSD"

Event: (All)

Type: Boolean

Description: A flag representing whether or not the user's display is using hardware acceleration.

Example: true

Event: (All)

Type: Boolean

Description: A flag representing whether the current user is a Coupa employee.

Example: true

Event: (All)

Type: String

Description: A unique identifier per user-machine combination, built from the user's user name, domain name, MAC address, and hard disk serial number. This information is hashed and converted into a UUID. Because it uses a piece of machine information that Coupa does not collect through licensing or any other means (hard disk SN) before hashing, it cannot be traced back to the user without direct access to the user's internal machine information.

Example: 1043265b-b411-5a67-1e20-f84b4459968f

Event: ProjectOpened

Type: String

Description: A unique identifier for the project based on the project file path.

Example: b9fb575a-44f8-4cfd-ae13-c0fdc9dcc56f

Event: ProjectOpened

Type: List<Tuple<String, Integer>>

Description: A list of the number of connections in the project of each connection type.

Example: ExcelFile:2, DelimitedFile:3, SqlServer:1

Event: ProjectOpened

Type: List<MacroInfo>

Description: A list of metadata objects representing macros within the project.

Event: ProjectOpened

Type: String

Description: A unique identifier for the macro.

Example: b9fb575a-44f8-4cfd-ae13-c0fdc9dcc56a

Event: ProjectOpened

Type: List<PluginTypeCount>

Description: A list of tuples representing the number of actions of a plugin-type executed within the associated macro.

Event: ProjectOpened

Type: String

Description: The name of the plugin-type.

Example: "ExcelFileImportPlugin"

Event: ProjectOpened

Type: Integer

Description: The number of actions of the associated plug-in type.

Example: 11

Event: ProjectOpened

Type: List<WorkflowInfo>

Description: A list of metadata objects representing workflows within the project.

Event: ProjectOpened

Type: String

Description: A unique identifier for the workflow.

Example: b9fb575a-44f8-4cfd-ae13-c0fdc9dcc56b

Event: ProjectOpened

Type: List<PluginTypeCount>

Description: A list of tuples representing the number of actions of a plug-in type which are executed within the associated workflow (this does not include actions within macros).

Event: ProjectOpened

Type: Integer

Description: The number of macros executed within the associated workflow.

Example: 6

Event: HelpRequested

Type: String

Description: The name of the Help Section requested.

Example: "Connections"

Event: HelpRequested

Type: String

Description: The address of the help content requested.

Example: "DG_Help_connections.htm"

Event: UnhandledException

Type: String

Description: The message in the Exception object.

Example: "Invalid operation exception."

Event: UnhandledException

Type: String

Description: The source object or application of the Exception object.

Example: "LLamasoft.DataGuru.BadObject"

Event: UnhandledException

Type: String

Description: A trace of the call stack when the Exception occurred.

Example: "at LLamasoft.Diagnostics.LLDiagnostics.ThrowInvalidOperationException(String message) in LLDiagnostics.cs:line 659"

Event: UnhandledException

Type: Integer

Description: A 32-bit error code representing the severity, facility, and reason for the error.

Example: -2146233079

Last modified: Thursday December 19, 2024

Is this useful?