Google Cloud Storage provides a file storage web service for developers and enterprises that combines the performance and scalability of Google’s cloud with geo-redundancy, advanced security and sharing capabilities.
To activate your Google Cloud Storage integration, you will need an active Google Service Account.
Create a Bucket in your account to store your mParticle data and grant
Storage Object Creator to
firstname.lastname@example.org. This allows mParticle to create files in your bucket.
Optionally, you can create a folder in your bucket to store your mParticle data. This is useful if you are storing other data in the same bucket, or if you want to separate dev and production data without creating two buckets. If you want to store your data in a folder, you must provide the name of the folder in the Connection Settings dialog.
Google Cloud Storage accepts data from all platform types. All event types are supported. By default all available data will be forwarded, but you can pick and choose which events and attributes to send in the Connection Settings dialog.
|Setting Name||Data Type||Default Value||Platform||Description|
|Storage Bucket Name||
||All||The name of the storage bucket to which mParticle will forward event data.|
||All||An optional name of a folder in the storage bucket in which to store event data.|
||All||An optional string identifier for your app that will be forwarded with each event batch. Standard app identifiers (Apple OS Bundle ID, Android Package Name) will be forwarded regardless of this setting.|
|Send Lifecycle Events||
||True||All||If enabled, lifecycle events (application start/stop, session start/end) will be forwarded.|
|Send Screen Views||
||True||All||If enabled, screen view events will be forwarded.|
|Send Crash Events||
||True||All||If enabled, app crashes will be forwarded.|
|Send Network Performance Events||
||True||All||If enabled, network performance events will be forwarded.|
|Send Custom Events||
||True||All||If enabled, custom app events will be forwarded.|
|Send Push Registrations and Receipts||
||True||All||If enabled, push registration and receipt notifications will be forwarded.|
|Send as Batch||
||True||All||If enabled, this setting will cause your app’s events to be sent in (roughly) 10-minute batches per device. If disabled, mParticle will POST each event to you individually, as its received. This setting is ignored if “Wait for Complete Batch” is enabled.|
|Wait for Complete Batch||
||False||All||If enabled, mParticle will POST events to you in batches only after a user session has ended, so that each event batch you receive will represent a full session of user activity within your app.|
|Include Location Information||
||True||All||If enabled, location data will be forwarded with event data whenever possible.|
|Include User Identities||
||True||All||If enabled, user identity information will be forwarded with event batches.|
|Send Profile Change Events||
||True||All||If enabled, mParticle will forward ID profile events, such as user sign ups, logins logouts, updates, and deletes.|
|Send Commerce Events||
||True||All||If enabled, commerce events will be forwarded.|
|Store Data In Folders By Date (deprecated)||
||False||All||If enabled, data will be stored in a folder by date.|
|Store Data In Folders By Date||
||UNSELECTED||All||If enabled, your data will be stored in a cloud folder according to the chosen method.|
||False||All||If enabled, data will be compressed in gzip format.|
||True||All||If enabled, the following metadata - application_info, device_info and source_info will be forwarded.|
|Include User Attribute Change Events||
||False||All||If enabled, User Attribute Change Events will be forwarded.|
|Include User Identity Change Events||
||False||All||If enabled, User Identity Change Events will be forwarded.|
Was this page helpful?