---
title: "Configuring Nectar DXP for WebRTC"
slug: "configuring-nectar-dxp-for-webrtc"
updated: 2026-10-15T18:07:11Z
published: 2026-10-15T18:07:11Z
canonical: "support.nectarcorp.com/configuring-nectar-dxp-for-webrtc"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.nectarcorp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring Nectar DXP for WebRTC

## Introduction

Nectar DXP users can install the Nectar DXP WebRTC extension to capture WebRTC metrics from browser-based telephony platforms.

WebRTC users have to authenticate against Nectar DXP in order to send call records. This authentication is facilitated by the Nectar DXP SSO integration, which is a prerequisite for WebRTC. This document describes how to configure an existing Nectar DXP SSO configuration to work with WebRTC.

## WebRTC Data Source Configuration

To enable the WebRTC data source in DXP, navigate to **Admin -> Advanced Settings -> Configuration -> Data Sources**, then scroll to **WebRTC** and click **Add Source**.

![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/image-1792087556019.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A02%3A29Z&se=2026-11-06T03%3A02%3A29Z&sr=c&sp=r&sig=IrcerhBJghGjI1Obxl3Rzh6KXNslDGBzel8sV4wTQBY%3D)

Select the desired platforms, set the Collection and Reauth. intervals, toggle Extension Logging if desired, then click **Save.**

## WebRTC Platforms

Currently supported platforms include:

- AirPhone
- Amazon Connect
- Avaya Cloud
- Cisco WebEX
- Five9
- Genesys Cloud
- MS Teams
- NICE Cxone
- Zoom
- Google Meet

## Accepted Domain Configuration

All email domains that are used by your WebRTC users have to be added to Nectar. These must be domains that are accepted by your SSO provider and are owned by your organization (ie. [gmail.com](//gmail.com) is not an acceptable domain). To add to your list of accepted domains, follow these instructions:

1. Click on the **ADMIN** tab on the top-right.
2. Click **Domain Names** in the left panel to open the Domain Names page.  ![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/image-1792086244293.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A02%3A29Z&se=2026-11-06T03%3A02%3A29Z&sr=c&sp=r&sig=IrcerhBJghGjI1Obxl3Rzh6KXNslDGBzel8sV4wTQBY%3D)
3. Click **Add Domain Name**.
4. Enter the name of the new domain and click **Add**.

## SSO Configuration

This section assumes you already have SSO configured for your environment.

The Nectar WebRTC extension uses your existing SSO configuration for authentication. When a user signs into the WebRTC extension, the SSO provider sends a list of groups the user is a member of. This list is parsed by Nectar DXP to determine the role to assign to the user. Select one or more groups that include all your WebRTC users and assign them to a Nectar DXP User role. Any role is acceptable, but for most customers, the **Self-View** role is sufficient. This gives just enough permissions to successfully authenticate to Nectar DXP without granting too many privileges. A user assigned to the **Self-View** role will be able to sign in with the WebRTC extension as well as the Nectar DXP web application to view their own call activity.

Assign one or more groups to WebRTC users by following the below instructions:

1. Click on the **ADMIN** tab on the top-right.
2. Click **SSO Configuration** in the left panel to open the SSO Configuration page.
3. Under **User Role Mapping**, pick the desired **Tenant User Role** (ie 'Self-View') and assign a group to the **External User Role** using the format required for your SSO provider.![](https://cdn.document360.io/f8330b7a-360f-4ca0-b0ac-2664b7c04c49/Images/Documentation/image-1792086282580.png?sv=2026-02-06&spr=https&st=2026-11-06T02%3A02%3A29Z&se=2026-11-06T03%3A02%3A29Z&sr=c&sp=r&sig=IrcerhBJghGjI1Obxl3Rzh6KXNslDGBzel8sV4wTQBY%3D)
4. Click **UPDATE** to save the configuration

## WebRTC Extension Recommendations

By default, the Nectar WebRTC extension re-authenticates every 24 hours. For the most seamless user experience, it is recommended that users sign into their browser using the same email address that will be used for the WebRTC extension. In most cases, this will make the re-authentication experience seamless. Otherwise, users will likely be prompted to re-authenticate via a pop-up browser tab that may confuse users.

## WebRTC Store URLs

| Chrome Web Store (v1) | [https://chromewebstore.google.com/detail/nectar-webrtc-analytics-u/cljibohjdlbgiadoeljcnpmnlgendajd](https://chromewebstore.google.com/detail/nectar-webrtc-analytics-u/cljibohjdlbgiadoeljcnpmnlgendajd) |
| --- | --- |
| Edge Add-ons (v1) | [https://microsoftedge.microsoft.com/addons/detail/nectar-webrtc-analytics-/ffpfbneknhhnhhnnimfkmiahnnfanlli](https://microsoftedge.microsoft.com/addons/detail/nectar-webrtc-analytics-/ffpfbneknhhnhhnnimfkmiahnnfanlli) |
| Chrome Web Store (v2) | [https://chromewebstore.google.com/detail/nectar-webrtc-analytics/epkpjghdlhbbncoanmfjgjijkbkgijkb](https://chromewebstore.google.com/detail/nectar-webrtc-analytics/epkpjghdlhbbncoanmfjgjijkbkgijkb) |