1 - Integrate the Daily Aggregate Database With Google Analytics

Before starting the configuration below, make sure you have reviewed all Installation & Configuration: Considerations.

Step 1: Get the Property ID from Google Analytics

You will need to copy a Property ID from Google Analytics, then paste it into the Daily Aggregate Database configuration. View permissions are acceptable.

A Property ID is a unique ID for a particular property in Google Analytics that allows you to retrieve Google Analytics 4 data.

1. Navigate to your Google Analytics dashboard.
2. In the upper left corner, you will see your current Property.
3. Click on the Property name, which brings up a list of all the Properties that you have access to, with each Property's ID under the Property's Name.
4. Copy the Property ID of the Property that contains the set of data you want to be captured in Salesforce.

NOTE: Your Google Analytics account might have multiple views. Confirm that the Property ID you select belongs to a Property that has data available for the following metrics:

• Cost
• Pageviews
• Clicks
• Cost Per Click
• Users
• New Users
• Sessions
• Session Duration

If your Property does not have data for any of these metrics, DST will still capture and report on the remaining metrics.

Step 2: Configure the Daily Aggregate Database in Salesforce

If you have not yet installed the Digital Source Tracker package and activated your license for the Daily Aggregate Database, follow the instructions in the Installation & Configuration: Considerations documentation. Make sure you are on version 1.3 or later of the Digital Source Tracker package.

You must already have Touchpoint Capture configured. Visit the Touchpoint Capture guide in this documentation for more information.

1. Go to the Ad Platform Configuration page.
   • Navigate to Setup | Build | Installed Packages | Full Circle Response Management | Configure | Digital Source Tracker | Ad Platform Configuration.

2. Under the Google Analytics Configuration section, add your Google Property ID and/or Google View ID.

Depending on whether you want Google Analytics 4 and/or Universal Analytics data, take the Google Property ID and/or Google View ID that you got from Google Analytics, and add them to the Google Property ID and/or Google View ID fields.

Do not enable the feature yet. You must complete additional steps.

3. (Optional) Navigate to Daily Aggregate Database Configuration tab and configure additional integration configuration fields.

The following fields have default values assigned. Each field's purpose is described below.

• Would you like to enable Daily Aggregate Database daily aggregation?: After the various configuration steps that we will cover, this radio button enables integration between your Google Analytics and Salesforce instances. Our configuration instructions will let you know the right time to toggle this to Yes.
• Google Analytics Monitoring Interval (Minutes): Google Analytics data, even when you visit their dashboard views directly, is not guaranteed to reflect their final ("golden") data for some time after it is captured. For Universal Analytics data, this can take up to 48 hours. For Google Analytics 4 data, Google does not specify how long it may take for data to be golden. By default, DST will consider Google Analytics 4 data to be golden after 48 hours. Within these 48 hours, as information from Google Analytics may change, you may adjust the frequency with which Google Analytics data is rebuilt. This is a non-negative integer that specifies how frequently non-golden Google Analytics data is rebuilt. The default is 60 minutes. Given the volume and behavior of your website traffic captured by Google Analytics, you may want to adjust this setting.
• Daily Aggregation Rebuild - Minimum Volume: For customers with high volumes of daily website traffic, you may only care about tracking and analyzing a certain minimum volume of traffic. This setting allows you to increase the minimum visits threshold to focus that on the most impactful portion of website visitors. If the data source is Google Analytics, this minimum default value means 0 Pageviews. If the data source is Full Circle Insights' Touchpoint Capture, this minimum default value means 0 Visits, where a Visit equates to a visitor who has made themselves known by filling out a form and converting. This is a non-negative integer that specifies the minimum number of volume that a data source needs to have before being captured in an Aggregate Database Entry record. The data is captured and updated in the Aggregate Database Entry by the Daily Aggregation Rebuild. The default is 0.
• Daily Aggregation Database Rebuild - Earliest Date: When dates on campaign members are updated, the Daily Aggregate Database rebuilds the data for Funnel Data Aggregation to reflect any changes. If many campaign members with dates in the past are updated, this could cause a backup of Aggregate Database Rebuild requests that may be unnecessary, potentially causing processing delays and creation of unnecessary records in the Aggregate Database that aren't going to be reported on. Enter a date here to prevent rebuild requests before this date in order to prevent unnecessary rebuild requests.
• Daily Aggregation Rebuild Interval (Minutes): An aggregation rebuild request is a request to rebuild the information contained in the Aggregate Database Entry records, so the most updated information is represented. Depending on the volume and velocity patterns of your website's traffic, and how frequently prospects end up converting by filling out a form, you can adjust this interval. This is a non-negative integer that specifies the minutes between daily aggregation rebuild requests processed by Full Circle Insights. The default is every 15 minutes.

