Skip to content

feat(tracking): send gift_package on purchase - #17

Merged
Xyzcancer merged 4 commits into
masterfrom
DEV-T-691-purchase-gift-package
Sep 3, 2026
Merged

Xyzcancer merged 4 commits into
masterfrom
DEV-T-691-purchase-gift-package

Conversation

@Xyzcancer

Copy link
Copy Markdown
Contributor

Summary

  • Moved to the released natives: Android v2.38.0, iOS REES46 3.33.0.
  • Added isGiftPackage on tracking.purchase (and the deprecated trackPurchase), sent as gift_package only when true.
  • The Android bridge no longer hand-rolls the purchase payload — the plugin builds a PurchaseTrackingRequest and calls sdk.tracking.purchase, dropping ~290 lines of duplicated serialization and validation. With it, the stored setSource attribution and popups carried by the purchase response now reach purchases.

Android v2.37.0 -> v2.38.0, iOS 3.31.0 -> 3.33.0.
DEV-T-691. `isGiftPackage` on `tracking.purchase` (and the deprecated
`trackPurchase`) reaches the wire as `gift_package` only when true, the way
`tax_free` does. Android builds the payload in the bridge, iOS hands the flag to
the native request.
The Android bridge hand-rolled the purchase JSON — wire keys, validation and the
reserved-`custom` list — and posted it through the deprecated `SDK.sendAsync`,
because published artifacts once had no public `trackPurchase`. They do now, so
the plugin builds a `PurchaseTrackingRequest` and calls `sdk.tracking.purchase`
the way every other event already goes through the namespace, and 290 lines of
duplicated serialization are gone.

Two gaps close with it: the stored attribution from `setSource` now reaches
purchases, and a popup carried by the purchase response is handled.
@Xyzcancer
Xyzcancer merged commit 7e19fe5 into master Sep 3, 2026
2 of 3 checks passed
@Xyzcancer
Xyzcancer deleted the DEV-T-691-purchase-gift-package branch September 3, 2026 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant