This guide explains how to use Beehive Pro to bring Google Analytics reports right to your site’s dashboard and, if you want, to the dashboards of every site in your multisite network.

Once Beehive is installed and activated, refer to this guide for assistance with configuration. Use the index on the left to quickly access guidance on specific features.

If you haven’t installed Beehive yet, then you should visit the Beehive Pro page where you can explore the plugin’s many features and sign up for a free trial membership.

Google Analytics Required

 

To properly configure Beehive, you need a Google Analytics account, which is free. If you need to create an account, the Get Google Analytics section of this guide will have you up to speed in minutes.

10.1 Guided Setup

The Guided Setup is available the first time Beehive is opened, and we encourage users to follow it. If you skipped the Guided Setup or want to re-configure Beehive, we recommend reading this section before jumping to the Settings section below and following the guidance offered there.

Before you begin, remember that you need a Google Analytics account, which is free. If you do not have an account already, see the Get Google Analytics section of this guide for guidance on creating that account, simply.

Choose a connection method

You must first decide what type of connection you wish to create between Beehive and Google Analytics. There are three options:

  • Tracking ID only – Adding a Tracking ID only allows data to be sent to a property within a Google Analytics account, but that data can only be viewed in Google Analytics and will not be available on the dashboards of the target site(s). If you are concerned about which users have access to a site’s statistics, Beehive can be configured to limit access to specific users.
  • Connect with Google – This method utilizes a shared API to display tracking statistics on site or network dashboards.
  • API Project (Recommended) – Creating a custom API Project for a specific site or network allows data to be displayed on site and network dashboards without the limitations inherent to a shared API.

If you wish to use the Tracking ID only, jump down a few paragraphs to that section and proceed.

If you wish to connect via API but are unsure which method to use, see the To Share or Not to Share section of this guide.

If you wish to use the custom API method that we recommend, see the Set up API Project section.

If you wish to use the shared API method, see the Connect with Google section of this guide.

10.1.1 Tracking ID Only

Tracking IDs are assigned to properties created within a Google Analytics account. If you have not yet created a property in Google Analytics for your site or network, you should do so before proceeding. See the Create a Property section of this guide if you need help creating a property.

If you have created a property, but need help locating the Tracking ID, scroll down a bit to the Locating a Tracking ID section below.

Once that property has been created, and if you’re certain you don’t want tracking statistics to appear on the dashboard of your site or network, then click the Add Google Analytics tracking ID link at the bottom of the Welcome to Beehive Pro screen.

On the next screen, enter your Google Analytics Tracking ID into the field provided and click Save Code.

That’s it. Google Analytics will begin collecting and organizing your tracking data. Remember, those stats can only be viewed in Google Analytics.

10.1.2 Locating a Tracking ID

Tracking IDs are stored within the Property menu of a Google Analytics account, located on the Admin page.

Login to your Google Analytics account and navigate to the Admin page.

In the Property column, locate and click Tracking Info. In the menu that appears, click Tracking Code, to reveal the Tracking ID.

Copy and save the ID in Beehive and you’re all set. Google Analytics will begin collecting and organizing your tracking data. Remember, those stats will only be available in the Google Analytics.

If you wish to re-configure Beehive to display analytics stats on your dashboards, see the Settings section of this guide.

10.2 Beehive Dashboard

The Dashboard statistics become available after Beehive is connected to Google Analytics and consists of the Overview, the Statistics quick access panel and the Google Tag Manager module (coming soon). Admins, particularly those managing multiple sites, can use the Dashboard to, quickly, get a big picture view of site activity over time.

Use the View Documentation button to access Beehive usage documentation (this document).

Overview

