Google Analytics Integration

Caveat: each of the following integration directions was based on the UI when it was written. The UIs may change by the time you read this, so UI updates are beyond the scope of these articles. Please go to the integration target sites for their latest information on integration directions.

Google Analytics integration provides insight into the correlation between actual traffic metrics and ongoing monitoring checks.

Intro

Google Analytics (GA) is both free and easy to set up and use for novices and professionals alike, making it the go-to web analytics tool.

The Synthetic Monitoring integration with Google Analytics integration provides additional features:

• A dashboard with the most popular metrics from Google Analytics such as Visits, Page Views, and Average Visit Duration, all plotted on easy-to-read charts.

• A Google Analytics Real-Time Check.

• The ability to compare metrics (Visits and Page Views) from Google Analytics with performance metrics on the Check Results page.

Sample views:

Integration Dashboard

Integration Check

Setting up Google Analytics Real-Time Integration Check

You’ll already have set up a Google Analytics account need to set the integration up.

Step	Screenshot
Start from the New Integration+ → Google Analytics Real-Time ASM Menu
Step 1: Add the GA Real-Time Check Add a Name and Description Add Tags for easier sorting, categorization, and grouping
Step 2: Command and Location Enter the View ID: This is your specific Google Analytics Account ID. The format is ga:{View ID} example ga:12345678 Select the Metric: Active Users: How many visitors were active on your site over a given period of time. The active users report in Google Analytics helps you understand your website's (or mobile app’s) retention rate. It reports on how often visitors come back to your website over a certain time period. Page Views: Page view measurement allows you to measure the number of views you had for a particular page on your website. Pages often correspond to an entire HTML document, but they can also represent dynamically loaded content; this is known as "virtual pageviews." Screen Views: Screens in Google Analytics represent content users are viewing within an app. The equivalent concept for a website is pages. Measuring screen views allows you to see which content is being viewed most by your users and how are they are navigating between different pieces of content.
Step 3: Set Interval, Thresholds & Monitor Groups Polling Interval For all the thresholds, there are these types Baseline Constant: A constant, fixed, Threshold. Average: A dynamically calculated Threshold based on the Average of the check’s returned value. ASM will look at the specified period of time (2-1440 Hours. 1440 Hours = 60 Days) and calculate a Threshold value based on the percentage of the average returned value plus the offset (of the Returned Value) value specified by the user. The example shown: 150% of the average returned value for the last two hours plus 50 offset. Median: A dynamically calculated Threshold based on the Median of the check’s returned values. ASM will look at the specified period of time (2-1440 Hours. 1440 Hours = 60 Days) and calculate a Threshold value based on the percentage of the median returned value plus the offset (of the Returned Value) value specified by the user. Example shown: 120% of the median returned value for the last two hours plus 0 offset. Standard Deviation: A dynamically calculated Threshold based on the Standard Deviation of check’s returned values. ASM will look at the specified period of time (2-1440 Hours. 1440 Hours = 60 Days) and calculate a Threshold based on Standard Deviations (1, 1.5, 2, 2.5, 3, 5, or 10) plus the average returned value for the period of time plus the offset (of the Returned Value) value specified by the user. Example shown: Two Standard Deviations plus the average value for the last two hours plus 10 offset. High Warning Threshold: If the returned value from the check passes over the High Warning Threshold, it will trigger a Severity change of the check Warning (Yellow). High Error Threshold: If the returned value from the check passes over the High Error Threshold, it will trigger a Severity change of the check Error (Orange). Low Warning Threshold: If the returned value from the check drops below the Low Warning Threshold, it will trigger a Severity change of the check Warning (Yellow). Low Error Threshold: If the returned value from the check drops below the Low Error Threshold, it will trigger a Severity change of the check Error (Orange). Monitor Group(s): Select what Groups these checks will be reported under. If you have many Monitor Groups, enter a few letters of the group name(s) to filter down the list.	Average Example: Median Example: Standard Deviation Example: Monitor Group(s) Click Next when you have set the Interval, Thresholds & Monitor Groups
Summary and Confirmation Page When satisfied, click Create to create the check.

Google Analytics Data Policy

There are two use-cases for Google Analytics (1) Display of the ASM Dashboard, (2) Creating a Google Analytics Real-Time Check.

GA and the ASM Dashboard

For the Apica ASM Dashboard, we gather these Google Analytics metrics for display:

• ga:visits

• ga:visitors

• ga:pageviews

• ga:pageviewsPerVisit

• ga:avgPageLoadTime

• ga:newVisits,

• ga:percentNewVisits,

• ga:avgSessionDuration,

• ga:visitBounceRate,

Apica does not store them; it only shows the values for this page.

GA and the ASM Google Analytics Real-time Check

When Apica creates a Google Analytics Real-Time check, we gather these metrics:

• rt:activeUsers

• rt:pageviews

• rt:screenViews

Apica stores these metric values as check results in our SQL/Mongo database.

• We store these values for up to 1 year for raw data

• Aggregated data (e.g., median, average, min, max by hours, weeks, months) is stored as long as the user has an active subscription in Apica Synthetic Monitoring.