Configuring Google DFA Accounts (Deprecated)

On this page

This account is used by the Snaps in the Google DFA Snap Pack.

Creating an Account

You can create an account from Designer or Manager. In Designer, when working on pipelines, every Snap that needs an account prompts you to create a new account or use an existing account. The accounts can be created in or used from:

  • Your private project folder: This folder contains the pipelines that will use the account.
  • Your Project Space’s shared folder: This folder is accessible to all the users that belong to the Project Space.
  • The global shared folder: This folder is accessible to all the users within an organization in the SnapLogic instance.

Account Configuration

In Manager, you can navigate to the required folder and create an account in it (see Accounts). To create an account for DFA (Google) OAuth2:

  1. Click Create, then select DFA > Google DFA OAuth2.
  2. Supply an account label.
  3. Click the Authorize bar. You will be asked to login into a Google account. Log in with user credentials. After successfully logging in, the user will be asked to provide few steps for permissions. The user has to allow permissions to make a connection.
  4. (Optional) Supply additional information on this account in the Notes field of the Info tab.
  5. Click Apply

Account Types

GoogleDFA OAuth2

 Account Settings

Label


Required. User provided label for the account instance

Access token


Required. The access token for the application. The retrieval of the access token is done when setting up the account for the endpoint. There, the OAuth2 flow will be executed and the resulting access token will be stored in this property. The access token might be refreshable, in that case an optional refresh token can be stored. The user must get a new access token if the access token has expired and no refresh token was defined or both the access and the refresh token have expired.


Refresh token

The refresh token for the application. The retrieval of the refresh token is done when setting up the account for the endpoint. There, the OAuth2 flow will be executed and the resulting refresh token can be stored in this property. If the refresh token is stored, then the access token can be refreshed automatically before it expires.


Access token expiration

The access token expiration value.


OAuth2 Endpoint


Required. Authorization endpoint to authorize the application.

Default valuehttps://accounts.google.com/o/oauth2/auth


OAuth2 Token


Required. Token endpoint to get the access token.

Default valuehttps://accounts.google.com/o/oauth2/token


Auth endpoint config

Provides custom properties for the OAuth2 auth endpoint.


Access type

The access type for the token, if offline, then it will be persisted in the account
Default value: offline


Approval prompt

The approval type for the token.

Default value: force


Application scope

The scope for the applications execution. As an example, the Snap could define that only a read of data by the application should be allowed.

Default valuehttps://www.googleapis.com/auth/dfareporting


Refresh

Refresh access token. Available after the account has been saved.


Auto-refresh token

Refreshes the token automatically using the refresh token if the property is enabled. Otherwise the token might expire and will not be automatically refreshed.


Authorize

Starts the OAuth authorization flow. Account will be saved before authorize. 


Account Encryption

Standard Encryption

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.


Enhanced Encryption

If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account.

Account:

  • High: Access token
  • Medium + High: Access token
  • Low + Medium + High: Access token, refresh token 

GoogleDFA Dynamic OAuth2

 Account Settings

Label


Required. User provided label for the account instance

Access token


Required. The access token for the application. The provided token will be passed as 'Authorization: bearer <access_token_value> to the Snap if 'Header authenticated' property is enabled. Some endpoints require an uppercase letter for Bearer, then the property value for the token must be provided as 'Bearer <access_token_value>' for the access token property value. The access token is not refreshable, but can be passed as a pipeline parameter.

Account Encryption

Standard Encryption

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.


Enhanced Encryption

If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account.

Account:

  • High: Access token
  • Medium + High: Access token
  • Low + Medium + High: Access token



See Also

Snap Pack History

 Click to view/expand

4.23 (main7430)

  • Starting from 4.23 GA, we are retiring the Google DFA Snap Pack from the Snaps Catalog.

4.22 (main6403)

  • No updates made.

4.21 (snapsmrc542)

  • No updates made.

4.20 (snapsmrc535)

  • No updates made.

4.19 (snaprsmrc528)

  • No updates made.

4.18 (snapsmrc523)

  • No updates made.

4.17 Patch ALL7402

  • Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.

4.17 (snapsmrc515)

  • Added the Snap Execution field to all Standard-mode Snaps. In some Snaps, this field replaces the existing Execute during preview check box.

4.16 (snapsmrc508)

  • No updates made. Automatic rebuild with a platform release.

4.15 (snapsmrc500)

  • No updates made. Automatic rebuild with a platform release.

4.14 (snapsmrc490) 

  • No updates made. Automatic rebuild with a platform release.

4.13 (snapsmrc486) 

  • No updates made. Automatic rebuild with a platform release.

4.12 (snapsmrc480)

  • No updates made. Automatic rebuild with a platform release.

4.11 [snapsmrc465]

  • No updates made. Automatic rebuild with a platform release.

4.10 (snapsmrc414)

  • No updates made. Automatic rebuild with a platform release.

4.9 (snapsmrc405)

  • No updates made. Automatic rebuild with a platform release.

4.8 (snapsmrc398)

  • No updates made. Automatic rebuild with a platform release.

4.7 (snapsmrc382)

  • No updates made. Automatic rebuild with a platform release.

4.6 (rcmsf233)

  • No updates made. Automatic rebuild with a platform release.

4.5.1 (dfa1578)

  • Updated tooltips and error messages to reflect current API version.

4.5 (rcmsf231)

  • Enabled suggestions for user profile name and campaign ID fields in Google DFA Reports Snap.

June 30, 2014

  • The Google DFA Reports Snap was enhanced to support expressions in the Metrics and Dimensions.
  • Addressed an issue with not being able to get Results with Valid Metrics and Dimensions in Google DFA Reports Snap.

March 2014

  • Introduced Google DFA Reports Snap.