The Overview panel provides a snapshot of a site’s traffic stats for a specified period of time. Overview elements include:

  • Timeframe filter – Located next to the View Documentation button, use the filter to display traffic and activity stats for a day or for years or any time frame in between using the custom range option. The selected time frame will modify the stats displayed in both the Overview and Statistics panels.
  • Pageviews – The number of unique pageviews during the selected time frame, along with the percentage change during that same period.
  • New Users – The number of new users during the selected time frame, along with the percentage change during that same period.
  • Top Page – The most visited page during the selected time frame.
  • Top Search Engine – The search engine that generated the most traffic for a site during the selected time frame.
  • Top Medium – The path that generated the most traffic (direct, organic search, referrals, paid, etc.) during the selected time frame.

Statistics

This widget gives you a snapshot of your statistics and acts as a quick-access panel to view your full analytics report. Click the View Full Report button to learn more about all of your analytics.

Google Tag Manager

How does better tag management for marketing optimization sound? Google Tag Manager working together with Beehive is a match that will drastically improve your ability to add measurement codes and related code fragments to your sites quickly and easily. Sit tight, this is on its way!

10.3 Statistics

Once Beehive is connected using one of the two API connection methods, your Google Analytics statistics will be available in two locations:

  • Statistics page – A customizable, detailed report of site or network data over time.
  • Statistics widget – Beehive places a widget the dashboard of each connected site to display a detailed summary of Google Analytics statistics.

Statistics are not displayed on for sites or networks that are connected to Google Analytics using a Tracking ID only. If you wish to upgrade your connection to an API, see the To Share of Not to Share section of this guide for guidance.

10.3.1 Statistics Page

Beehive adds a Statistics tab to the Admin menu. Click the tab to access the Google Analytics Statistics page.

Sites that have not connected Beehive to Google Analytics will see an notification to that effect and a link to the Settings module, where new connections can be created.

Visitors

The Visitors panel displays traffic and activity data across multiple metrics, and using the available filters, will display comparative data over selected time frames.

The data for for each metric during the currently selected time frame is displayed along the bottom of the panel. Click any metric to view a chart detailing that metric’s activity over time.

These metrics are defined as:

  • Sessions – The number of unique user sessions during the selected time frame. A session is defined as a group of user interactions with your website that take place within a given time frame.
  • Users – The number of unique individual users who interacted with a site during the selected time frame.
  • Pageviews – The number of pages that were fully loaded into a browser at the request of users. A user who views five pages in one session will result in a single session and five pageviews.
  • Pages/Session – The average number of pages users viewed during a single session.
  • Average Time – The average amount of time users spent interacting with a site during a single session.
  • Bounce rate – A bounce occurs when a user leaves a site shortly after arriving without interacting with any elements on the page. The bounce rate is the number of these events as a percentage of all sessions during the selected time frame.

Time Frame Filter

Use the time frame filter to display data for a variety of periods, including custom data ranges.

Changing the time frame will refresh the data for every chart on the Statistics page, so all charts display data for the same period.

Compare to last period

Select the Compare to last period option, and then click a metric to see a comparison of the current data for that period and the data for the time frame preceding the current time frame.

For example, the lighter-colored line in the image below shows a site’s pageview data for the last 30 days, while the bolder line shows the same metric for the 30 days immediately preceding the last 30 days.

Mediums, Search Engines and Top pages

Beehive displays key Search Engine Optimization data in three circle charts directly below the Visitors data.

These charts show traffic data in the following categories:

  • Medium – The various sources for site traffic: organic, direct, referral, and so on.
  • Social Networks – Traffic that was referred to a site from a social network.
  • Search Engines – A ranking of search engines based on the amount of traffic derived from those sources.

Top Countries

The Top Countries chart uses color coding to show, geographically, where traffic is coming from to a site and the number of visitors from each country during the selected time frame.

Top Pages

A list of a site’s most visited pages and the number of visitors who viewed the pages during the selected time period, as well as the average amount of time users spent on that page and the percent change since the previous period.

The list contains links to the listed pages. Click any link to view that page.

10.3.2 Statistics widget

The Beehive Statistics widget provides access to site traffic statistics directly from the dashboard of any site with Beehive activated and connected to Google Analytics.

For sites that are not connected to Google Analytics, Beehive will display a notification to that effect. Click the link provided or go to the Settings module to connect Beehive to Google Analytics.

