Using Components: Google Analytics Source

Use the Google Analytics source component to define the Google Analytics reporting source, and which fields will be used in the package.

To define the Google Analytics source:

  1. Add a Google Analytics source component to begin your dataflow.
  2. Open the component and name it.

source settings

Define the source settings parameters. You can see further definition and example of the parameters on the Query Explorer site.
  • analytics connection - either click the dropdown arrow and select an existing connection, or click create new to create a new connection (see Defining connections).
  • profile ids - The ids of your Google Analytics profiles (or tables) in the form of ga:xxx. You can enter multiple ids separated by comma. Use the Account Explorer tool to get a list of the profiles you have access to. 
  • dimensions (optional) - Select dimensions from the dropdown list of dimensions.
  • metrics - Select metrics from the dropdown list of metrics.
  • segment (optional) - Select a segment from the dropdown list of segments or write your own.
  • filters (optional) - Enter a filter to retrieve a subset of the data.
  • sort (optional) - Enter the sort order and sort field.
  • date range - Enter the Start date and End date to filter the data. Click on each date and select the date from the calendar. You can also use variables as values for the custom date range in the format yyyy-MM-dd.
  • sampling level - Set the sampling level for the query. See the Google Analytics sampling section for more details.
  • include empty rows - if unchecked, records where all metric values are zero will be omitted.
  • profile id field name - Modify the name that will appear as the field for profile ID.
  • account name field name - Modify the name that will appear as the field for account name.
  • property name field name - Modify the name that will appear as the field for property name.
  • profile name field name - Modify the name that will appear as the field for profile name.

Then click the Test Connection button to help check that the connection is good and that the profile ids exist.

report fields mapping

After defining the dimension and metrics source settings, the field names and data types will be populated. You can make these modifications to the list of fields:

  • Define how you will refer to these fields (alias) in the other components of your package. If you use illegal characters, we'll let you know before you close the dialog.
  • Remove report fields from the list.
data preview

Click the Show data preview button to preview the analytics data for your source settings.

Note: Google analytics allows a maximum of 7 dimensions and 10 metrics in any one API request. A workaround could be to use several Google Analytics source components with the same dimensions and different metrics and then join them on the profile id and dimensions.

Creating packages

  1. Creating a new package
  2. Create a package from a template
  3. Working in the package designer
  4. Using Components: Facebook Ads Insights Source (Beta)
  5. Using components: File Storage Source
  6. Using components: Database Source
  7. Using components: Google AdWords Source
  8. Using components: NetSuite Source
  9. Using Components: Google Analytics Source
  10. Using Components: Google BigQuery Source
  11. Using components: Google Cloud Spanner Source
  12. Using Components: Bing Ads Source
  13. Using components: MongoDB Source
  14. Using components: Amazon Redshift Source
  15. Using Components: Rest API Source
  16. Using Components: Salesforce Source
  17. Using components: Select
  18. Using components: Sort
  19. Using components: Rank
  20. Using components: Limit
  21. Using components: Sample
  22. Using components: Join
  23. Using components: Cross Join
  24. Using components: Clone
  25. Using components: Cube and Rollup
  26. Using components: Union
  27. Using components: Filter
  28. Using Components: Window
  29. Using components: Assert
  30. Using components: Aggregate
  31. Using components: Distinct
  32. Using components: File Storage Destination
  33. Using components: Amazon Redshift Destination
  34. Using Components: Salesforce Destination (Beta)
  35. Using components: Google BigQuery Destination
  36. Using components: Google Cloud Spanner Destination
  37. Using components: Database Destination
  38. Using components: MongoDB Destination
  39. Using and setting variables in your packages
  40. Validating a package
  41. Using pattern-matching in source component paths
  42. Using ISO 8601 string functions
  43. Using Expressions in Xplenty
  44. Xplenty Functions

Feedback and Knowledge Base