A rebuild request initiates the re-evaluation of all Aggregate Database Entry records for that particular day. As the Aggregate Database Entry record receives data from a variety of sources (Google Analytics, Digital Source Tracker Standard, and Response Management), data from the master source may change slightly at different times of the day. Any changes to data that impact the Aggregate Database Entry records since the last rebuild are then written to the corresponding Aggregate Database Entry records.

Step 3: Create a New Auth. Provider Record in Salesforce

This step creates an Auth. Provider record in Salesforce. An authentication provider allows a user to log in to your Salesforce org using their login credentials from an external service provider. In this case, the external service provider is Google.

If you are a G Suite customer, you will need to create a Google Cloud Project for authentication. Follow the steps in this guide to create your own Google Cloud Project. If you are not a G Suite customer, we will create a G Suite user for you under the domain fullcircleinsightsdst.com and you will use our Google Cloud Project to authenticate. You will need to grant Google Analytics view access to this user, as we will use it for authentication. Make sure you've reviewed pre-implementation steps before using the instructions below.

Navigate to Setup | Administer | Security Controls | Auth. Providers | New.

1. At the Auth. Provider Edit window, choose "Open ID Connect" as the Provider Type.
   1. Additional fields appear once this option is selected.
2. Enter the following information into the following fields:
   1. Name: FCR_Google_OpenID_Provider
   2. URL Suffix: FCR_Google_OpenID_Provider (this should be auto-populated after you add in the Name)
   3. Consumer Key: Contact your Full Circle CSM for this information. Or use the one you have, if you have created your own internal Google Cloud Project.
   4. Consumer Secret: Contact your Full Circle CSM for this information. Or use the one you have, if you have created your own internal Google Cloud Project.
   5. Authorize Endpoint URL: https://accounts.google.com/o/oauth2/auth?access_type=offline&approval_prompt=force&include_granted_scopes=true
   6. Token Endpoint URL: https://www.googleapis.com/oauth2/v4/token
   7. User Info Endpoint URL: https://www.googleapis.com/oauth2/v2/userinfo
   8. Default Scopes: openid profile https://www.googleapis.com/auth/analytics.readonly
   9. Do not modify any other fields.
   10. Click Save when done.
3. The Auth. Provider Detail page appears for the Auth. Provider record you just created.
   1. Salesforce will have auto-populated fields in the Salesforce Configuration section of the page.
4. From the Salesforce Configuration section of the Auth. Provider Detail record, copy the information in the Callback URL field.
5. If you are not a G Suite customer and will use our Google Cloud Project for authentication, provide this Callback URL to your Full Circle CSM.

Step 4: Create Credentials in Google Cloud Platform Project

	Note: This step must be performed by the Full Circle CSM. If you have not yet coordinated with your CSM, please review our recommended pre-implementation considerations.

If you are a G Suite customer and using your own internal Google Cloud Project for authentication, follow these steps so it recognizes your Salesforce org. Make sure you have completed all steps in this guide to create a Google Cloud Project.

1. Open the Google Cloud Platform dashboard and go into the Google Cloud Project named Full Circle DST Connector.
2. From the Project's sidebar, go to Credentials. The Credentials page appears.
3. From the OAuth 2.0 client IDs section, click the Oauth ID with the Name of Full Circle DST. The Client ID for Web application page appears.
4. Confirm that the Client ID and Client Secret in this credential match the data in the Consumer Key and Consumer Secret fields in the Salesforce Auth. Provider record.
5. Find the Authorized redirect URIs section on this page.
6. Assuming the Callback URL you have has not yet been added as an Authorized redirect URI, scroll down to the end of this list of URIs. In the blank field, paste in the Callback URL. Click Save to save your entry.

If you are not a G Suite customer and will use Full Circle's Google Cloud Project, Full Circle must now update our system so it recognizes your Salesforce org, which will eventually authenticate with your Google Analytics instance.

Step 5: Update the Named Credential Record(s)

After the Full Circle CSM has authorized your Salesforce org's Auth. Credential's Callback URL, go to the Named Credential record to modify it and verify the Authentication Status. This will confirm that the Auth. Provider has been successfully authorized by the Google Cloud Project.

Navigate to Setup | Administer | Security Controls | Named Credentials.

The default Named Credential records that were shipped in the managed package have the Authentication Protocol field set to "No Authentication." This was done to allow these records to be included in the managed package.

