You won’t be able to see data flow from your input (Android) to your output (webhooks) until you connect them.
|Connection Setting||Recommended Setting||Description|
|Connection Status||Active||You must toggle thi switch to Active for data to be forwarded to your webhook.|
|Metadata Field Exclusion||Click the X to remove.||This setting allows you to exclude a specific metadata field from that data you send to your output.|
|Send as Batch||Disabled||This is checked by default. Since we want to see our data forwarded as soon as possible, uncheck this so that events are forwarded in real time.|
|Send Custom Events||Check||The Higgs Shop does use custom events, so to ensure these are sent to our webhooks this must be enabled.|
|Send Lifecycle Events||Check||Lifecycle events include events when a user starts or exits your app.|
|Send Screen Views||Check||We do want to forward screenview events from The Higgs Shop.|
|Send Commerce Events||Check||The Higgs Shop is an ecommerce app, so we want to forward commerce events like product purchases.|
|Include Metadata||Check||Metadata includes information about the application or users’ devices.|
|Include User Identity Change Events||Check||We want to track events when the user identity changes.|
You should now see the complete connection between your Android input and your webhooks output diagramed on the Connections page.
Remember that connections in mParticle consist of an input (a data source) and an output (an integration where data is forwarded). In the connection we just created, The Higgs Shop Android app is our input and the webhook is our output.
The connection mode determines whether data collected from the input will be sent directly to the output, or if it will be sent to mParticle’s servers first before being forwarded to the output.
Since our connection is sending data from The Higgs Shop to mParticle’s servers before forwarding it to our webhook, we are using a server-to-server connection mode.
Was this page helpful?