Skip to main content
Version: 9.2

Analytic Suite

The Analytic Suite widget enables users to display the distinct data analysis views available within the Analyze functionality of Qrvey Composer.
This includes Summaries, Tables, Metric Views, and more.


⚡ Quick Embeddable Sample (For Testing Only)

The following sample demonstrates how to quickly embed the Analytic Suite widget in your system.
⚠️ Important: This example is for testing purposes only.

  • API Key: In production, your API key must never be exposed in the UI. It should only be used in backend-to-backend communication.
  • Minimal Config: The sample uses the minimum set of properties needed for quick testing. Production deployments may require additional properties, as described below.
<!-- Tag -->
<an-dashboard config="anSuiteConfig"></an-dashboard>

<!-- Config -->
<script>
var anSuiteConfig = {
apiKey: "<YOUR_PRIVATE_API_KEY>", // Testing only. Do not expose in production.
domain: "<DOMAIN>",
appId: "<APP_ID>",
userId: "<USER_ID>",
qrveyId: "<DATASET_ID>" // Represents the dataset ID
};
</script>

<!-- Launcher -->
<script type="module" src="https://<WIDGETS_URL>/qrvey-an-widgets/an-dashboard/andashboard/andashboard.esm.js"></script>
<script nomodule src="https://<WIDGETS_URL>/qrvey-an-widgets/an-dashboard/andashboard/andashboard.js"></script>

Production Deployment

When deploying to production:

  • Use a qvToken instead of an apiKey.
  • Ensure appId, userId, and qrveyId are passed via the token, not hard-coded.
  • clientId, orgId, and orgs are not required for rendering the widget, but can be provided when you want Analytic Suite to act as a gateway for other components (e.g., Download Manager, Export Data modal, Subscriptions, personalization).
  • Configure additional properties such as settings, themeId, i18n, and customTokens as needed.
  • Keep the API key securely stored on the server side only.

Configuration Object

PropertyTypeRequiredqvToken SupportDescription
domainStringRequiredNoQrvey instance URL. Example: https://example.qrvey.com.
qvTokenStringRequired, if apiKey is not provided---Encrypted token used for secure authentication. Used in production to securely pass all required parameters. Cannot be used with apiKey.
apiKeyStringRequired, if qvToken is not providedNoSecret token for accessing the application. ⚠️ For testing only; do not use in production UI. Cannot be used with qvToken.
appIdStringRequiredYesID of the Qrvey application that contains the asset you want to embed.
userIdStringRequiredYesID of the Qrvey user that owns the application being embedded.
qrveyIdStringRequiredNoRepresents the dataset ID used by the Analytic Suite.
clientIdStringOptionalYesNot required for rendering. Unique identifier for the tenant end user. Enables personalization and Download Manager features.
orgIdStringOptionalYesNot required for rendering. Used to pass organization context to other components.
orgsObject ArrayOptionalOnlyNot required for rendering. Defines users and roles grouped by organization. Used to enable sharing/subscription features in other components.
timezoneObjectOptionalYesOverrides the time zone setting in Qrvey Admin Center. For more information, see Configuring Time Zone Settings.
customTokensObjectOptionalNoObject. Add custom tooltips onto metric panels. For details, please see Custom Tokens. Example: { "my_header": "A Cool Tooltip Header!" }
authenticatedSession.emailStringOptionalOnlySpecifies the email address to send scheduled exports. If not set, exports are sent to the email associated with the userId.
settingsObjectOptionalNoGeneral configuration object for controlling certain behaviors. For details, please see The Settings Object below.
userFiltersObjectOptionalYesCollection of custom filters applied to the Analytic Suite views. For more details, please see User Filters.
themeIdStringOptionalNoTheme ID to apply a pre-defined theme. For more details, please see Accessing a Theme Programmatically.

Orgs

For full details on how orgs work, please see Ownership, Orgs & Subscriptions.

PropertyTypeDescription
orgIdStringThe ID of the organization to which the roles and users will be defined next. Should correspond to the user in session's orgId if you want the roles and users to be listed in subscribe.
usersArrayAn object/array of users to be listed in the subscribe modal. This is not for the current user. Adjust clientId and email accordingly.
users.clientIdStringclientId of the user.
users.emailStringEmail address of the user.

Example:

const orgs = [
{
orgId: 'ORG_ID',
users: [
{
clientId: 'CLIENT_ID',
email: 'EMAIL'
},
{
clientId: 'CLIENT_ID2',
email: 'EMAIL2'
}
]
}
]

i18n

For more information, please see Internationalization, Step by Step.

PropertyTypeRequiredValue
langStringRequiredThe language to use for the UI. Example: "es".
localeStringOptionalThe locale code to use for date and number formatting. Example: "es-ES".

Settings

PropertyTypeRequired
viewString, Determines the initial view to display. Accepts:
SUMMARY_VIEW/MULTI_PANEL
TABULAR_VIEW
CUSTOM_VIEW
METRIC_VIEW
Default: MULTI_PANEL (which is an alias for SUMMARY_VIEW)
Optional
modeString, Determines displaying the complete layout or the views only. It depends on set view. Accepts:
COMPLETE
SIMPLE
Default: COMPLETE
Optional
displayModeString, Changes the style and extends the layout onto the entire container.
FULL
NORMAL
Default: NORMAL
Optional
stylesObject, Styles options object. These properties will extend from the current theme.Optional
styles.chartsTitleString, Sets the charts' title.Optional
styles.chartsFontFamilyString, Sets the chart's font family.Optional
styles.axisDataLabelsString, Sets axis labels color in charts.Optional
styles.dataLabelsString, Sets a hex color for data labels in charts.Optional
styles.valuesMainString, Sets a hex color for axis ticks values in charts.Optional
styles.chartsLegendsString, Sets a hex color for charts legends labels.Optional
styles.chartsTooltipsString, Sets a hex color for charts tooltips.Optional
styles.tableHeaderFontString, Sets a hex color for table header texts.Optional
styles.chartsMainString, Sets a hex color for chart data points like bars, symbols and lines.Optional
styles.themePaletteArray, Sets up to 20 hex colors that will be used for chart data points.Optional

Timezone

PropertyTypeRequired
timezone.offsetString. Specifies the timezone offset. Accepted formats: +03:00, -03, etc.Optional

Styles

The Single Panel Widget supports customization through CSS variables, allowing you to adapt the look and feel of dashboards to match your application’s design system. This includes control over fonts, colors, spacing, and other UI elements.

By overriding the available style variables, you can achieve a fully branded experience for end users without altering functionality. This is the recommended way to ensure consistency across embedded dashboards.

👉 For the complete list of available style variables and examples of how to use them, please refer to the Styles documentation.