[][src]Struct google_analyticsreporting4::Pivot

pub struct Pivot {
    pub metrics: Option<Vec<Metric>>,
    pub dimensions: Option<Vec<Dimension>>,
    pub max_group_count: Option<i32>,
    pub dimension_filter_clauses: Option<Vec<DimensionFilterClause>>,
    pub start_group: Option<i32>,
}

The Pivot describes the pivot section in the request. The Pivot helps rearrange the information in the table for certain reports by pivoting your data on a second dimension.

This type is not used in any activity, and only used as part of another schema.

Fields

metrics: Option<Vec<Metric>>

The pivot metrics. Pivot metrics are part of the restriction on total number of metrics allowed in the request.

dimensions: Option<Vec<Dimension>>

A list of dimensions to show as pivot columns. A Pivot can have a maximum of 4 dimensions. Pivot dimensions are part of the restriction on the total number of dimensions allowed in the request.

max_group_count: Option<i32>

Specifies the maximum number of groups to return. The default value is 10, also the maximum value is 1,000.

dimension_filter_clauses: Option<Vec<DimensionFilterClause>>

DimensionFilterClauses are logically combined with an AND operator: only data that is included by all these DimensionFilterClauses contributes to the values in this pivot region. Dimension filters can be used to restrict the columns shown in the pivot region. For example if you have ga:browser as the requested dimension in the pivot region, and you specify key filters to restrict ga:browser to only "IE" or "Firefox", then only those two browsers would show up as columns.

start_group: Option<i32>

If k metrics were requested, then the response will contain some data-dependent multiple of k columns in the report. E.g., if you pivoted on the dimension ga:browser then you'd get k columns for "Firefox", k columns for "IE", k columns for "Chrome", etc. The ordering of the groups of columns is determined by descending order of "total" for the first of the k values. Ties are broken by lexicographic ordering of the first pivot dimension, then lexicographic ordering of the second pivot dimension, and so on. E.g., if the totals for the first value for Firefox, IE, and Chrome were 8, 2, 8, respectively, the order of columns would be Chrome, Firefox, IE.

The following let you choose which of the groups of k columns are included in the response.

Trait Implementations

impl Clone for Pivot[src]

impl Debug for Pivot[src]

impl Default for Pivot[src]

impl<'de> Deserialize<'de> for Pivot[src]

impl Part for Pivot[src]

impl Serialize for Pivot[src]

Auto Trait Implementations

impl RefUnwindSafe for Pivot

impl Send for Pivot

impl Sync for Pivot

impl Unpin for Pivot

impl UnwindSafe for Pivot

Blanket Implementations

impl<T> Any for T where
    T: 'static + ?Sized
[src]

impl<T> Borrow<T> for T where
    T: ?Sized
[src]

impl<T> BorrowMut<T> for T where
    T: ?Sized
[src]

impl<T> DeserializeOwned for T where
    T: for<'de> Deserialize<'de>, 
[src]

impl<T> From<T> for T[src]

impl<T, U> Into<U> for T where
    U: From<T>, 
[src]

impl<T> ToOwned for T where
    T: Clone
[src]

type Owned = T

The resulting type after obtaining ownership.

impl<T, U> TryFrom<U> for T where
    U: Into<T>, 
[src]

type Error = Infallible

The type returned in the event of a conversion error.

impl<T, U> TryInto<U> for T where
    U: TryFrom<T>, 
[src]

type Error = <U as TryFrom<T>>::Error

The type returned in the event of a conversion error.

impl<T> Typeable for T where
    T: Any