Widget Tools and Tabs

Use the tools and tabs at the top of the widget to access the desired statistical data or view.

The tools include:

  • See all stats – Click to open the Statistics page where a detailed report of site traffic data can be found.
  • Refresh data – Click to pull in fresh data from Google Analytics.
  • Time frame filter – Click the drop-down menu to apply a custom time frame and display data for the selected period only. The selected time frame will apply to all metrics viewed until the time frame is changed.

The tabs include:

  • General stats – Each panel within the General Stats tab can be clicked to see a more detailed display of that data.
  • Audience – The Audience tab displays data related to users behavior while on a site: numbers of unique users, sessions, pageview and page per session.
  • Top Pages and Views – A list of a site’s most visited pages, along with the number of visitors, the average time users spend on those pages and whether the pages are trending up or down.
  • Traffic – This tab displays the leading sources of a site’s traffic geographically, by search engine, medium and social network.

10.4 To Share or Not to Share

Google requires the use of an API to collect user data, because APIs provide better protection for that data. Beehive users have the option to use a shared API (Connect with Google) or to create a custom API project (Set up API project) specifically for their sites.

We strongly recommend creating a custom API project using the instructions provided in this guide.

It must be said that the Connect with Google method, typically, is very quick and easy to set up. However, it’s so simple because it uses an existing, hard-coded API that is shared by multiple users. Google limits the maximum number of requests a single API can make per hour and per day. A shared API significantly increases the chances of hitting this limit and distorting your stats.

Creating a custom API project, on the other hand, creates an exclusive connection just for your site or network. This custom connection ensures your stats will be as accurate as they can be, and it is extremely rare for a single user or even a single multisite network to reach the Google Analytics API limit. See Limits and Quotas on API Requests for more information on the limits of shared APIs.

However, it is important to note that Google does have a hard limit of 50 “refresh tokens” per account. That means that you can connect up to 50 domains using the same account. So if you do have lots of sites, or a multisite with lots of domain-mapped subsites, you might indeed hit that limit, and random sites will start displaying “unknown error occurred” messages. See Refresh token expiration for more information on that limit.

Workarounds for the above situation could be to have only 45-50 sites on one account, and create a different account for additional sites. Or add an additional user to your account to be able to add more sites to that account as that additional user.

10.5 Set up API Project

This section guides users through the process of creating a Google API project for Beehive.

Google API projects are created in the Google Developers Console and involve configuring a Google API, or multiple APIs, to service websites, mobile apps and other applications. In this project we’ll be combining three APIs from the Google API library into a single, robust data collection and reporting profile.

The APIs involved are:

The Google Analytics API allows those with established credentials to configure the data collection and reporting profile for a specific property (domain/site/nework).

The People API collects user profile and contact information for consenting users and shares that data with Google Analytics. This API can be enabled with a couple of clicks. No configuration is necessary.

The Google Analytics Reporting API allows authorized users to build custom dashboards in Google Analytics, automate complex reporting tasks and integrate with applications like Beehive. Like The People API, the Reporting API requries no configuration and is enabled with a couple of clicks.

Begin by signing into a Google or G-Suite account associated with the site on which Beehive is being configured, then navigate to the Google Developer Console . If this is your first time accessing the console, agree to the Terms and Service to proceed.

This is the Google API project dashboard, where API projects are created and managed. Click Create to initiate a new project.

If you don’t see the Create button, it may be that an API project was created with this account at some point in the past, possibly unrelated to Beehive. In this case, click the Select a Project drop-down and then click New Project. Remember this screen and remember that drop-down menu, because this is where you will come if you ever wish to modify your Beehive API project or any other Google API projects you may initiate.

Give the project a name. If you are using a G-Suite account, select the organization and location you want to associate with it, then click Create.

10.5.1 Enabling APIs

Click Enable APIs and Services to access the Google library of APIs.

Enable the Google Analytics API

Use the search tool to locate the Google Analytics API or scroll to the bottom of the page where it’s located and click Google Analytics API.

