Release 0.1.0

What's New in 0.1.0

• User Identification — tie subscribers to your own user records

  Associate a subscription with first-party identity fields (and clear them on sign-out) so campaigns and segments can be personalized from your own data.

  • identify(JSONObject fields) / identify(JSONObject fields, PushEngageResponseCallback callback) — upsert subscriber fields. Valid keys are restricted to the predefined set: first_name,
    last_name, email, phone, gender, dob, language, profile_id, country, city, state, zip. Values must be String, Number, or Boolean. If every requested field already matches the locally
    cached value, the call short-circuits with no network request.
  • logout(List fieldNames) / logout(List fieldNames, PushEngageResponseCallback callback) — remove identifying fields while keeping the device subscribed for push. Passing
    null or an empty list clears the default PII set (first_name, last_name, email, phone, gender, dob, profile_id); pass an explicit list to scope the removal.

• Custom Event Tracking — drive triggered campaigns from in-app actions

  • trackEvent(TrackEvent event) / trackEvent(TrackEvent event, PushEngageResponseCallback callback) — send a custom event for the current subscriber. Custom events are used to trigger or
    exit workflows based on subscriber activity in your app, such as adding items to a cart, completing a purchase, or any custom action you define.

• Notification Customization

  • setBadgeCount(int count) — control the numeric badge displayed alongside notifications the SDK builds. Pass 0 to clear, a positive integer to set. Applied via
    NotificationCompat.Builder.setNumber(count); surfaces in the system long-press menu. Negative values are coerced to 0.

• Diagnostics

  • setFcmConfigErrorListener(FcmConfigErrorListener listener) — register a callback that fires when the SDK detects a mismatch between your app's local Firebase configuration and the
    configuration registered for your PushEngage site. Use this during integration to catch sender-ID or project-ID drift early — when a mismatch is detected at sync time, the SDK also skips
    the subscribe call so a permanently-undeliverable subscriber is not created on the server. Pass null to clear a previously-registered listener.