Google Pub/Sub is Google’s enterprise low-latency messaging service that enables communication between independently written applications hosted on the Google Cloud Platform and externally.
To activate your Google Pub/Sub integration, you will need an active Google Service Account, plus the project ID and Topic name of your Pub/Sub project.
You must grant Pub/Sub Publisher access for your topic to
email@example.com. This allows mParticle to publish messages to your topic.
Google Pub/Sub accepts data from all platform types.
mParticle forwards the following identifiers to Google Pub/Sub, where available:
mParticle forwards the following event types to Google Pub/Sub:
|Setting Name||Data Type||Default Value||Platform||Description|
||All||Google Pub/Sub project name|
||All||Google Pub/Sub topic name|
||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 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.|
|Send Crash Events||
||True||All||If enabled, app crashes will be forwarded.|
|Send Custom Events||
||True||All||If enabled, custom app events will be forwarded.|
|Include User Identities||
||True||All||If enabled, user identity information will be forwarded with event batches.|
|Send Lifecycle Events||
||True||All||If enabled, lifecycle events (application start/stop, session start/end) will be forwarded.|
|Include Location Information||
||True||All||If enabled, location data will be forwarded with event data whenever possible.|
|Send Network Performance Events||
||True||All||If enabled, network performance events will be forwarded.|
|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 Push Registrations and Receipts||
||True||All||If enabled, push registration and receipt notifications will be forwarded.|
|Send Screen Views||
||True||All||If enabled, screen view events will be forwarded.|
|Send Commerce Events||
||True||All||If enabled, commerce events will be forwarded.|
||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?