Cick Enable.

If you are prompted to create credentials, ignore the request and exit the prompt. Google requires OAuth 2.0 credentials for API connections, but it is better to add all the required APIs before creating those credentials.

Enable Google People API

In a similar way to how you enabled the Google Analytics API, click the Enable APIs & Services button to access the Google API Library.

Type “people” into the search tool to quickly locate Google People API, then select it and click Enable to add it to the project.

MISSING CONTENT?

Enable Google Analytics Reporting API

Finally, add the Google Analytics Reporting API in the same way. Click Enable APIs and Services to return to the API Library. Search for “reporting”, select and Enable the Google Analytics Reporting API.

Once the three required APIs are added to the project, it’s time to create the OAuth Client ID.

10.5.2 Credentials and Consent Screen

Google requires informed user consent for most of its data collection APIs. In the case of Beehive, Google requires an OAuth 2.0 Client ID which, in turn, requires that users grant consent to the data collection via a consent screen. First, we will configure the constent screen, then the Client ID.

OAuth 2.0 and Google Verification

 

OAuth 2.0 is a protocol intended to ensure users whose data is being collected and handed off to a third-party have consented to that transaction. Google requires sites to identify the data collection app involved and to verify that data is being collected in accordance with Google policies before granting OAuth 2.0 credentials. Depending on the sensitivity of the data or the API involved, Google may require an application and its consent notification to submit to a verification process before providing those credentials. See the Scopes section of this guide for more information about that verification process.

There are many routes through the OAuth credential screens, but the following path is the most direct.

First, navigate to your Google API Project Dashboard by clicking Google APIs in the upper left corner. Once there, click the Credentials tab.

Then click Create Credentials and select OAuth client ID from the dropdown menu.

Configure the Consent Screen

Google requires users consent to having their data collected via a popup consent screen, and requires Admins to provide information that will appear on that screen.

Click Configure Consent Screen to proceed.

Depending on the user data being collected and its intended use, some Admins may be required to provide more information than others. Beehive Admins are required to identify the type of data being collected, the application’s name, an email address for support requests and an authorized domain.

This is an example of what a configured Beehive consent screen looks like.

The following guidance will help you complete the required consent screen fields.

User Type – If you choose the Internal mode, access will be limited to G Suite users within your organization and doesn’t require verification. External is available to anyone with a Google Account.

Click Create once you have chosen your User Type.

Application Type – Select Public, if you want to allow any Google account to connect to Beehive. You’d want this option to enable clients or subsite admins to connect with their Google accounts using this same API. Select Internal if you want to limit access to only users within your organization, or if you are using a GSuite account for this API.

Application Name – This name that will appear on consent screens indicating who is requesting users’ data. Google requires that the name accurately reflect your application and be consistent with the application name users see elsewhere. You can include your site or company name with the application name, but be careful not to use a name that suggests your application is from Google or any entity other than your own.

Support email – By default, the Google account you signed in with will appear as the support email. Later, you can create a user with an email address specifically for support requests.

DID YOU KNOW?

WPMU DEV members are authorized up to 10 free email accounts that can be configured in minutes to display the member’s domain in the email address. See our Email Hosting product page for details.

Scopes for Google APIs – We do not recommend adding scopes to your Beehive API project. If you require additional scopes, see the Scopes and Verification section below before adding them. Otherwise, no action is needed in this section.

Authorized domains – Type your domain name into this field and hit return. Google requires that authorized domains be top-level domains only, such as example.edu, mysite.com, etc. Subdomains, such as analytics.example.com, cannot be an authorized domain; however, once an authorized domain is added, Admins can use any of its subdomains or pages elsewhere, as needed. Enter your domain into the field provided, and if it is accepted, the domain name will appear above the field.

When ready, click Save to preserve the information and exit the page.

Go back to the Credentials tab in your Google APIs & Services dashboard and click the Create Credentials select OAuth client ID from the dropdown menu, as you did before.

Create Client ID

Complete the Create OAuth Client ID form as instructed below and click Create.

