Historical Release Notes

Historical release notes for iOS SDK 4.x for Marketing Cloud Solutions guide, listed by release date in descending order.

New Features in Version 4.10.0

The iOS SDK version 4.10.0 (May 20, 2016) includes the following changes:

Feature Description

Target methods

You can now use the following new Target methods:

  • targetLoadRequestWithName:defaultContent:profileParameters:orderParameters:mboxParameters:callback:
  • targetThirdPartyID
  • targetSetThirdPartyID:
  • targetPcID
  • targetSessionID

See Target Methods.

TVJS methods

You can now use the following new Target TVJS methods:

  • targetThirdPartyID
  • targetSetThirdPartyID
  • targetPcID
  • targetSessionID

See TVJS Methods.

Adobe Target for TVML/TVJS

You can now use the following property names when configuring your ADBTarget element:

  • id
  • total
  • purchasedProductIds
  • mboxParameters

See Adobe Target for TVML/TVJS.

New Features in Version 4.9.0

The iOS SDK version 4.9.0 (May 5, 2016) includes the following changes:

Feature Description

Deep linking

You can implement deep linking in your applications to drive users to app or web link destinations.

See Implementing Deep Linking.

New Features in Version 4.8.6

The iOS SDK version 4.8.6 (March 9, 2016) includes the following changes:

Feature Description

Track app crashes

The iOS SDK version 4.8.6 contains critical changes that prevent false crashes from being reported. We highly recommend that you update to version 4.8.6.

See Track App Crashes.

New Features in Version 4.8.5

The iOS SDK version 4.8.5 (February 18, 2016) includes the following changes:

Feature Description

Opt-out and privacy settings

Starting with iOS SDK 4.8.5, privacy settings set via the setPrivacyStatus method affect activity from Analytics, Target, and Audience Manager.

See ADBMobile JSON Config and Opt-Out and Privacy Settings

New Features in Version 4.8.0

The iOS SDK version 4.8.0 (November 2, 2015) includes the following changes:

Feature Description
New Marketing Cloud Visitor ID Service methods

Added the following new methods:

  • visitorSyncIdentifiers:authenticationState:
  • visitorSyncIdentifierWithType:identifier:authenticationState:
  • visitorGetIDs

Changed the visitorSyncIdentifiers:identifiers method to visitorSyncIdentifiers:

See Marketing Cloud Visitor ID Service Methods.

New TVJS methods

Added the following new methods:

  • visitorSyncIdentifiersAuthenticationState
  • visitorSyncIdentifierWithTypeIdentifierAuthenticationState
  • visitorGetIDsJs

See TVJS Methods.

New ADBMobile JSON Config variable

Added the following variable:

  • analyticsForwardingEnabled

See ADBMobile JSON Config.

New Features in Version 4.7.0

The iOS SDK version 4.7.0 (October 15, 2015) includes the following changes:

Feature Description
tvOS Support

tvOS is supported for Apple TV.

See Core Implementation and Lifecycle and Apple TV Implementation with tvOS.

App Transport Security Support

Starting with iOS 9, Apple introduced App Transport Security, a set of requirements that conforms to best practices for secure connections.

See App Transport Security.

PhoneGap Plugin methods

Added the following new methods:

Configuration Methods

  • setPushIdentifier
  • setAdvertisingIndentifier
  • keepLifecycleSessionAlive
  • trackingSendQueuedHits

Tracking Methods

  • trackPushMessageClickthrough

New Target method:

  • targetClearCookies

Acquisition Methods

  • acquisitionCampaignStartForApp

Audience Manager Methods

  • audienceGetVisitorProfile
  • audienceGetDpuuid
  • audienceGetDpid
  • audienceSetDpidAndDpuuid
  • audienceSignalWithData
  • audienceReset

Visitor ID Service Methods

  • visitorGetMarketingCloudId
  • visitorSyncIdentifiers

App Extensions and Apple Watch Methods

  • setAppGroup
  • syncSettings
  • initializeWatch

See PhoneGap Plug-in Methods.

New Features in Version 4.6

The iOS SDK version 4.6 (September 17, 2015) includes the following changes:

