Insights

We collect insights data for each configuration a user creates when they open the configurator

Inspect insights data

Go to the dashboard, select your desired configuration and click "Open" on the configurations area.

You can filter your insights and view details about your insights by clicking on the respective insights entry.

When you select a value for a filter property, conditions are connected using AND logic, meaning all conditions must be met. If you select multiple values within a single filter property, these values are connected using OR logic, meaning any of the selected values can apply.

Example

This example shows all configuration insights, which have been created in the last 7 days AND were the type is Configuration OR Finish.

Data collection

Generic information

• Creation date

• User who created the configuration (if it is a logged in Combeenation user) - for more info see personal configurations

• Type of the configuration

• On which version the configuration is based on 

• Preset id 

Information about the configuration

• When a configuration checkout will be performed, we store:

  • Checkout type

  • Used shop name

  • Price (if the price property of the checkout component is set)

• Configuration insights values

  Pricing tier dependent

  Depending on your pricing tier, this may not be visible at the moment.

  These values can be used to track specific configuration parameters and later filter them as needed. To specify those values go to your checkout component and edit the field Insights. Example:
  

  Configuration.Insights({
    color : "red",
    height : 100,
    hasAddon : true
  })

  Text values will be limited to 100 characters, and the amount of cfgn insights is also limited per company.

User and device metadata

We are also collecting device information from the client:

• Height & width of the viewed device (correctly speaking the iframe in which the configurator is embedded)

• Browser

• Mobile detection

• Country & City

  • Based on the IP address of the user, we try to roughly locate the country and city of the user. This is not 100% accurate.

  • Coming soon: Deactivate this location feature, if you don’t want to collect location information about your users