Application type – Select Web application and a series of settings relevant to web applications will appear.

Name – Here you are actually naming the credentials associated with this project. The name can be anything that works for you.

Authorized Javascript origins – All the javascript required for Beehive to function is contained in the app, so Admins can ignore this field.

Authorized redirect URLs– You must add the URL of the site being connected twice, once with a slash (/) at the end and once without a slash (/) at the end.

When you are ready, click Create and Google will generate your credentials.

You can copy your Client ID and Client Secret key directly from this module or you can locate them at a later stage in your Credentials tab, as discussed below.

Locating Your Client Secret and Client ID

The Credentials screen contains a list of the Client IDs for all your Google API projects. Each Client ID will have an associated Client Secret, which can be viewed by clicking the name of the project or the Edit icon.

When you open the Client ID page, the Secret Key may not appear immediately. If not, simply refresh the page, and the key should appear beneath the Client ID.

The Client ID for this project cannot be changed, but users can reset the Client Secret as necessary by clicking Reset Secret.

Return to the Hive

Return to your site and copy/paste the Client ID and Client Secret into their respective fields in Beehive and click Authorize.

You will be asked to log in to the API project and grant permission for Google Analytics to collect data from this site. Log in with the Google account used to create the project.

Click Allow in the pop up to confirm the connection between Beehive and Google Analytics.

At this point, you have created an API project and given permission for Beehive to pass data to that project. Now, you must choose the profile within that project with which this site’s data to be a site is connected to Google Analytics with a robust data collection and reporting profile. It may take several minutes for data to begin appearing in your Dashboard. In the meantime, there are a few more steps required to complete the Beehive configuration.

PRO TIP

You can create multiple Views for each property (domain/site/network) in Google Analytics. Multiple Views allow you to create more narrowly tailored reports, which has the added benefit of cleaning up the data as Google separates it from the rest.

Setup Your Account

Now that Beehive is connected, just a few housekeeping tasks and you’re done. First, you will establish which roles will able to view the Google Analytics data and reports that appear on your dashboard and in Beehive.

From the drop-down menu select the View, formerly profile, associated with this site. Below that, ensure the Automatically detect tracking ID is enabled. In the list below that, select the user roles allowed to access analytics data and reports.

When the Finishing Up screen closes, the integration will be complete.

Congratulations! You have successfully integrated Google Analytics into your site with Beehive.

10.6 Connect with Google

To use the shared API, rather than the custom API we recommend, click Connect with Google in the Welcome to Beehive screen or the Settings module in Beehive.

Choose the Google account you wish to use to connect Beehive with Google Analytics.

PRO TIP

You can create multiple Views for each property (domain/site/network) in Google Analytics. Multiple Views allow you to create more narrowly tailored reports, which has the added benefit of cleaning up the data as Google separates it from the rest.

Click Allow to authorize Beehive to access your Google Analytics account.

Copy and paste the code Google provides into the field provided and click Authorize.

Beehive is now connected to your Google Analytics account, but it still needs two things before it begins collecting data for a given site.

First, Beehive needs to know what View within that account should be associated with the data collected. The drop-down menu contains a list of the Views that exist within the connected account. Use it to select the correct View, or create a new View for this project in Google Analytics and it will appear in the list.

Next, Beehive needs the tracking ID Google assigned to that View when it was created. Select the Automatically detect tracking ID option and Beehive will add the code for you. That code can be added at a later time in the Settings module.

Select the user roles who will have access to the Beehive Analytics reports for this site or network, then click Continue.

Tracking Admin Pages

By default, analytics data for each network site is displayed on that site’s dashboard only. However, by enabling this Admin Page Tracking feature, data from every site will be shared with the Network Admin site as well.

Click Finish and Beehive will begin feeding data to Google Analytics, which will organize and return that data as statistics in the Beehive dashboard widget and on the Statistics page.

10.7 Connecting a Multisite Network