If you are configuring DST to retrieve Google Analytics 4 data:

1. Click the name of the Named Credential provided by Full Circle: FCR_Google_Analytics_4_Credential. You arrive at the Named Credential detail page for this credential.
2. Click Edit and change the Authentication Protocol field to OAuth 2.0. At this time, more fields should appear.
3. In the Authentication Provider field, enter the name of the Auth. Provider record that you just created: FCR_Google_OpenID_Provider
4. In the Scope field, enter the same information as was in the Default Scopes field of the Auth. Provider record you created: openid profile https://www.googleapis.com/auth/analytics.readonly
5. In the Authentication section, look for the Authentication Status field. The status should be Pending.
6. If you are a G Suite customer and are using your own internal app for authentication, check the Start Authentication Flow on Save checkbox so that the field is checked.
7. Click Save. This starts the authentication process if you have checked the Start Authentication Flow on Save checkbox in the previous step.
   1. If you get a Google Error page, this means the authentication process was not able to start. Review the previous steps to confirm the correct data was added to noted fields.

If you are configuring DST to retrieve Universal Analytics data:

1. Click the name of the Named Credential provided by Full Circle: FCR_Google_Analytics_Credential. You arrive at the Named Credential detail page for this credential.
2. Click Edit and change the Authentication Protocol field to OAuth 2.0. At this time, more fields should appear.
3. In the Authentication Provider field, enter the name of the Auth. Provider record that you just created: FCR_Google_OpenID_Provider
4. In the Scope field, enter the same information as was in the Default Scopes field of the Auth. Provider record you created: openid profile https://www.googleapis.com/auth/analytics.readonly
5. In the Authentication section, look for the Authentication Status field. The status should be Pending.
6. If you are a G Suite customer and are using your own internal app for authentication, check the Start Authentication Flow on Save checkbox so that the field is checked.
7. Click Save. This starts the authentication process if you have checked the Start Authentication Flow on Save checkbox in the previous step.
   1. If you get a Google Error page, this means the authentication process was not able to start. Review the previous steps to confirm the correct data was added to noted fields.

Step 6: Commence Authentication

This process authenticates Google Analytics with Salesforce through your own Google Cloud Project or Full Circle's Google Cloud middleware.

If you are a G Suite customer and are using your own internal app for authentication, follow these steps to authenticate using your Google Analytics account:

1. A Sign in with Google > Choose an account to continue to salesforce.com page appears.
   1. It displays a Google account for you to choose, which enables you to authenticate with Salesforce.
   2. You also have an option to Use Another Account.
   3. This Google account must have access to your company's Google Analytics. Specifically, the Google account should have access to the same Google Analytics Property that has its Property ID captured in Step 1.
   4. NOTE: We strongly recommend using a Google account that is dedicated for integrations rather than a Google account that belongs to a particular employee. If that employee leaves the company and the Google account loses access, then the Google Analytics integration for Digital Source Tracker will stop working.
   5. If there is nobody in your organization that has both a Salesforce Administrator profile and has access to a Google account with at least Viewer access to the Google Analytics Property, then follow the instructions here.
2. Select the appropriate Google account.

If you are not a G Suite customer and will use Full Circle's Google Cloud Project, your CSM will authenticate with the user under the fullcircleinsightsdst.com domain that you have granted Google Analytics view access to.

Step 7: Approve Authentication Request

If you are a G Suite customer and are using your own internal app for authentication, a Sign in with Google > salesforce.com wants to access your Google Account page appears. Click Allow. The Named Credential record appears.

If you are not a G Suite customer and will use Full Circle's Google Cloud Project, your CSM will complete this step.

Step 8: Confirm Successful Authentication

Look at the Authentication Status field. The status should now display "Authenticated as of..." with some additional information.

If you are configuring DST to retrieve both Google Analytics 4 and Universal Analytics data, return to Step 5 and repeat with the Named Credential you have not configured yet.

Next Steps

Now that you have authenticated Google Analytics with your Salesforce org, proceed to the next section to set up your Full Circle Insights Response Management Funnel Metrics functionality to feed key information into Aggregate Database Entry records.

Data from Google Analytics will not yet be captured in Aggregate Database Entry records until the Daily Aggregate Database is enabled. If you are ready to enable the Daily Aggregate Database, complete the following steps:

1. Go to the Daily Aggregate Database Configuration page.
   • Navigate to Setup | Build | Installed Packages | Full Circle Response Management | Configure | Digital Source Tracker | Daily Aggregate Database Configuration.

2. Select Yes under Would you like to enable the Daily Aggregate Database?