Data Subject Request API Version 1 and 2
Data Subject Request API Version 3
Key Management
Platform API Overview
Accounts
Apps
Audiences
Calculated Attributes
Data Points
Feeds
Field Transformations
Services
Users
Workspaces
Warehouse Sync API Overview
Warehouse Sync API Tutorial
Warehouse Sync API Reference
Data Mapping
Warehouse Sync SQL Reference
Warehouse Sync Troubleshooting Guide
ComposeID
Warehouse Sync API v2 Migration
Audit Logs API
Bulk Profile Deletion API Reference
Calculated Attributes Seeding API
Custom Access Roles API
Household Reach API Reference
Data Planning API
Pixel Service
Profile API
Events API
mParticle JSON Schema Reference
IDSync
AMP SDK
Initialization
Configuration
Network Security Configuration
Event Tracking
User Attributes
IDSync
Screen Events
Commerce Events
Location Tracking
Media
Kits
Application State and Session Management
Data Privacy Controls
Error Tracking
Opt Out
Push Notifications
WebView Integration
Logger
Preventing Blocked HTTP Traffic with CNAME
Workspace Switching
Linting Data Plans
Troubleshooting the Android SDK
API Reference
Upgrade to Version 5
Upgrade to Version 6
Cordova Plugin
Identity
Direct URL Routing FAQ
Web
Android
iOS
Workspace Switching
Initialization
Configuration
Event Tracking
User Attributes
IDSync
Screen Tracking
Commerce Events
Location Tracking
Media
Kits
Application State and Session Management
Data Privacy Controls
Error Tracking
Opt Out
Push Notifications
Webview Integration
Upload Frequency
Preventing Blocked HTTP Traffic with CNAME
Linting Data Plans
Troubleshooting iOS SDK
Social Networks
iOS 14 Guide
iOS 15 FAQ
iOS 16 FAQ
iOS 17 FAQ
iOS 18 FAQ
API Reference
Upgrade to Version 7
Upgrade to Version 9
Getting Started
Identity
Getting Started
Identity
Upload Frequency
Getting Started
Opt Out
Initialize the SDK
Event Tracking
Commerce Tracking
Error Tracking
Screen Tracking
Identity
Location Tracking
Session Management
Initialization
Configuration
Content Security Policy
Event Tracking
User Attributes
IDSync
Page View Tracking
Commerce Events
Location Tracking
Media
Kits
Application State and Session Management
Data Privacy Controls
Error Tracking
Opt Out
Custom Logger
Persistence
Native Web Views
Self-Hosting
Multiple Instances
Web SDK via Google Tag Manager
Preventing Blocked HTTP Traffic with CNAME
Facebook Instant Articles
Troubleshooting the Web SDK
Browser Compatibility
Linting Data Plans
API Reference
Upgrade to Version 2 of the SDK
Alexa
Overview
Step 1. Create an input
Step 2. Verify your input
Step 3. Set up your output
Step 4. Create a connection
Step 5. Verify your connection
Step 6. Track events
Step 7. Track user data
Step 8. Create a data plan
Step 9. Test your local app
Overview
Step 1. Create an input
Step 2. Verify your input
Step 3. Set up your output
Step 4. Create a connection
Step 5. Verify your connection
Step 6. Track events
Step 7. Track user data
Step 8. Create a data plan
Step 1. Create an input
Step 2. Create an output
Step 3. Verify output
Node SDK
Go SDK
Python SDK
Ruby SDK
Java SDK
Introduction
Outbound Integrations
Firehose Java SDK
Inbound Integrations
Compose ID
Glossary
Data Hosting Locations
Migrate from Segment to mParticle
Migrate from Segment to Client-side mParticle
Migrate from Segment to Server-side mParticle
Segment-to-mParticle Migration Reference
Rules Developer Guide
The Developer's Guided Journey to mParticle
API Credential Management
Composable Audiences Overview
User Guide Overview
Warehouse Setup Overview
Audience Setup
Frequently Asked Questions
Overview
Overview
User Profiles
Household Reach
Calculated Attributes Overview
Using Calculated Attributes
Create with AI Assistance
Calculated Attributes Reference
Predictions Overview
What's Changed in the New Predictions UI
View and Manage Predictions
Future Behavior Predictions Overview
Create Future Behavior Prediction
Manage Future Behavior Predictions
Create an Audience with Future Behavior Predictions
Identity Dashboard
Identity Logs
Create an Input
Start capturing data
Connect an Event Output
Create an Audience
Connect an Audience Output
Transform and Enhance Your Data
Usage and Billing Report
The new mParticle Experience
The Overview Map
Observability Overview
Observability User Guide
Observability Troubleshooting Examples
Observability Span Glossary
Audit Logs
Key Management
Platform Configuration
Event Forwarding
Event Match Quality Dashboard
Notifications
System Alerts
Trends
Introduction
Data Retention
Data Catalog
Connections
Activity
Data Plans
Live Stream
Filters
Consent Filters
Rules
Blocked Data Backfill Guide
Tiered Events
mParticle Users and Roles
Analytics Free Trial
Troubleshooting mParticle
Usage metering for value-based pricing (VBP)
IDSync Overview
Use Cases for IDSync
Components of IDSync
Store and Organize User Data
Identify Users
Default IDSync Configuration
Profile Conversion Strategy
Profile Link Strategy
Profile Isolation Strategy
Best Match Strategy
Aliasing
Audiences Overview
Create an Audience
Connect an Audience
Manage Audiences
Audience Insights
Audience Sharing
Match Boost
Inclusive & Exclusive Audiences Overview
Using Logic Blocks in Audiences
Combining Inclusive and Exclusive Audiences
Inclusive & Exclusive Audiences FAQ
Audience Expansion
Audience Agent Overview
Building Audiences with the Agent
Data and Privacy
Predictive Audiences Overview
Using Predictive Audiences
Introduction
Core Analytics (Beta)
Sync and Activate Analytics User Segments in mParticle
User Segment Activation
Welcome Page Announcements
Project Settings
Roles and Teammates
Organization Settings
Global Project Filters
Portfolio Analytics
Analytics Data Manager Overview
Events
Event Properties
User Properties
Revenue Mapping
Export Data
UTM Guide
Analyses Introduction
Getting Started
Visualization Options
For Clauses
Date Range and Time Settings
Calculator
Numerical Settings
Assisted Analysis
Properties Explorer
Frequency in Segmentation
Trends in Segmentation
Did [not] Perform Clauses
Cumulative vs. Non-Cumulative Analysis in Segmentation
Total Count of vs. Users Who Performed
Save Your Segmentation Analysis
Export Results in Segmentation
Explore Users from Segmentation
Getting Started with Funnels
Group By Settings
Conversion Window
Tracking Properties
Date Range and Time Settings
Visualization Options
Interpreting a Funnel Analysis
Group By
Filters
Conversion over Time
Conversion Order
Trends
Funnel Direction
Multi-path Funnels
Analyze as Cohort from Funnel
Save a Funnel Analysis
Explore Users from a Funnel
Export Results from a Funnel
Saved Analyses
Manage Analyses in Dashboards
Data Dictionary
Query Builder Overview
Modify Filters With And/Or Clauses
Query-time Sampling
Query Notes
Filter Where Clauses
Event vs. User Properties
Group By Clauses
Annotations
Cross-tool Compatibility
Apply All for Filter Where Clauses
Date Range and Time Settings Overview
User Attributes at Event Time
Understanding the Screen View Event
User Aliasing
Dashboards––Getting Started
Manage Dashboards
Dashboard Filters
Organize Dashboards
Scheduled Reports
Favorites
Time and Interval Settings in Dashboards
Query Notes in Dashboards
The Demo Environment
Keyboard Shortcuts
User Segments
Data Privacy Controls
Data Subject Requests
Default Service Limits
Feeds
Import Data with CSV Files
CSV File Reference
SFTP Credentials
Glossary
Video Index
Single Sign-On (SSO)
Setup Examples
Introduction
Introduction
Introduction
Rudderstack
Google Tag Manager
Segment
Advanced Data Warehouse Settings
AWS Kinesis (Snowplow)
AWS Redshift (Define Your Own Schema)
AWS S3 (Snowplow Schema)
AWS S3 Integration (Define Your Own Schema)
BigQuery (Snowplow Schema)
BigQuery Firebase Schema
BigQuery (Define Your Own Schema)
GCP BigQuery Export
Snowflake (Snowplow Schema)
Snowplow Schema Overview
Snowflake (Define Your Own Schema)
Aliasing
Event
Audience
Audience
Feed
Event
Audience
Cookie Sync
Platform SDK Events
Server-to-Server Events
Audience
Audience
Event
Audience
Feed
Event
Event
Event
Data Warehouse
Event
Audience
Event
Event
Feed
Event
Event
Event
Event
Event
Audience
Feed
Event
Event
Audience
Event
Event
Feed
Event
Event
Event
Custom Feed
Event
Data Warehouse
Event
Audience
Audience
Audience
Event
Audience
Event
Event
Event
Event
Event
Audience
Event
Audience
Event
Event
Data Warehouse
Audience
Event
Event
Audience
Cookie Sync
Event
Event
Event
Event
Feed
Feed
Event
Kit
Event
Event
Audience
Event
Event
Audience
Event
Event
Feed
Event
Audience
Audience
Event
Event
Audience
Event
Audience
Audience
Microsoft Ads Audience Integration
Event
Audience
Audience
Event
Event
Event
Event
Feed
Event
Event
Event
Event
Event
Event
Feed
Audience
Event
Event
Event
Event
Event
Event
Feed
Event
Event
Event
Audience
Custom Pixel
Feed
Event
Event
Event
Event
Audience
Event
Event
Event
Audience
Data Warehouse
Event
Audience
Audience
Event
Feed
Loyalty Feed
Audience
Audience
Event
Audience
Audience
Audience
Cookie Sync
Event
Feed
Event
Audience
Event
Audience
Audience
Audience
Event
Event
Event
Event
Audience
Cookie Sync
Cookie Sync
Audience
Feed
Audience
Code-sign the nested Swift framework inside the release XCFramework (https://github.com/mParticle/mparticle-apple-sdk/pull/948)
Backports GoDaddy TLS Root CA - R1 support to the 8.23.x line.
8.23.1 pinned the GoDaddy G2 intermediate and required every certificate at chain index >= 1 to match, so it rejected certificate chains issued under GoDaddy’s TLS Root CA R1 hierarchy. GoDaddy has ended DV issuance under G2, so affected hosts cannot be served a G2 leaf indefinitely.
This release backports root-only certificate matching (shipped on the main line in 8.26.0) and adds the self-signed GoDaddy TLS Root CA - R1 to the pinned root set, alongside the existing GoDaddy and ISRG anchors. Certificate pinning behaviour is the only change; there are no API changes.
Swift Package Manager: Package.swift for this release resolves its xcframeworks from the assets attached below rather than from static.mparticle.com. Checksums:
mParticle_Apple_SDK.xcframework.zip — 4203313ecf5f27be2434f37af39d10898159a3dda6cca8c21ff237a272bf36e8mParticle_Apple_SDK_NoLocation.xcframework.zip — aca86f77832cbd91933a410037659f1bfda73315945adc32a64dca78aa553eeeBackports GoDaddy TLS Root CA - R1 support to the 8.12.x line.
8.12.0 pinned the GoDaddy G2 intermediate and required every certificate at chain index >= 1 to match, so it rejected certificate chains issued under GoDaddy’s TLS Root CA R1 hierarchy. GoDaddy has ended DV issuance under G2, so affected hosts cannot be served a G2 leaf indefinitely.
This release backports root-only certificate matching (shipped on the main line in 8.26.0) and adds the self-signed GoDaddy TLS Root CA - R1 to the pinned root set, alongside the existing GoDaddy and ISRG anchors. Certificate pinning behaviour is the only change; there are no API changes.
Swift Package Manager and CocoaPods both build from source on the 8.12.x line — Package.swift declares no binary targets — so resolving the v8.12.1 tag is sufficient and no checksums are involved.
Pre-built xcframeworks are attached below for convenience. They are not referenced by Package.swift and are not required to consume this release.
mParticle_Apple_SDK.xcframework.zip — 4a2eef828bbd17c58f8d3d361218bccae321bb7d728fef0a2d202ba023f703b0mParticle_Apple_SDK.xcframework.nolocation.zip — f5324fe8bfbed99b9bcd44a116b91329fa54eaff6d9d93e2d48b6eb2f3a6a528Each contains four slices — ios-arm64, ios-arm64_x86_64-simulator, tvos-arm64, tvos-arm64_x86_64-simulator. As with previous releases on this line, they are unsigned.
Carthage: mParticle_Apple_SDK.json is unchanged. It resolves mParticle_Apple_SDK.framework.zip, a fat-framework archive this release does not produce, so Carthage users on 8.12.x remain on 8.12.0.
Backports GoDaddy TLS Root CA - R1 support to the 8.15.x line.
8.15.1 pinned the GoDaddy G2 intermediate and required every certificate at chain index >= 1 to match, so it rejected certificate chains issued under GoDaddy’s TLS Root CA R1 hierarchy. GoDaddy has ended DV issuance under G2, so affected hosts cannot be served a G2 leaf indefinitely.
This release backports root-only certificate matching (shipped on the main line in 8.26.0) and adds the self-signed GoDaddy TLS Root CA - R1 to the pinned root set, alongside the existing GoDaddy and ISRG anchors. Certificate pinning behaviour is the only change; there are no API changes.
Swift Package Manager: Package.swift for this release resolves its xcframeworks from the assets attached below rather than from static.mparticle.com. Checksums:
mParticle_Apple_SDK.xcframework.zip — 82fc9874005a1297a4d40496a38d14dc36cae4c5aed534e8f5d04c3652f1b205mParticle_Apple_SDK_NoLocation.xcframework.zip — db2e29734420de551821ed81456622b3d9d1361754579c4002b1fb6bfbbfef42MPRokt.selectPlacements and MPRokt.selectShoppableAds now deliver a RoktPlacementFailure event to the caller’s onEvent handler when the Rokt kit configuration is unavailable. Previously the call was dropped with only a log message, leaving callers waiting on a callback that never arrived. (#814)MPRokt.selectPlacements and MPRokt.selectShoppableAds now deliver a RoktPlacementFailure event to the caller’s onEvent handler when the Rokt kit configuration is unavailable. Previously the call was dropped with only a log message, leaving callers waiting on a callback that never arrived. (#814)MPRokt.selectPlacements and MPRokt.selectShoppableAds now deliver a RoktPlacementFailure event to the caller’s onEvent handler when the Rokt kit configuration is unavailable. Previously the call was dropped with only a log message, leaving callers waiting on a callback that never arrived. (#814)MParticleOptions.deviceConsentState and MParticle.sharedInstance.deviceConsentState. When set, it supersedes user/MPID-level consent everywhere consent is evaluated (kit enablement, consent forwarding to kits, and the consent included in uploads for all MPIDs), is persisted device-wide independent of the active user, and triggers the same kit refresh as a user consent change. Set it to nil to clear and revert to user/MPID-level consent.MPRokt.handleURLCallback: for forwarding Afterpay/PayPal redirect URLs to the registered Rokt payment extension. Call from application:openURL:options: (AppDelegate) or scene:openURLContexts: / .onOpenURL (Scene/SwiftUI).RoktContracts to 2.0.0 (adds PaymentMethodType.paypal and totals on PaymentPreparation).MParticle.sharedInstance.identity.deviceApplicationStamp now returns the same value sent on the wire as device_application_stamp (mp_deviceid). Previously it returned the unrelated MPDevice.deviceIdentifier used for ramp bucketing.mParticle_Apple_SDK (xcframework/CocoaPods framework) or mParticle_Apple_SDK_ObjC (SPM/CocoaPods ObjC). CI smoke-tests kit headers against the core SDK xcframework.braze-16 kit track for Braze Swift SDK 16.x.useEcommerceRecommendedEvents is enabled in kit configuration, forward supported mParticle commerce events to Braze recommended eCommerce events (ecommerce.cart_updated, ecommerce.checkout_started, ecommerce.product_viewed, ecommerce.order_placed, ecommerce.order_refunded).RoktSDKPlus) — Umbrella Swift package and CocoaPods pod at Kits/rokt-sdk-plus/rokt-sdk-plus-ios, versioned with the core SDK and mirrored to ROKT/rokt-sdk-plus-ios.xcodebuild -create-xcframework for this Swift-package-only target (archives do not produce *.framework under Products/Library/Frameworks/). CI uploads a small placeholder zip so mirror artifact steps still succeed; integrate via SwiftPM or CocoaPods from the tag.RoktSDKPlus.podspec with the ecosystem version (double-quoted s.version, same as other kits). Release – Draft now bumps single-quoted s.version = '…' podspec lines so mParticle-Rokt and RoktSDKPlus stay in sync for pod lib lint.Rokt-Widget to 5.1.0 (adds Afterpay payment support).RoktContracts to 2.0.0.handleURLCallback: to Rokt.handleURLCallback(with:) on the Rokt SDK.stop on MPKitRokt so the kit remains active across switchWorkspaceWithOptions: without requiring an app restart.MParticleOptions.deviceConsentState and MParticle.sharedInstance.deviceConsentState. When set, it supersedes user/MPID-level consent everywhere consent is evaluated (kit enablement, consent forwarding to kits, and the consent included in uploads for all MPIDs), is persisted device-wide independent of the active user, and triggers the same kit refresh as a user consent change. Set it to nil to clear and revert to user/MPID-level consent.MPRokt.handleURLCallback: for forwarding Afterpay/PayPal redirect URLs to the registered Rokt payment extension. Call from application:openURL:options: (AppDelegate) or scene:openURLContexts: / .onOpenURL (Scene/SwiftUI).RoktContracts to 2.0.0 (adds PaymentMethodType.paypal and totals on PaymentPreparation).MParticle.sharedInstance.identity.deviceApplicationStamp now returns the same value sent on the wire as device_application_stamp (mp_deviceid). Previously it returned the unrelated MPDevice.deviceIdentifier used for ramp bucketing.mParticle_Apple_SDK (xcframework/CocoaPods framework) or mParticle_Apple_SDK_ObjC (SPM/CocoaPods ObjC). CI smoke-tests kit headers against the core SDK xcframework.braze-16 kit track for Braze Swift SDK 16.x.useEcommerceRecommendedEvents is enabled in kit configuration, forward supported mParticle commerce events to Braze recommended eCommerce events (ecommerce.cart_updated, ecommerce.checkout_started, ecommerce.product_viewed, ecommerce.order_placed, ecommerce.order_refunded).RoktSDKPlus) — Umbrella Swift package and CocoaPods pod at Kits/rokt-sdk-plus/rokt-sdk-plus-ios, versioned with the core SDK and mirrored to ROKT/rokt-sdk-plus-ios.xcodebuild -create-xcframework for this Swift-package-only target (archives do not produce *.framework under Products/Library/Frameworks/). CI uploads a small placeholder zip so mirror artifact steps still succeed; integrate via SwiftPM or CocoaPods from the tag.RoktSDKPlus.podspec with the ecosystem version (double-quoted s.version, same as other kits). Release – Draft now bumps single-quoted s.version = '…' podspec lines so mParticle-Rokt and RoktSDKPlus stay in sync for pod lib lint.Rokt-Widget to 5.1.0 (adds Afterpay payment support).RoktContracts to 2.0.0.handleURLCallback: to Rokt.handleURLCallback(with:) on the Rokt SDK.stop on MPKitRokt so the kit remains active across switchWorkspaceWithOptions: without requiring an app restart.MParticleOptions.deviceConsentState and MParticle.sharedInstance.deviceConsentState. When set, it supersedes user/MPID-level consent everywhere consent is evaluated (kit enablement, consent forwarding to kits, and the consent included in uploads for all MPIDs), is persisted device-wide independent of the active user, and triggers the same kit refresh as a user consent change. Set it to nil to clear and revert to user/MPID-level consent.MPRokt.handleURLCallback: for forwarding Afterpay/PayPal redirect URLs to the registered Rokt payment extension. Call from application:openURL:options: (AppDelegate) or scene:openURLContexts: / .onOpenURL (Scene/SwiftUI).RoktContracts to 2.0.0 (adds PaymentMethodType.paypal and totals on PaymentPreparation).MParticle.sharedInstance.identity.deviceApplicationStamp now returns the same value sent on the wire as device_application_stamp (mp_deviceid). Previously it returned the unrelated MPDevice.deviceIdentifier used for ramp bucketing.mParticle_Apple_SDK (xcframework/CocoaPods framework) or mParticle_Apple_SDK_ObjC (SPM/CocoaPods ObjC). CI smoke-tests kit headers against the core SDK xcframework.RoktSDKPlus) — Umbrella Swift package and CocoaPods pod at Kits/rokt-sdk-plus/rokt-sdk-plus-ios, versioned with the core SDK and mirrored to ROKT/rokt-sdk-plus-ios.xcodebuild -create-xcframework for this Swift-package-only target (archives do not produce *.framework under Products/Library/Frameworks/). CI uploads a small placeholder zip so mirror artifact steps still succeed; integrate via SwiftPM or CocoaPods from the tag.RoktSDKPlus.podspec with the ecosystem version (double-quoted s.version, same as other kits). Release – Draft now bumps single-quoted s.version = '…' podspec lines so mParticle-Rokt and RoktSDKPlus stay in sync for pod lib lint.Rokt-Widget to 5.1.0 (adds Afterpay payment support).RoktContracts to 2.0.0.handleURLCallback: to Rokt.handleURLCallback(with:) on the Rokt SDK.stop on MPKitRokt so the kit remains active across switchWorkspaceWithOptions: without requiring an app restart.MParticleOptions.deviceConsentState and MParticle.sharedInstance.deviceConsentState. When set, it supersedes user/MPID-level consent everywhere consent is evaluated (kit enablement, consent forwarding to kits, and the consent included in uploads for all MPIDs), is persisted device-wide independent of the active user, and triggers the same kit refresh as a user consent change. Set it to nil to clear and revert to user/MPID-level consent.MPRokt.handleURLCallback: for forwarding Afterpay/PayPal redirect URLs to the registered Rokt payment extension. Call from application:openURL:options: (AppDelegate) or scene:openURLContexts: / .onOpenURL (Scene/SwiftUI).RoktContracts to 2.0.0 (adds PaymentMethodType.paypal and totals on PaymentPreparation).MParticle.sharedInstance.identity.deviceApplicationStamp now returns the same value sent on the wire as device_application_stamp (mp_deviceid). Previously it returned the unrelated MPDevice.deviceIdentifier used for ramp bucketing.RoktSDKPlus) — Umbrella Swift package and CocoaPods pod at Kits/rokt-sdk-plus/rokt-sdk-plus-ios, versioned with the core SDK and mirrored to ROKT/rokt-sdk-plus-ios.xcodebuild -create-xcframework for this Swift-package-only target (archives do not produce *.framework under Products/Library/Frameworks/). CI uploads a small placeholder zip so mirror artifact steps still succeed; integrate via SwiftPM or CocoaPods from the tag.RoktSDKPlus.podspec with the ecosystem version (double-quoted s.version, same as other kits). Release – Draft now bumps single-quoted s.version = '…' podspec lines so mParticle-Rokt and RoktSDKPlus stay in sync for pod lib lint.Rokt-Widget to 5.1.0 (adds Afterpay payment support).RoktContracts to 2.0.0.handleURLCallback: to Rokt.handleURLCallback(with:) on the Rokt SDK.MPRokt.handleURLCallback: for forwarding Afterpay/PayPal redirect URLs to the registered Rokt payment extension. Call from application:openURL:options: (AppDelegate) or scene:openURLContexts: / .onOpenURL (Scene/SwiftUI).RoktContracts to 2.0.0 (adds PaymentMethodType.paypal and totals on PaymentPreparation).RoktSDKPlus) — Umbrella Swift package and CocoaPods pod at Kits/rokt-sdk-plus/rokt-sdk-plus-ios, versioned with the core SDK and mirrored to ROKT/rokt-sdk-plus-ios.xcodebuild -create-xcframework for this Swift-package-only target (archives do not produce *.framework under Products/Library/Frameworks/). CI uploads a small placeholder zip so mirror artifact steps still succeed; integrate via SwiftPM or CocoaPods from the tag.RoktSDKPlus.podspec with the ecosystem version (double-quoted s.version, same as other kits). Release – Draft now bumps single-quoted s.version = '…' podspec lines so mParticle-Rokt and RoktSDKPlus stay in sync for pod lib lint.Rokt-Widget to 5.1.0 (adds Afterpay payment support).RoktContracts to 2.0.0.handleURLCallback: to Rokt.handleURLCallback(with:) on the Rokt SDK.MPRokt.handleURLCallback: for forwarding Afterpay/PayPal redirect URLs to the registered Rokt payment extension. Call from application:openURL:options: (AppDelegate) or scene:openURLContexts: / .onOpenURL (Scene/SwiftUI).RoktContracts to 2.0.0 (adds PaymentMethodType.paypal and totals on PaymentPreparation).RoktSDKPlus) — Umbrella Swift package and CocoaPods pod at Kits/rokt-sdk-plus/rokt-sdk-plus-ios, versioned with the core SDK and mirrored to ROKT/rokt-sdk-plus-ios.xcodebuild -create-xcframework for this Swift-package-only target (archives do not produce *.framework under Products/Library/Frameworks/). CI uploads a small placeholder zip so mirror artifact steps still succeed; integrate via SwiftPM or CocoaPods from the tag.Rokt-Widget to 5.1.0 (adds Afterpay payment support).RoktContracts to 2.0.0.handleURLCallback: to Rokt.handleURLCallback(with:) on the Rokt SDK.MPRokt.handleURLCallback: for forwarding Afterpay/PayPal redirect URLs to the registered Rokt payment extension. Call from application:openURL:options: (AppDelegate) or scene:openURLContexts: / .onOpenURL (Scene/SwiftUI).RoktContracts to 2.0.0 (adds PaymentMethodType.paypal and totals on PaymentPreparation).Rokt-Widget to 5.1.0 (adds Afterpay payment support).RoktContracts to 2.0.0.handleURLCallback: to Rokt.handleURLCallback(with:) on the Rokt SDK.Refer the MIGRATING.md for the migration guide from version 8.x to 9.x
Full Changelog: https://github.com/mParticle/mparticle-apple-sdk/compare/v8.44.4…v9.0.0
Full Changelog: https://github.com/mParticle/mparticle-apple-sdk/compare/v8.44.3…v8.44.4
Full Changelog: https://github.com/mParticle/mparticle-apple-sdk/compare/v8.44.0…v8.44.1
Full Changelog: https://github.com/mParticle/mparticle-apple-sdk/compare/v8.43.1…v8.44.0
Full Changelog: https://github.com/mParticle/mparticle-apple-sdk/compare/v8.42.2…v8.43.1
Full Changelog: https://github.com/mParticle/mparticle-apple-sdk/compare/v8.42.1…v8.42.2
Full Changelog: https://github.com/mParticle/mparticle-apple-sdk/compare/v8.42.0…v8.42.1
Full Changelog: https://github.com/mParticle/mparticle-apple-sdk/compare/v8.41.1…v8.42.0
Full Changelog: https://github.com/mParticle/mparticle-apple-sdk/compare/v8.41.0…v8.41.1
Full Changelog: https://github.com/mParticle/mparticle-apple-sdk/compare/v8.40.0…v8.41.0
Was this page helpful?