Each subsite in a multisite network must be connected individually, but if Beehive is installed, network activated and connected in Network Admin using the Google Analytics API, we will use that custom connection for the entire network. This allows subsites to connect with the fast and easy Connect with Google method but still reap the benefits of a custom API connection.

NOTE:

If you are unsure why we recommend creating a custom connection, see To Share or Not to Share

.

The steps for connecting Beehive to Google Analytics for a multisite network are essentially the same as connecting a single site, although multisites have a couple of unique options after the connection is complete. Take a moment to familiarize yourself with them now, or return to this section when you are ready to configure these options.

When you’re ready, go to Guided Setup to begin configuring Beehive, and remember to configure the plugin from Network Admin before connecting any subsites.

Granting Permission Authority

After connecting Beehive to Google Analytics in Network Admin, you will be given a chance to determine what users can access the analytics data. This setting applies to the Network Admin site only. Enable Allow subsite admins to overwrite this setting, and subsite admins will be able to choose for themselves who sees their sites’ data.

Tracking Admin Pages

By default, analytics data for each network site is displayed on that site’s dashboard only. However, by enabling this Admin Page Tracking feature, data from every site will be shared with the Network Admin site as well.

Click Finish to complete the initial setup.

Beehive is now connected to your Network Admin site, and you can now begin connecting subsites using the Connect with Google option.

10.7.1 Connecting Network Subsites

If you followed our advice and connected the network using the Google Analytics API and did so from Network Admin, every subsite can now connect using the simple Connect with Google method.

Begin by navigating to any subsite.

You should see a notification that the site is not yet connected to Google Analytics. Click Connect Account.

From this point on, follow the process discussed in Connect with Google section.

10.8 Settings

Settings is where admins can modify Beehive’s configuration, including resetting the Google Analytics connection to, essentially, start over.

NOTE

If you are attempting to authenticate and connect to Google Analytics for the first time and are unfamiliar with the process, we recommend reading the Guided Setup section of this guide. It provides an easy-to-understand overview of the various connection types and will help you make an informed choice about the connection method that best serves your needs.

10.8.1 Tracking Settings

Tracking Settings is where the credentials that connect Beehive to Google Analytics are managed.

Account

To display your Google Analytics statistics on your site dashboards you will need to connect with one of the two API methods:

  • Connect with Google – a shared API with multiple users
  • Set up API project (Recommended) – creates a custom API connection for a specific site or network of sites.

If you are unfamiliar with Google APIs, we recommend reading the To Share of Not to Share section above before proceeding.

  • Connect with Google – To connect Beehive to Google Analytics using the shared API, click Connect with Google and enter your Access Code in the field provided. If you do not have an access code, see the Connect with Google section of this guide.
  • Set up API project (Recommended) – To connect Beehive to Google Analytics using a custom API project you created in the Google Developers Console, click Set up API project and enter the Client ID and Client Secret into the fields provided. If you have not yet created an API project or don’t have the required credentials, see the Set up API project section of this guide.

Remember to click Save Changes before leaving the Settings module or your changes may not be preserved.

If your connection has been successful, you will see a success message above the Account module.

Resetting the connection

Resetting the connection between Beehive and Google Analytics will remove the statistics data from the dashboard of every site being tracked. The data will not be lost, however, and can still be accessed in Google Analytics.

To reset the connection, click the tool icon and then select Log out or Switch Profile, both of which will disconnect Beehive from Google Analytics.

Tracking Statistics

If you only want to share site data with Google Analytics but do not want to display it on your dashboards, you can connect simply by entering a Tracking ID into the field provided. If you need help locating your Tracking ID, see the Locating a Tracking ID section of this guide.

Remember to click Save Changes before leaving the Settings module or your changes may not be preserved.

10.8.2 General

The features in the General Settings allow users to leverage additional functionality from their Beehive-Google Analytics connection.

Admin pages tracking

By default, only activity on frontend pages of your site is tracked. However, by enabling this Admin Page Tracking feature, activity in the wp-admin is also tracked.

IP Anonymization

