If you have a Google Analytics account, you can connect to your web data. For any interaction with the data in the Query Builder, BIME sends a dynamic request to the Google Analytics API and retrieves the results live. For information on Google Analytic's special query features, see About Google Analytics' special features.
Creating a connection
- In the Data sources library, select the Google Analytics icon ( ).
- Click Authenticate to sign in with your Google Analytics account.
- If your account is a premium account, click the Premium account checkbox to view all custom variables and columns in your schema.
- From the Sampling level drop-down list, select the number of sessions used to calculate results. There are three options available:
- A sample size that balances speed and accuracy.
- A smaller sample size with faster response.
- A larger sample with a more accurate response, but slower results.
Note: Depending on your sampling size, you might receive different results in BIME than in Google Analytics.
- Select a profile from the list at the bottom of the page. Click the All button to select all profiles or None to deselect all profiles.
Note: It is best to only aggregate profiles where you need to use the data together. Working with several profiles can impact the response time from the API.
- Click Save, and you will automatically be redirected to a new query.
- You can also edit cache and time zone options by clicking the Advanced button at the top of the Data source Builder. With the cache, only the first interaction will be live. For example, if the cache is set to refresh every day at midnight, the first dashboard load the next day will be live, but the second and subsequent loads will pull from the cache.
Your Google Analytics connection is now created.
- The number of profiles involved in a connection. BIME makes one call to Google for each profile connection. It is recommended to combine profiles only where you need to see numbers together.
- The number of segments involved in your query. BIME makes one call to Google for each segment used in your query. If you want to compare segments using the 'All Segments' brick, put it on the frame first, and select only the segments you want to see. This will keep the system from performing unnecessary queries. For more information on segments, see Segments.
- Cardinality of attributes, or the number of different values. Attributes like Page Paths, Keywords, and Sources contain several different values. They will increase the response time and put pressure on the BIME engine. When you integrate these attributes, consider using segments rather than in-memory calculated attributes to organize results. Segments will be pre-filtered by the API.
- Exceeded quota and token limits. The quota and token limits are shared across all Google data sources (Google Analytics, Adwords, MCF, RT, Search, Spreadsheet). Google Apps and services permit you to have a maximum of 25 API tokens using the same sign in, so 25 users can use the same sign in to connect to Google applications. If a 26th user tries to connect using the same credentials, the oldest token expires. The user with the oldest token will not be able to access that connection.