Analytic Attribution

Personalization Builder analytics uses an unique identifier to attribute collected analytics to a specific user. By default, the SDK uses the contact key as this identifier, called the PIID. Your app can explicitly set this value.

The Mobile Push SDK has an optional configuration option called useLegacyPiIdentifier. This option replaces an absent or empty PIID with the MobilePush contact key. If this configuration option is false, the SDK doesn’t replace an absent or empty PIID. Review Configure the SDK to configure the SDK with pianalytics and useLegacyPiIdentifier.

Important: To ensure future compatibility, we recommend explicitly setting the PIID. The useLegacyPiIdentifier configuration option will be deprecated in a future release.

Example: Analytic Attribution

Integration Methods

These methods integrate your mobile app with Personalization Builder. To use the methods, you must have an existing Personalization Builder deployment, and you must enable the “pianalytics” option when you configure your SDK.

Track Cart

To track the contents of an in-app shopping cart, use the method shown in the example. For more information about this method’s general use with Personalization Builder, review Track Items in Shopping Cart.

Track Conversion

To track a purchase made through your mobile app, use the method shown in the example. For more information about this method’s general use with Personalization Builder, review Track Purchase Details.

Track Page Views

To implement page-view analytics in your app, use the method shown in the example. For more information about this method’s general use with Personalization Builder, review Track Items Viewed.

  • MarketingCloudSDK+Intelligence.h