🎯New Source Connector Request: Google Analytics Source Connector

[ehisakhile]

Source Connector Google Analytics

What is a Vanus Connector

Vanus Connect allows you to skip the complex integration with external services by offering out-of-the-box connectors. Each connector acts as a proxy between outside services and your system, enabling users to have faster integrations with no codes. All data produced or processed by our connectors conform to the CloudEvents specification, which helps enterprises leverage event-driven architecture to do business in the age of events.

What is a Source Connector

A Source connector obtains data from an underlying data producer and delivers it to the target after the original data has been transformed into a CloudEvents. For example:

• MySQL Source: extracts data from the Binlog, transforms it into CloudEvents, and sends it to the target.

• GitHub Source: uses a Webhook server to receive the event from GitHub, transform them to CloudEvents, and send them to the target.

• AWS S3 Source: Uses the AWS SDK to get the data, transforms it into CloudEvents, and sends them to the target.

There are two types of connectors push or pull connectors.

• A push connector is passive and only does its logic when it receives an event
• A pull connector must pull the data in an interval. We use a push method when it’s possible

Features of this Source Connector

Receive events from Google Analytics for Audience Demographics, Traffic Sources, User Behavior, Content Performance.

Specific data needed

Audience Demographics

• Location: The geographic location of website visitors, including country, region, and city.
• Language: The language preferences of website visitors.
• Technology: The technology used by website visitors to access the site, including browser, operating system, and device type.

Traffic Sources

• Organic Search: The number of website visitors who arrived at the site through organic search results, along with the keywords used to find the site.
• Paid Search: The number of website visitors who arrived at the site through paid search campaigns, along with information about the campaigns, keywords, and ad groups.
• Direct Traffic: The number of website visitors who arrived at the site by typing the URL directly into the browser or using a bookmark.
• Referral Traffic: The number of website visitors who arrived at the site through links on other websites, along with information about the referring site.
• Social Media: The number of website visitors who arrived at the site through social media channels, including the specific social media platform and the content that brought them to the site.
• Email: The number of website visitors who arrived at the site through email campaigns, along with information about the campaigns, open rates, and click-through rates.
• Display Advertising: The number of website visitors who arrived at the site through display advertising campaigns, along with information about the campaigns, impressions, and click-through rates.
• Affiliates: The number of website visitors who arrived at the site through affiliate marketing campaigns, along with information about the affiliates and their promotional activities.

User Behaviour

• Pageviews: The number of times each page on the website has been viewed by visitors.
• Time on Page: The average amount of time visitors spend on each page.
• Bounce Rate: The percentage of visitors who leave the website after viewing only one page.
• Site Search: Information about how visitors are using the site search function, including the terms they search for and the pages they visit as a result.
• Events: Information about specific user interactions with the website, such as clicks on buttons or links, video views, and form submissions.

Content Performance

• Pageviews: The number of times each page on the website has been viewed by visitors.
• Unique Pageviews: The number of individual visitors who viewed each page.
• Time on Page: The average amount of time visitors spend on each page.
• Bounce Rate: The percentage of visitors who leave the website after viewing only one page.
• Exit Pages: The pages on the website where visitors are most likely to leave.
• Site Speed: Information about the loading speed of individual pages on the website, including average page load time and suggestions for improvement.

How to create a new connector

• Fork the vanus-connect repo.
• Create a source_twitter_proposal.md based on the source_proposal_example.md under the vanus-connect/proposals directory. The proposal will introduce how a developer tends to implement the connector in detail. The proposal PR must be approved and merged before going to the next step.
• Copy one of the source templates (Golang template, Java template) to vanus-connect/connectors/ and rename it as source-twitter.
• Implement your connector and submit a PR.
• Wait for the connector to be reviewed and approved.

How to claim to implement this connector

If you want to solve this issue, please leave a comment on this issue like:

I'd like to implement the connector, please assign it to me.

Vanus Community will assign the issue to you on time.