Feature Description

Push Messaging to Analytics Segments

Adobe Mobile Services and the Adobe Mobile SDK allow you to send push messages to Analytics segments. The SDK also allows you to easily report users that have opened your app as a result of opening the push message.

See Push Messaging.

Acquisition Methods

Allows developers to start an app acquisition campaign as if the user had clicked a link. This is helpful for creating manual acquisition links and handling the app store redirect yourself.

See Acquisition Methods.


Postbacks let you send data collected by the SDK to a separate third-party server. Leveraging the same triggers and traits you use to display an in-app message, you can configure the SDK to send customized data to a third-party destination.

See Postbacks.


Added the following new identifiers:

WatchKit Support for WatchOS 2

Added WatchKit support for WatchOS 2.

See Apple Watch Implementation with WatchOS 2.

New Features in Version 4.5

The iOS SDK version 4.5 includes the following changes:

Feature Description

iOS Extension

Starting in iOS SDK version 4.5, a new iOS extension lets you collect usage data from your Apple Watch Apps, Today Widgets, Photo Editing widgets, and all the other iOS extension apps.

We strongly recommend that you use the iOS SDK rather than using your own wrapper.

Apple provides a set of APIs that lets the Watch app communicate with the containing app (sending requests to the containing app and then receiving responses).

Although you can send tracking data as a dictionary from the Watch app to the containing app and then call any tracking method on the containing app to send the data, this solution has limitations.

In most cases when a user is using the Watch app, the containing app is running in the background and it is only safe to call TrackActionInBackground, TrackLocation, and TrackBeacon. Calling other tracking methods interferes with lifecycle data, so you should use only these three methods to send the data from Watch app.

Even if these three tracking methods meet your requirements, we recommend using the iOS SDK because the SDK for watch app includes all Mobile features except in-app messaging.

See iOS Extension Implementation.

New Features in Version 4.4

Feature Description

Custom data with lifecycle metrics

You can now include custom context data variables with lifecycle metrics. See Implement Lifecycle Metrics.

Beacon tracking support in PhoneGap

The trackBeacon and clearCurrentBeacon calls are now available in PhoneGap.

New Features in Version 4.3

Feature Description

Marketing Cloud Visitor ID

The Marketing Cloud visitor ID service provides a universal visitor ID across Marketing Cloud solutions.

New Features in Version 4.2

Feature Description

In-App Messaging

Deliver in-app messages to your app users triggered from any analytics data or event. After implementation, messages are delivered to the app dynamically without requiring a code update.

Dynamic Points of Interest

Points of interests are now retrieved dynamically after they are defined in Adobe Mobile services. You no longer need to submit an app update to the store to update your points of interest.

Run-time selection of JSON Config file

You can now load a different ADBMobile JSON Config file when the application starts. The different configuration is used until the application is closed.

POST Support

All hits are now sent using HTTP POST instead of GET.

New Features in Version 4.1

Feature Description

Mobile app acquisition

Allows you to measure the effectiveness of app download campaigns. By generating acquisition links in Adobe mobile services and implementing version 4.1, you can measure your acquisition channels from the first click through KPIs.

Hit batching

Enables the SDK to store hits and send them in batches instead of sending each hit as it occurs.

iBeacon support

Support for iBeacon technology to measure and personalize for app users in close proximity.

New Features in Version 4

In addition to significant performance increases, version 4 adds the following new features:

Feature Description

Geo-location - Points of Interest

Points of interest are for you to set up a lat/long central point, determine a radius, and then our trackLocation call will determine if the location provided for that call falls within any of your points of interest.

Lifetime Value

Lifetime value is a way to measure your users’ contributions and usage within your app. Each time you send in a value with trackLifetimeValueIncrease, it will add to that user’s existing value.

Timed Action

Timed Actions are an easy way for you see how long it takes your users to complete a process end-to-end within your app. Using trackTimedActionStart, trackTimedActionUpdate, and trackTimedActionEnd, we will calculate the amount of time in session and the total time (cross-session) it takes for the action to be completed.


Quickly enable and disable analytics.