Google does collect IP addesses in order to report geolocation data, but those address are never reported and are stored in an anonymous state. When enabled, IP Anonymization modifies collected IP addresses so they cannot be used by Google and allows you to ensure your audience that you are not leaving it up to Google to protect their data.

Multisite Super Admins have an additional option that, when selected, forces all subsites to anonymize IP addresses, as well.

Display Advertising

When enabled, this feature adds Google advertising cookies to your site or network so you can do things like:

  • Create Remarketing Audiences based on specific behavior, demographic, and interest data, and share those lists with Google Ads
  • Use demographic and interest data in your Analytics reports
  • Create Segments based on demographic and interest data

Keep in mind that you may need to update your privacy policy if you wish to enabled this feature.

Permissions

Here you can determine who can see the data and reports compiled by Google Analytics. On multisite networks, the roles enabled will apply to every site in the network unless the Allow site admins to overwrite this setting is enabled.

Capabilities

Capabilites are an extension of the Roles feature and allows SuperAdmins to delegate control over subsites in highly specific ways.

Access the WordPress list of commands and apply those commands in the field provided to craft custom roles with capabilities defined by you.

10.8.3 Permissions

Here you can determine who can see the data and reports compiled by Google Analytics. On multisite networks, the roles enabled will apply to every site in the network unless the Allow site admins to overwrite this setting is enabled.

Capabilities

Capabilites are an extension of the Roles feature and allows SuperAdmins to delegate control over subsites in highly specific ways.

Access the WordPress list of commands and apply those commands in the field provided to craft custom roles with capabilities defined by you.

10.9 Get Google Analytics

This section guides users through creating a Google Analytics account and a property within that account that Beehive can connect to during configuration.

Since you don’t have an account, perhaps you don’t know how Google Analytics works. Here’s the short version: Google Analytics, using javascript, tracks what users do on your sites—what links they click, what pages they view and for how long and many other data points as well.

Google can do this because users—that’s you—insert custom code into the code for every page they want tracked. This code tells Google who owns the data collected from a given page so it can be associated with the right account in Analytics. The data is then categorized based on a myriad of variables– many of which can be customized in Beehive– and displayed as reports on site dashboards that admins can use to plan and achieve site or network goals.

It may be helpful to also understand how a Google Analytics account is structured. There’s the Account, of course, and within each account there are properties and within each property there are Views.

Here’s how Google defines each:

Account: Think of it as the top-level folder that you access using your login details. If you are managing a single website, then one account is sufficient. If you’re managing multiple websites that aren’t directly related, then these should be stored in separate accounts. Google allows users to create up to 100 accounts.

Property: A “property” is simply Google-speak for a website or network of sites that have been added to a Google Analytics account. When Beehives connects, it connects to a specific property. Each account can have up to 50 properties.

Views: Views tell Google Analytics what reports should be created for a given property. In simplest terms, each view is a separate report. A default View called All Website Data is defined for each property when it’s created. Users can create up to 25 custom Views, each targeting a unique traffic factor or group of factors, as defined by the user.

PRO TIP

You can create multiple Views for each property (domain/site/network) in Google Analytics. Multiple Views allow you to create more narrowly tailored reports, which has the added benefit of cleaning up the data as Google parses it to fulfill your request.

Sign Up

Ensure that you are logged in to a Google account with admin privileges on the site or network you wish to connect with Beehive. Browse to the Google Analytics Setup page and click Sign Up.

By the way, if you clicked the Google Analytics Setup Page link above, and it opened an Analytics Dashboard, then the Google account you’re using already is associated with an Analytics account.

Create Account

Create your first Analytics account by simply giving the account a name and then choosing what, if any, of your collected data you want to share. Click Next to proceed.

Click Website to tell Google what type of analytics the account will require.

Create a Property

In the next series of steps, you will be creating the first property associated with the new account. This is accomplished from the account Admin page, a button for which is located in the bottom left corner of any Google Analytics page.

Locate and click the Admin button, then lick the Create property button to proceed.

