Teak provides push notifications, emails, and universal links, all with optional built in incentivization, with event and profile based segmentation and targeting capabilities.
When syncing an audience, Teak will only match users that are already known in your Teak instance. In order for Teak to match users, you must have implemented the Teak and mParticle SDKs with a common user identifier and must ensure that the appropriate mParticle identity type is mapped to Teak’s Player ID Identity type as part of configuring the integration.
Teak will only match users that are already known in your Teak instance.
Setting Name | Data Type | Default Value | Description |
---|---|---|---|
Teak App ID | string |
Your Teak App ID, from the Settings for your app on the Teak dashboard | |
Teak App Secret | string |
Your Teak App Secret, from the Server tab of Settings for your app on the Teak dashboard | |
Player ID Identity Type | string |
Select which user identity to forward to Teak as your customer’s Player ID. |
Setting Name | Data Type | Default Value | Description |
---|---|---|---|
Configure User Attribute Forwarding | bool |
False | If enabled, you can configure user attributes to share for this audience connection. |
Was this page helpful?