Google Analytics Connector > Mappings and mapping tasks with Google Analytics > Google Analytics sources in mappings
  

Google Analytics sources in mappings

To read data from Google Analytics, configure a Google Analytics report as the Source transformation in a mapping.
Specify the name and description of the Google Analytics source. Select a Google Analytics report from the ga dataset in the Package Explorer. Configure the query options and advanced properties for the source object.
The following table describes the source properties that you can configure for a Google Analytics source:
Property
Description
Connection
Name of the Google Analytics source connection.
Source Type
Type of the source object. Select Single Object or Parameter.
Object
Name of the source object. Select a Google Analytics report from the ga dataset or select the InfaCustomGroup from the InfaCustom dataset in the Package Explorer.
The InfaCustomGroup report contains dimensions and metrics from all the Google Analytics reports.
The following table describes the query options that you can configure in a Source transformation:
Property
Description
Filter
Filter value in a read operation. Click Configure to add conditions to filter records and reduce the number of rows that the Secure Agent reads from the source.
You can specify the following filter conditions:
  • - Not parameterized. Use a basic filter to specify the object, field, operator, and value to select specific records.
  • - Completely parameterized. Use a parameter to represent the field mapping.
  • - Advanced. Use an advanced filter to define a more complex filter condition on a dimension or metric. Specify the advanced filter expression using the following filter syntax:
    • ga:name<Operator>Expression
    Where, name is the name of the dimension or metric, Operator is the operator supported by the dimension or metric, and Expression is the value that you specify.
    For example, ga:browser==Firefox
    For more information about configuring advanced filters, click the following URL:
    https://developers.google.com/analytics/devguides/reporting/core/v3/reference#filters
Sort
Not applicable for Google Analytics Connector.
The following table describes the advanced properties that you can configure for a Google Analytics source:
Property
Description
AccountId
Not applicable for Google Analytics Connector.
PropertyId
The Google Analytics Property ID associated with the Google Analytics project.
You can override the PropertyId connection property at runtime.
ViewId
Not applicable for Google Analytics Connector.
StartDate
Start date from which the Secure Agent must read the data from a Google Analytics report.
You can specify a specific date using the YYYY-MM-DD format. You can also specify relative terms such as today, yesterday, or NdaysAgo.
You can specify multiple dates separated by a comma to filter the data in a Google Analytics report.
EndDate
End date till which the Secure Agent must read the data from a Google Analytics report.
You can specify a specific date using the YYYY-MM-DD format. You can also specify relative terms such as today, yesterday, or NdaysAgo.
You can specify multiple dates separated by a comma to filter the data in a Google Analytics report.
Page Size
Number of rows that the Secure Agent must read from a Google Analytics report.
Specify 0 to read all the rows in the Google Analytics report.
Default is 0 and the maximum value is 2,147,483,647.
Read Time Out Value
Not applicable for Google Analytics Connector.
You can set the tracing level in the advanced session properties to determine the amount of details that logs contain.
The following table describes the tracing levels that you can configure:
Property
Description
Terse
The Secure Agent logs initialization information, error messages, and notification of rejected data.
Normal
The Secure Agent logs initialization and status information, errors encountered, and skipped rows due to transformation row errors. Summarizes session results, but not at the level of individual rows.
Verbose Initialization
In addition to normal tracing, the Secure Agent logs additional initialization details, names of index and data files used, and detailed transformation statistics.
Verbose Data
In addition to verbose initialization tracing, the Secure Agent logs each row that passes into the mapping. Also notes where the Secure Agent truncates string data to fit the precision of a column and provides detailed transformation statistics.
When you configure the tracing level to verbose data, the Secure Agent writes row data for all rows in a block when it processes a transformation.