Managing the Sales Intelligence Extension as an Admin

Setting Up and Driving Adoption Across Your Team

The Similarweb Sales Intelligence browser extension is your team's fastest path to prospect insights, surfacing website data, contacts, and signals without leaving their existing workflow. As an admin or RevOps lead, you have direct control over how the extension is deployed, configured, and adopted across your organization.

This article walks through everything you can do from the admin seat: deploying the extension at scale, configuring what your team sees, tracking adoption, and driving ongoing engagement.

To access extension admin settings, go to Integrations in the left-hand navigation, then select Browser Extension.

Deploying the Extension to Your Team

Before your team can use the extension, they need to install it. There are two ways to make this happen.

Option 1: Send an Email Guide

From the Browser Extension settings page, use the Send email guide button to generate a ready-made installation message you can send to your team. The email includes a direct link to the extension and clear setup steps. This is the quickest path for smaller teams or targeted rollouts.

Option 2: IT-Managed Deployment (Recommended)

For larger teams, including to ensure every new hire has the extension from day one, use the View IT instructions option. This gives you a policy string you can pass directly to your IT team. Once configured, IT can push the extension automatically to any Chrome browser in a specific group (for example, everyone in the Sales department), and the installation will apply to new joiners automatically without any manual steps.

This is the most reliable way to ensure high installation rates. You can verify whether deployment was successful by monitoring the adoption dashboard (see below).

Tip: Even with IT deployment in place, it's worth sending the email guide as a heads-up so your team knows what the extension is and why it's there.

Configuring the Extension for Your Team

Once installed, the extension is ready to use. But what your team sees by default depends on how you've configured it. Admin-level configuration lets you set a starting point that's relevant to your team's workflows, without overwhelming new users.

Admin configuration is intentionally a starting point, not a lockdown. If a user wants to add widgets, adjust persona filters, or enable additional platforms, they can do so from their own extension settings. 

Access configuration settings from the Browser Extension section under Integrations.

Platforms and Integrations

Toggle on only the platforms your team actively uses. If your company runs on Salesforce, disable HubSpot and Microsoft Dynamics to keep the interface clean. If you don't use SalesLoft or Google Calendar, untoggle those too. Users will see only what's relevant to them.

Supported platforms include: 

• LinkedIn
• Salesforce
• HubSpot
• Microsoft Dynamics 365
• SalesLoft
• Outlook Office 365
• Google Workspace (Gmail, Google Calendar, Google Sheets)

Widgets

The extension's website overview displays a range of data widgets: traffic over time, engagement metrics, traffic geography, e-commerce overview, technologies, ad network traffic, and signals. Not every metric is relevant to every team. For example:

• A team selling to e-commerce companies may prioritize traffic and e-commerce data
• A team focused on tech companies may find technologies and signals more useful

As an admin, you can enable only the widgets that matter for your team's use case. Individual users can still customize their own view further. Admin configuration sets the default starting point, not a hard restriction.

Auto-Open Behavior

The extension can be set to open automatically whenever a user visits a supported page. This is a useful setting during onboarding as it ensures users discover the extension naturally, rather than having to remember to click it.

That said, auto-open can become disruptive once users are familiar with the product. Consider enabling it for new teams or during rollout, and communicate to users that they can disable it themselves if they prefer.

Defining Personas for Contact Discovery

One of the most powerful things an admin can do is define personas. A persona is a set of title-based rules. For example: "Show me contacts at Director level or above whose title contains the word 'Product'." When a user opens the extension on a company website or LinkedIn page, they can apply a persona to instantly filter the contact list to their most relevant targets.

How to Build Effective Personas

The best personas are built from your own closed-won data. Pull your CRM records from the past 12 months, look at the titles of contacts involved in deals you won, and identify the patterns. If your closed deals consistently involve Product Managers, VP of Marketing, and Head of Growth, build personas around those title patterns.

From the admin settings, you can create personas that appear as pre-built options for your entire team. Users can apply them with a single click, or modify them if their own accounts require something different.

Tracking Installation and Adoption

The Browser Extension settings page includes an adoption dashboard that gives you a full view of who has installed the extension and how actively they're using it.

What You Can See

• Total seats vs. installed: How many users in your account have installed the extension out of the total seats available.
• Per-user activity: For each user, you can see their installation status and their activity level.
• Role context: If a user hasn't installed the extension, check their role. Focus your attention on salespeople, account managers, and BDRs who aren't yet installed or active.

How to Use the Data

Filter or export the user list to identify specific groups:

• Not installed: Prioritize these for the deployment or email outreach steps above.
• Installed but low activity (e.g., 0–2 active days/month): These users may need a training session, a workshop, or a one-on-one walkthrough to understand how to get value from the extension.
• Highly active users (e.g., 19–22 active days/month): These are your super users. Engage them as internal champions. They can train peers and help drive adoption organically.

Building an Adoption Plan

Putting this all together, a successful extension rollout typically follows this sequence:

1. Deploy: Use IT-managed deployment or the email guide to ensure the extension is installed across your sales team.
2. Configure: Set default platforms, widgets, and personas relevant to your team's use case before users start exploring.
3. Enable auto-open (optional): Turn this on during initial rollout to help users discover the extension naturally in their existing workflows.
4. Monitor adoption: Check the dashboard after deployment. If installation rates are still low after IT configuration, follow up directly with specific users.
5. Drive engagement: Export low-activity users and create a plan: a group training session, an email series, or a designated internal champion who can run peer-to-peer enablement.
6. Iterate: As your team's workflows evolve or new use cases emerge, revisit your persona definitions and widget configuration.

Who Can Access These Settings?

Browser Extension configuration and the adoption dashboard are available to admins only. Individual users can adjust their own extension settings (widgets, personas, auto-open) but cannot see team-wide adoption data or change account-level defaults.

FAQ

Can users on my team only see what I've configured, or can they change their own settings? 
Admin configuration sets the default, not a lock. Users can adjust their own widgets, personas, and platform settings at any time.

A user has the extension installed but shows as inactive. What should I do? 
First check their role. For salespeople showing low usage, try a short enablement session or connection with an internal super user.

How does IT-managed deployment handle new hires? 
The policy applies automatically going forward. Any new user added to the designated group will have the extension pushed to their Chrome without any manual steps.

What should I do if the extension isn't showing data on a site?
Check that the site meets the minimum traffic threshold. Similarweb generally doesn't return data for sites with fewer than 100,000 monthly visits. If the site qualifies and data is still missing, confirm the user is logged into the correct SI account.