Sourcepoint offers a variety of SDKs that allow your organization to run our messaging campaigns on different devices. In this article we will provide an overview of our SDK types (Unified vs legacy). 

Unified vs legacy SDKs

In this section, we will cover the difference between two sets of SDKs that our clients may be utilizing in their implementations: legacy and unified SDKs.

Legacy SDKs

Sourcepoint's legacy SDKs refer to a set of early SDKs that were adopted by clients to support GDPR and CCPA compliance regimes for either Android or iOS devices.

Sourcepoint legacy SDKs are characterized by a single compliance regime for each platform.

 Example

If your organization wished to comply with both GDPR and CCPA on Android devices, you would have needed to implement two separate SDKs (i.e. GDPR for Android and CCPA for Android).

While your organization can continue to utilize legacy SDKs, all future feature developments will be for our Unified SDK. We strongly encourage your organization to implement or migrate your existing implementations to our Unified SDKs.

Unified SDKs

Sourcepoint's Unified SDK combines support for GDPR and CCPA compliance regimes into a single SDK for each platform.

 Example

Using a Unified SDK, your organization can support both GDPR and CCPA compliance regimes on Android devices using a single SDK (instead of two legacy SDKs).

A Unified SDK approach provides the following benefits for Sourcepoint and its clients:

  • Allows Sourcepoint to develop new features, maintain, and update our SDKs more quickly
  • Easier support for new and updated compliance regimes
  • Simpler and faster client implementations
  • Improved messaging performance.

Mobile and OTT SDKs

For a comprehensive list of mobile and OTT SDKs we offer, please visit the help center article below:

  Note: Unless indicated, any non-legacy SDK will be considered unified (i.e. will support GDPR and CCPA compliance regimes).

Was this article helpful?
0 out of 0 found this helpful