Hi Airbyte Community 👋, I'm currently configuring a new connection using the Hubspot Source connector and encountering an issue with the visibility of an experimental stream. Connection Configuration • Connector: Hubspot Source • Authentication Method: OAuth (Public App) • Source Setting:

Enable experimental streams

is Activated (set to

true

). Scope Check I have carefully reviewed and confirmed the scopes granted to my Hubspot Public App. They include the necessary scopes documented for the experimental streams: •

crm.objects.contacts.read

•

business-intelligence

•

crm.schema.contacts.read

The Problem Despite activating the

Enable experimental streams

option and ensuring all required scopes are present in the OAuth app configuration, the

contacts_web_analytics

stream is not appearing in the list of available streams when I configure the connection. Question 1. What could be preventing this specific experimental stream from being listed? 2. Are there any other prerequisites (e.g., a specific Hubspot tier, feature enablement, or additional scopes not explicitly documented) that are required for the

contacts_web_analytics

stream to become visible? Any insights or suggestions from others who have successfully used this experimental stream would be greatly appreciated!

Based on the docs and issues you shared, there’s unfortunately no explicit mention of the

contacts_web_analytics

experimental stream or its prerequisites in the available HubSpot source documentation or GitHub/forum threads. From what we do have: - The HubSpot migration guide and related docs only describe breaking changes around contacts-related streams (deprecations, incremental behavior fixes, and the

marketing_emails

migration), but they don’t reference any

contacts_web_analytics

or “experimental streams” toggle or behavior.[\[HubSpot migration guide\](https://docs.airbyte.com/integrations/sources/hubspot-migrations)] - Known HubSpot issues cover: - URL length and field/column limits in contacts calls.[\[Forum URL too large\](https://discuss.airbyte.io/t/59)] - Performance and pagination/backfill problems on contacts and contact associations.[\[Forum performance\](https://discuss.airbyte.io/t/2219); \[Contacts associations auth\](https://github.com/airbytehq/airbyte/issues/62467)] - Incremental sync bugs on the

contacts

stream after low-code migration.[\[Contacts bookmarks\](https://github.com/airbytehq/airbyte/issues/60858)] - Missing / extra streams in other connectors (e.g., Google Ads) caused by permissions or config, but nothing analogous documented for HubSpot experimental streams.[\[Google Ads permissions\](https://github.com/airbytehq/airbyte/issues/52680)] None of these sources document: - How

Enable experimental streams

is supposed to work for HubSpot. - Any extra scopes, HubSpot tier requirements, or feature flags specifically tied to

contacts_web_analytics

. - Known bugs where

contacts_web_analytics

fails to appear despite the flag being enabled and scopes being present. Because of that, I can’t confidently say: 1. Why

contacts_web_analytics

is not appearing in your stream list. 2. Whether there are hidden prerequisites (HubSpot product tier, additional scopes, internal Airbyte feature flag, connector version constraints, etc.). Given the lack of explicit information in the knowledge sources, the most accurate guidance I can offer is: - Double‑check you’re on a recent HubSpot source connector version (several issues you shared show behavior changes across versions, especially around contacts streams).[\[Contacts bookmarks\](https://github.com/airbytehq/airbyte/issues/60858); \[HubSpot migration guide\](https://docs.airbyte.com/integrations/sources/hubspot-migrations)] - If you still don’t see the stream, this likely indicates: - Either the experimental stream isn’t yet generally exposed in the connector version you’re using, or - There is an undocumented limitation/bug. Since the existing docs and issues don’t cover this, the next concrete step is to open a GitHub issue against

source-hubspot

with: - Your connector version. - Screenshot of the source configuration (showing

Enable experimental streams

= true). - Confirmation of scopes on the HubSpot app. That will allow the Airbyte team to confirm whether this is: - A known but undocumented limitation, or - A bug that needs to be fixed or a feature flag that needs to be enabled. I’m sorry I can’t be more specific here—the current knowledge sources simply don’t contain details about

contacts_web_analytics

or experimental-stream visibility logic.