Now, tell Google Analytics what type of data this property will be using: website data, app data or both. For our purposes, click Web and then click the Continue button at the bottom of the screen.

Enter the site or network URL, choose an industry category and time zone, then click Create.

If the Google Analytics Terms of Service popup appears, click Agree to proceed.

If you have been following this guide, you should now have a Google Analytics account with a property created and waiting for data from your site or network. Once that property was created, Google assigned to it a Tracking ID, which needs to be copied and pasted into the appropriate fields in Beehive.

Tracking IDs and Codes

To locate the Tracking ID, begin on the Admin page and locate the Create Property column. In that column, locate and click Tracking Info, and in the menu that appears, click Tracking Code.

This property’s Tracking ID identifies the property in which the collected data should be stored and the Global Site Tag, sometimes called as the tracking code, is used to track conversions.

The Tracking ID and global site tag must be present on your site for Beehive to achieves its full potential. They can be added manually, but we recommend allowing Beehive to accomplish this, automatically.

Congratulations! You now have a Google Analytics account and a property waiting to connect with Beehive. Go to Guided Setup section of this document for guidance on configuring Beehive.

10.10 Scopes and Verification

We do not recommend adding scopes to your Beehive API project. OAutho 2.0 verification is sufficient for the three scopes employed by Beehive and results in essentially immediate approval of your application by Google.

The data collected by Beehive requires three scopes:

userinfo.profile – Collects publicly available personal information.

userinfo.email – Collects users email addresses.

analytics.readonly – Shares analytics data with a client service, in this case Beehive.

Adding scopes to your Beehive API project can broaden the type of data collected, but doing so may also trigger a higher verification standard that prevents immediate creation of the required credentials or places limits on Beehive until the verification process is complete. The verification process for highly sensitive scopes can take weeks.

NOTE

If you are considering adding scopes to your Beehive API project, see the Scopes and Verification section of this guide before doing so.

Blog Writing EstimateUse this form to request a cost estimate for all content types except technical documentation. Tech docs should be requested using the Documentation form. Thanks!

Asterisks (*) indicate required fields. This form is highly compact, so most fields require responses.

Experience

NOTABLE WRITING EXPERIENCE

European Stars and Stripes — Darmstadt, DE
Produced news, feature and investigative reports for Germany-based American newspaper.

The Advocate — Baton Rouge, LA, USA
Produced news, feature and investigative reports for daily American newspaper.

Ruston News Group — Ruston, LA, USA
Editor for weekly newspaper published in rural North Louisiana.

NOTABLE TECH PROJECTS

WPMU DEV, Incsub, LLC — Documentation developer
Mar 2018 - Aug 2020
Developed usage documentation and provided general editorial support to international WordPress development, hosting and support company.

William Allison - A Law Firm — Business Development Project Manager
Nov 2015 - Nov 2016
Responsible for evaluating, purchasing and implementing technology solutions to enhance the law firm’s business development and practice management systems. My areas of responsibility were twofold: modernization of the firm’s electronic case management system and building an online marketing presence that generated quality case leads.

Carrollton Group — Technical Writer
Oct 2014 - Nov 2015
Documented testing procedures for the Deepwater Horizon Claims Center online claims processing network of sites.

Industrial Training Institute — Technical Writing Instructor
Aug 2011 - May 2013
Developed a comprehensive technical writing training program for technical college students entering the industrial, medical and information technology fields.

Georgia Pacific — Training Documentation Specialist
Aug 2009 - Dec 2010
Developed training documentation and testing materials in support of project to migrate GP's massive training program to an online environment.

EDUCATION
LSU — Mass Communications
Baton Rouge, LA

RFP EstimateUse this form to submit a Request for Proposal or other document(s) that clearly defines your content needs. If no such document exists, please use the Blog Writing or Documentation form to request estimates.

Documentation EstimateUse this form to request a cost estimate for the development of online user, product or process documentation and any supporting image or video content. All other projects should be submitted using the Blog Writing form. Thanks!

Asterisks (*) indicate required fields. This form is highly compact, so most fields require responses.