You won’t be able to see data flow from your input (iOS) to your output (webhooks) until you connect them.
|The connection status must be active to forward data to an output.
|Metadata Field Exclusion
|Click the X to remove.
|This setting allows you to exclude a specific metadata field from the data you send to your output.
|Send as Batch
|If enabled, the SDK will not forward data in realtime.
|Send Custom Events
|Custom events include any events defined manually using the SDK.
|Send Lifecycle Events
|Lifecycle events include events created when a user starts or exits your app.
|Send Screen Views
|Screen view events include events created when a user opens or navigates to a different page in your app.
|Send Commerce Events
|Commerce events include events created when a user adds an item to their cart or when a user makes a purchase.
|Metadata includes information about the application or users’ devices.
|Include User Identity Change Events
|User identity change events include events created when a user logs into or out of your app.
You should now see the complete connection between your iOS input and your webhooks output diagrammed on the Connections page.
Remember that connections in mParticle consist of an input (a data source) and an output (a destination where mParticle sends data). In the connection we just created, The Higgs Shop iOS app is the input and the webhook is the output.
Connection modes determine whether data collected from the input is sent directly to the output, or if it is sent to mParticle’s servers first before it’s forwarded to the output.
Was this page helpful?