Skip to content

2.5.2

Latest

Choose a tag to compare

@pequots34 pequots34 released this 20 Nov 00:26
996b327

Recognizer SDK (2.5.2)

  • Supports Activation SDK 1.3.2, which reports screen views and taps using the same events as the iOS SDK, so shoppers in apps built on the Activation SDK are now counted in publisher reports. There is no API change: hosts using activations update their com.actualplatform:activation dependency to 1.3.2 and recompile. See Activation SDK 1.3.2 for Android below.
  • Stability fixes and improvements

Account Linking SDK (2.5.2)

  • Stability fixes and improvements

Camera SDK (2.5.2)

  • Stability fixes and improvements

Camera UI SDK (2.5.2)

  • Stability fixes and improvements

Core SDK (2.5.2)

  • Stability fixes and improvements

Digital SDK (2.5.2)

  • Stability fixes and improvements

Digital Analytics SDK (2.5.2)

  • Stability fixes and improvements

Earnings SDK (2.5.2)

  • Stability fixes and improvements

Logcat SDK (2.5.2)

  • Stability fixes and improvements

Security SDK (2.5.2)

  • Stability fixes and improvements

Surveys SDK (2.5.2)

  • Stability fixes and improvements

Activation SDK 1.3.2 for Android

This update brings the SDK's analytics in line with the native iOS SDK. Apps built on the Activation SDK now send the same screen-view and tap events, so their shoppers are counted in your publisher reports: offer wall visits, screen views, clips by screen, and offer wall to scan conversion. Previously these shoppers were missing from those reports. There are no API changes.

dependencies {
    implementation(platform("com.actualplatform:activation-bom:1.3.2"))
    implementation("com.actualplatform:activation")
}

Upgrade Notes

  • No code changes are required. This release adds no public API and changes none. As with every release, your integration must be recompiled against 1.3.2.

The compile target is unchanged from 1.3.1: compileSdk 37 or higher is still required, your app's targetSdk does not need to change, and no new dependencies are introduced. The matching Receipts SDK release is 2.5.2.

What's New & Improved

  • Screen view reporting. The SDK reports a screen view when a shopper opens any of these screens:

    • the offer wall, an offer group, and a store's offer list
    • offer details
    • the stores sheet
    • the Receipt Summary
    • the receipt error screens: submission limit reached, upload failed, invalid receipt, receipt too old, and missing fields

    A view is sent once each time a screen opens. Returning to a screen that is already open, such as after closing a sheet on top of it, sends nothing. Views of the Receipt Summary and the receipt error screens carry the receipt's blink_receipt_id, so they can be tied back to the scan.

  • Tap reporting. The SDK reports taps on offer cards, the clip button, the Scan Receipt button, store tiles, the "more stores" tile, and the "show more" button. Each tap records the screen it happened on and, where it applies, the offer or store tapped and its position in the list. This is what powers clips-by-screen and offer wall to scan conversion.

  • Same event names as the native iOS SDK. Screen views and taps use the iOS SDK's event types and field names, so they feed the same reports. To tell the two apart, every event the SDK sends, including existing ones such as ad_request, now carries platform (android or ios) and product (activation-android-kmp or activation-ios-kmp).

  • Reporting never gets in the shopper's way. Events are sent in the background, in the order they happened. A send that fails is dropped without affecting the shopper. An event is only ever sent under the session and user it happened in, so events still pending after an identity change or ActivationClient.close() are dropped rather than attributed to the next user.

Bug Fixes

None.