Source Hubspot: Web Analytics API

[roman-yermilov-gl]

What

Implement Web Analytics streams: #32702

How

Implemented new Web Analytics streams:

• ContactsWebAnalytics
• CompaniesWebAnalytics
• DealsWebAnalytics
• TicketsWebAnalytics
• EngagementsCallsWebAnalytics
• EngagementsEmailsWebAnalytics
• EngagementsMeetingsWebAnalytics
• EngagementsNotesWebAnalytics
• EngagementsTasksWebAnalytics
• GoalsWebAnalytics
• LineItemsWebAnalytics
• ProductsWebAnalytics
• Custom Objects Stream

Implement client side incremental sync
Make streams to share same schema for default properties
Make a toggle to turn on/off web analytics streams

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	⬜️ Ignored (Inspect)	Visit Preview		Dec 8, 2023 1:12pm

[github-actions]

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

• PR name follows PR naming conventions
• Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
• Secrets in the connector's spec are annotated with airbyte_secret
• All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
• Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
• Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
• If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

1. Check for hidden checklists in your PR description

2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

[timroes]

Hi, why was this merged, despite CI being red on it? The doc changes broke master. @roman-yermilov-gl could you please open another PR to fix the issues with the docs.

[18:10:23.024] Running build in Washington, D.C., USA (East) – iad1
[18:10:23.317] Cloning github.com/airbytehq/airbyte (Branch: master, Commit: 79d6e51)
[18:10:30.826] Cloning completed: 7.508s
[18:10:30.826] Running "git diff HEAD^ HEAD --quiet . ../docs"
[18:10:35.079] Restored build cache
[18:10:35.155] Running "vercel build"
[18:10:35.638] Vercel CLI 32.6.1
[18:10:36.270] Running "install" command: `yarn install `...
[18:10:36.605] yarn install v1.22.17
[18:10:36.677] [1/4] Resolving packages...
[18:10:37.121] success Already up-to-date.
[18:10:37.126] Done in 0.53s.
[18:10:37.337] yarn run v1.22.17
[18:10:37.363] $ docusaurus build
[18:10:38.432] Fetching connector registry...
[18:10:38.508] [INFO] [en] Creating an optimized production build...
[18:10:38.776] fetched 358 connectors form registry
[18:10:39.776] [info] [webpackbar] Compiling Client
[18:10:39.799] [info] [webpackbar] Compiling Server
[18:10:54.012] [success] [webpackbar] Client: Compiled with some errors in 14.24s
[18:10:54.016] 
[18:10:54.016] 
[18:10:54.016] SyntaxError: /vercel/path0/docs/integrations/sources/hubspot.md: Expected corresponding JSX closing tag for <HideInUI>. (289:0)
[18:10:54.017]   287 | <h3 {...{"id":"experimental-streams"}}>{`Experimental streams`}</h3>
[18:10:54.017]   288 | <p><a parentName="p" {...{"href":"https://developers.hubspot.com/docs/api/events/web-analytics"}}>{`Web Analytics`}</a>{` streams may be enabled as an experimental feature but please note that they are based on API which is currently in beta and may change at some point of time or be unstable.`}</p>
[18:10:54.017] > 289 | </FieldAnchor>
[18:10:54.017]       | ^
[18:10:54.017]   290 | <h3 {...{"id":"notes-on-the-engagements-stream"}}>{`Notes on the `}<inlineCode parentName="h3">{`engagements`}</inlineCode>{` stream`}</h3>
[18:10:54.017]   291 | <ol>
[18:10:54.018]   292 | <li parentName="ol">{`Objects in the `}<inlineCode parentName="li">{`engagements`}</inlineCode>{` stream can have one of the following types: `}<inlineCode parentName="li">{`note`}</inlineCode>{`, `}<inlineCode parentName="li">{`email`}</inlineCode>{`, `}<inlineCode parentName="li">{`task`}</inlineCode>{`, `}<inlineCode parentName="li">{`meeting`}</inlineCode>{`, `}<inlineCode parentName="li">{`call`}</inlineCode>{`. Depending on the type of engagement, different properties are set for that object in the `}<inlineCode parentName="li">{`engagements_metadata`}</inlineCode>{` table in the destination:`}</li>
[18:10:54.018] [ERROR] Client bundle compiled with errors therefore further build is impossible.
[18:10:54.091] error Command failed with exit code 1.
[18:10:54.091] info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[18:10:54.109] Error: Command "yarn build" exited with 1

[erohmensing]

^ Specifically I think the issue is that you can't use a FieldAnchor within a HideInUI component, as the field anchor only works within the UI

[timroes]

I think it might be related to this (https://github.com/airbytehq/airbyte/blob/master/docs/integrations/sources/hubspot.md?plain=1#L194) being a self-closing tag, but then closed in line 200 again.

[roman-yermilov-gl]

@timroes CI was green, all tests were passed and I had one approve

[roman-yermilov-gl]

@timroes Let me fix this self-closing tag in additional PR

[roman-yermilov-gl]

@timroes @erohmensing
I have prepared PR with fix: #33257