Drupal Association members fund grants that make connections all over the world.
Updated: Comment #4
Google Analytics custom fields are defined in the Google Analytics Views module as a single field, using '(n)' to represent the variable part of the field. The module doesn't provide a mechanism for specifying which variation of the custom field you want to use. Therefore, if a custom field is used, the query will contain fields with this '(n)' place holder text which causes the query to fail.
The initial proposed solution was to manually specify all custom field variations. This is impractical as Google Analytics Premium accounts allow up to fifty variations of each custom field and there are currently 9 custom fields. This would add 450 fields to views while failing to account for the possiblity of new custom fields or more than fifty variations.
Instead of manually specifying all custom field variations, configuration forms should provide an integer text field allowing users to specify the variation to use.
- Review the latest patch
User interface changes
Adds a new integer text field to configuration forms of custom fields for specifying which variation to use.
Original report by q2_faith
ga:customVarValue(n) in fields, views don't show result.
In Query Explorer I wrote ga:customVarValue1 to get the result. How can I do in views(ga:customVarValue1 instead of ga:customVarValue(n))