Skip to main content

iOS SDK

With the Kameleoon iOS (Swift) SDK, you can run experiments and activate feature flags on native mobile iOS applications. Integrating our SDK into your Swift apps is easy, and its footprint (memory and network usage) is low.

Getting started: For help getting started, see the developer guide.

Changelog: Latest version of the Swift SDK: 4.10.0 Changelog.

SDK methods: For the full reference documentation of the iOS SDK methods, see the reference section.

Developer guide​

Follow these steps to install and configure the Kameleoon iOS SDK in your application for the first time.

Getting started​

Starter kit​

If you're just getting started with Kameleoon, we provide a starter kit and demo application to test the SDK and learn how it works. The starter kit includes a fully configured app with examples demonstrating how you might use the SDK methods in your app. You can find the starter kit, the demo application and detailed instructions on how to use it at Starter kit for iOS

Prerequisites​

  • Use Swift version 5.0 or higher on the iOS platform. There is no planned support for earlier iOS applications (including earlier Swift versions and Objective-C apps). We provide a Universal Framework version compatible both with x86_64 (for the iOS Simulator) and ARM (for production deployment into the App Store).

Installation​

You can install the iOS SDK using CocoaPods or Swift Package Manager:

With Swift Package Manager, add a package dependency to your Xcode project. Select File > Swift Packages > Add Package Dependency and enter the repository URL: https://github.com/Kameleoon/client-swift.

Alternatively, you can modify your Package.swift file directly:

dependencies: [
  .package(url: "https://github.com/Kameleoon/client-swift.git", from("3.0.3"))
]

Additional configuration​

To customize the SDK behavior, create a kameleoon-client-swift.plist configuration file in the root directory of your Xcode project. You can also download a sample configuration file.

These are the keys you can set:

  • refresh_interval_minute (optional): Specifies the frequency, in minutes, that active experiments and feature flags are fetched from the Kameleoon servers. The initial fetch is performed on the first application launch and subsequent fetches are processed at the defined refresh interval. Once you launch an experiment, pause the experiment, or stop the experiment, the change won't propagate to each of your visitors' iOS devices until their next refresh. This means if you set the refresh interval to 30 minutes, it may take up to 30 minutes before all devices receive the update. If not specified, the default interval is 60 minutes.
  • data_expiration_interval_minute: Designates the predefined time period, in minutes, that the SDK stores the visitor and their associated data. Each data instance is evaluated individually. This allows you to set the amount of time the SDK saves the data before automatically deleting it. If no interval is specified, the SDK does not automatically delete data from the device. The default value is Date.distantFuture.
  • default_timeout_millisecond: Specifies the refresh interval, in minutes, that the SDK fetches the configuration for the active experiments and feature flags. The value determines the maximum time it takes to propagate changes, such as activating or deactivating feature flags or launching experiments, to your production servers. If left unspecified, the default interval is set to 60 minutes. Additionally, we offer a streaming mode that uses server-sent events (SSE) to push new configurations to the SDK automatically and apply new configurations in real-time, without any delays.
  • tracking_interval_millisecond: this specifies the interval for tracking requests, in milliseconds. All visitors who were evaluated for any feature flag or had data flushed will be included in this tracking request, which is performed once per interval. The minimum value is 100 ms and the maximum value is 1000 ms, which is also the default value.
  • environment (optional): For customers using multi-environment experimentation and feature flagging, this option specifies which feature flag configuration to use. By default, each feature flag has the options production, staging, development. If not specified, the default value is production. More information.
  • is_unique_identifier (optional): Indicates that the specified visitorCode is a unique identifier. If not provided, the default value is false.
note

If you specify a visitorCode and set the isUniqueIdentifier parameter to true, the SDK methods use the visitorCode value as the unique visitor identifier, which is useful for cross-device experimentation. The SDK links the flushed data with the visitor that is associated with the specified identifier.

The isUniqueIdentifier can be useful in other edge-case scenarios, such as when you can't access the anonymous visitorCode that was originally assigned to the visitor, but you do have access to an internal ID that is connected to the anonymous visitor using session merging capabilities.

Initialize the Kameleoon Client​

After you've the SDK in your application and set up the app properties, the next step is to create the Kameleoon Client. A Client is a singleton object that acts as a bridge between your application and the Kameleoon platform. It includes all the methods and properties you need to run an experiment.

import kameleoonClient

let visitorCode = "visitorCode"
let siteCode = "a8st4f59bj"
do {
    // pass client configuration as an argument
    let config = try KameleoonClientConfig(
        clientId: "clientId", // optional
        clientSecret: "clientSecret", // optional
        refreshIntervalMinute: 15, // optional, 60 minutes by default
        dataExpirationIntervalMinute: 60*24*365, // optional, `Data.distantFuture` by default
        defaultTimeoutMillisecond: 10_000, // optional, 10_000 milliseconds by default
        trackingIntervalMillisecond: 500, // optional, 1000 milliseconds by default
        environment: "production", // optional
        isUniqueIdentifier: true, // optional, false by default
    )
    let kameleoonClient = try KameleoonClientFactory.create(
        siteCode: siteCode,
        visitorCode: visitorCode, // optional
        config: config // optional
    )
} catch KameleoonError.visitorCodeInvalid {
  // Provided visitor code is invalid
} catch KameleoonError.siteCodeIsEmpty {
  // Indicates that provided site code is empty
} catch {
    // Unexpected error occurred
}

do {
    // read client configuration from a file 'kameleoon-client-swift.plist'
    // visitor code isn't provided, so SDK generates a random visitor code which it will use in the future
    let kameleoonClient = try KameleoonClientFactory.create(siteCode: siteCode)
} catch KameleoonError.visitorCodeInvalid {
    // Provided visitor code is invalid
} catch {
    // Unexpected error occurred
}

The KameleoonClientFactory.create() method initializes the client, but the client is not immediately ready for use. The client must retrieve the current configuration of experiments and feature flags (along with their traffic repartition) from a Kameleoon remote server. This requires the client to have network access, which is not always available. Until the Kameleoon Client is fully ready, you should not attempt to run other methods in the Kameleoon iOS SDK. After the client fetches the first configuration of feature flags, it periodically refreshes the configuration. If the refresh fails for any reason, the Kameleoon client continues to function using the previous configuration.

You can use the .ready public getter to check if the Kameleoon client initialization is finished.

Alternatively, you can use a helper callback to encapsulate the logic of experiment triggering and variation implementation. The best approach (.ready or callback) depends on your preferences and use case. We recommend using .ready when you expect that the SDK will already be ready for use. For example, if you are running an experiment on a dialog that would be accessible only after a few seconds or minutes of navigation within the app. We recommend using the callback when there is a high probability that the SDK is still initializing when the experiment is accessible. For example, an experiment that is visible at the launch of the app should use a callback that makes the application wait until either the SDK is ready or a specified timeout has expired.

note

It's your responsibility as the app developer to ensure the client is ready before calling any methods. A good practice is to always assume that the app user should be left out of the experiment if the Kameleoon client is not yet ready. This is actually easy to do, because this corresponds to the implementation of the default reference variation logic. For example, as shown in the code sample above.

You're now ready to implement feature management and features flags. See the Reference section for details about additional methods.

Best practices for initialization and usage​

  • We recommend initializing KameleoonClient as a singleton as early as possible after the application starts. This ensures that initialization begins promptly, as it may take some time. Since initialization is asynchronous, it does not block or delay the application's startup process.
  • Before using KameleoonClient, verify that it is initialized by calling the runWhenReady method. Otherwise, attempts to use the client before it is ready will result in errors.
  • ⚠️ Most key methods may throw errors, so proper exception handling is required. Be sure to review the documentation for each method you use to understand its potential errors.
// Initialize `KameleoonClient` on application startup and use it as a singleton later
do {
    let kameleoonClient = try KameleoonClientFactory.create(siteCode: "<siteCode>");
} catch {}

// Example: Apply a discount percentage based on an feature flag variable's value
func applyDiscountIfApplicable() {
    client.runWhenReady(timeoutMilliseconds: 1000) { ready in
        guard ready else { return }
        if let variation = try? client.getVariation(featureKey: "discount"),
           let discount = variation.variables["discount_value"]?.value as? Double {
            applyDiscount(value: discount)
        }
    }
}

Activating a feature flag​

Retrieving a flag configuration​

To implement a feature flag in your code, you must first create the feature flag in your Kameleoon account.

To determine the status or variation of a feature flag for a specific user, you should use the getVariation() or isFeatureActive() method to retrieve the configuration based on the featureKey.

The getVariation() method handles both simple feature flags with ON/OFF states and more complex flags with multiple variations. The method retrieves the appropriate variation for the user by checking the feature rules, assigning the variation, and returning it based on the featureKey and visitorCode.

The isFeatureActive() method can be used if you want to retrieve the configuration of a simple feature flag that has only an ON or OFF state, as opposed to more complex feature flags with multiple variations or targeting options.

If your feature flag has associated variables (such as specific behaviors tied to each variation) getVariation() also enables you to access the Variation object, which provides details about the assigned variation and its associated experiment. This method checks whether the user is targeted, finds the visitor’s assigned variation, and saves it to storage. When track=true, the SDK will send the exposure event to the specified experiment on the next tracking request, which is automatically triggered based on the SDK’s tracking_interval_millisecond. By default, this interval is set to 1000 milliseconds (1 second).

The getVariation() method allows you to control whether tracking is done. If track=false, no exposure events will be sent by the SDK. This is useful if you prefer not to track data through the SDK and instead rely on client-side tracking managed by the Kameleoon engine, for example. Additionally, setting track=false is helpful when using the getVariations() method, where you might only need the variations for all flags without triggering any tracking events. If you want to know more about how tracking works, view this article

Adding data points to target a user or filter / breakdown visits in reports​

To target a user, ensure you've added relevant data points to their profile before retrieving the feature variation or checking if the flag is active. Use the addData() method to add these data points to the user's profile.

To retrieve data points that have been collected on other devices, use the getRemoteVisitorData() method. This method asynchronously fetches data from our servers. However, it is important you call getRemoteVisitorData() before retrieving the variation or checking if the feature flag is active, as this data might be required to assign a user to a given variation of a feature flag.

To learn more about available targeting conditions, read our detailed article on the subject.

Additionally, the data points you add to the visitor profile will be available when analyzing your experiments, allowing you to filter and break down your results by factors like device. See the complete list here.

If you need to track additional data points beyond what's automatically collected, you can use Kameleoon's Custom Data feature. Custom Data allows you to capture and analyze specific information relevant to your experiments. Don't forget to call the flush() method to send the collected data to Kameleoon servers for analysis.

Tracking goal conversions​

When a user completes a desired action (such as making a purchase), it is recorded as a conversion. To track conversions, use the trackConversion() method and provide the required goalId parameter.

The conversion tracking request will be sent along with the next scheduled tracking request, which the SDK sends at regular intervals (defined by tracking_interval_millisecond). If you prefer to send the request immediately, use the flush() method with the parameter instant=true.

Cross-device experimentation​

To support visitors who access your app from multiple devices, Kameleoon allows you to synchronize previously collected visitor data across each of the visitor's devices and reconcile their visit history across devices through cross-device experimentation. We recommend reading our article on cross-device experimentation for more information on how Kameleoon handles data across devices and detailed use cases.

Synchronizing custom data across devices​

Although custom mapping synchronization is used to align visitor data across devices, it is not always necessary. Below are two scenarios where custom mapping sync is not required:

Same user ID across devices If the same user ID is used consistently across all devices, synchronization is handled automatically without a custom mapping sync. It is enough to call the getRemoteVisitorData() method when you want to sync the data collected between multiple devices.

Multi-server instances with consistent IDs In complex setups involving multiple servers (for example, distributed server instances), where the same user ID is available across servers, synchronization between servers (with getRemoteVisitorData()) is sufficient without additional custom mapping sync.

Customers who need additional data can refer to the getRemoteVisitorData() method description for further guidance. In the below code, it is assumed that the same unique identifier (in this case, the visitorCode, which can also be referred to as userId) is used consistently between the two devices for accurate data retrieval.

note

If you want to sync collected data in real time, you need to choose the scope Visitor for your custom data.

Device A
// In this example, Custom data with index `90` was set to "Visitor" scope in Kameleoon.
let visitorScopeCustomDataIndex = 90

kameleoonClient.addData(CustomData(id: visitorScopeCustomDataIndex, values: "your data"))
kameleoonClient.flush()
Device B
// Before working with the data, call `getRemoteVisitorData`.
kameleoonClient.getRemoteVisitorData { result in
    // After calling, the SDK on Device B will have access to CustomData of Visitor scope defined on Device A.
    // So, "your data" will be available to target and track the visitor.
}

Using custom data for session merging​

Cross-device experimentation allows you to combine a visitor's history across each of their devices (history reconciliation). History reconciliation allows you to merge different visitor sessions into one. To reconcile visit history, you can use CustomData to provide a unique identifier for the visitor. For more information, see our dedicated documentation.

After cross-device reconciliation is enabled, calling getRemoteVisitorData() with the parameter userId retrieves all known data for a given user.

Sessions with the same identifier will always be shown the same variation in an experiment. In the Visitor view of your experiment's results pages, these sessions will appear as a single visitor.

The SDK configuration ensures that associated sessions always see the same variation of the experiment. However, there are some limitations regarding cross-device variation allocation. We've outlined these limitations here.

Follow the activating cross-device history reconciliation guide to set up your custom data on the Kameleoon platform.

Afterwards, you can use the SDK normally. The following methods that may be helpful in the context of session merging:

  • getRemoteVisitorData() with passed isUniqueIdentifier=true to KameleoonClientConfig - to retrieve data for all linked visitors.
  • trackConversion() or flush() with passed isUniqueIdentifier=true to KameleoonClientConfig - to track some data for specific visitor that is associated with another visitor.
tip

As the custom data you use as the identifier must be set to Visitor scope, you need to use cross-device custom data synchronization to retrieve the identifier with the getRemoteVisitorData() method on each device.

Here's an example of how to use custom data for session merging.

// In this example, `91` represents the Custom Data's index,
// configured as a unique identifier in Kameleoon.
let mappingIndex = 91;
let featureKey = "ff123";

// 0. Initializing anonymous KameleoonClient

// Assume `anonymousVisitorCode` is the randomly generated ID for the visitor.
let anonymousKameleoonClient = KameleoonClientFactory.create(
    siteCode: siteCode,
    visitorCode: anonymousVisitorCode
)
anonymousKameleoonClient.runWhenReady { result in
    // ...
}

// 1. Before the visitor is authenticated

// Retrieve the variation for an unauthenticated visitor.
let anonymousVariation = anonymousKameleoonClient.getVariation(featureKey)

// 2. After the visitor is authenticated

// Assume `userId` is the visitor code of the authenticated visitor.
anonymousKameleoonClient.addData(CustomData(id: mappingIndex, values: userId))
anonymousKameleoonClient.flush(instant: true)

KameleoonClient userKameleoonClient = KameleoonClientFactory.create(
    siteCode: siteCode,
    visitorCode: userId,
    config: KameleoonClientConfig(
        isUniqueIdentifier: true // Indicate that `userId` is a unique identifier
    )
)
userKameleoonClient.runWhenReady { result in
    // ...
}

// 3. After the visitor has been authenticated

// Retrieve the variation for the `userId`, which will match the anonymous visitor code's variation.
let userVariation = userKameleoonClient.getVariation(featureKey: featureKey)
let isSameVariation = userVariation.key == anonymousVariation.key // true

// The `userId` and `anonymousVisitorCode` are now linked and tracked as a single visitor.
userKameleoonClient.trackConversion(goalId: 123, revenue: 10.0);

// Additionally, the linked visitors will share all fetched remote visitor data.
userKameleoonClient.getRemoteVisitorData { result in
    // ...
}

In this example, we have an application with a login page. Since we don't know the user ID at the moment of login, we use an anonymous visitor automatically generated by SDK. Visitor code can be retrieved with getVisitorCode() method. After the user logs in, we can associate the anonymous visitor with the user ID and use it as a unique identifier for the visitor.

Targeting conditions​

The Kameleoon SDKs support a variety of predefined targeting conditions that you can use to target users in your campaigns. For the list of conditions this SDK supports, see use visit history to target users.

You can also use your own external data to target users.

Logging​

The SDK generates logs to reflect various internal processes and issues.

Log levels​

The SDK supports configuring limiting logging by a log level.

// The `none` log level does not allow logging.
KameleoonLogger.logLevel = .none

// The `ERROR` log level only allows logging issues that may affect the SDK's main behaviour.
KameleoonLogger.logLevel = .error

// The `WARNING` log level allows logging issues which may require additional attention.
// It extends the `ERROR` log level.
// The `WARNING` log level is a default log level.
KameleoonLogger.logLevel = .warning

// The `INFO` log level allows logging general information on the SDK's internal processes.
// It extends the `WARNING` log level.
KameleoonLogger.logLevel = .info

// The `DEBUG` log level allows logging extra information on the SDK's internal processes.
// It extends the `INFO` log level.
KameleoonLogger.logLevel = .debug

Custom handling of logs​

The SDK writes its logs to the console output by default. This behaviour can be overridden.

note

Logging limiting by a log level is performed apart from the log handling logic.

public struct CustomLogger: Logging {
    let customLogger = Logger(subsystem: "com.yourcompany.app", category: "app")

    public func log(level: LogLevel, message: String) {
        switch level {
            case .error:
                customLogger.error("\(message)")
            case .warning:
                customLogger.warning("\(message)")
            case .info:
                customLogger.info("\(message)")
            case .debug:
                customLogger.debug("\(message)")
            default:
                break
        }
    }
}


// Log level filtering is applied separately from log handling logic.
// The custom logger will only accept logs that meet or exceed the specified log level.
// Ensure the log level is set correctly.
KameleoonLogger.logLevel = .debug // Optional, defaults to `LogLevel.WARNING`.
KameleoonLogger.logger = CustomLogger()

Apple privacy compliance​

Starting May 1st, 2024, Apple requires apps that include a third-party SDK, such as the Kameleoon iOS SDK, to have a privacy manifest file for that SDK. The latest version of the SDK is code-signed, compliant, and includes a valid manifest file with the SDK. No action is required if you're using the Kameleoon iOS SDK version 4.2 or later.

Reference​

This is the full reference documentation for the Kameleoon iOS (Swift) SDK.

Initialization​

Once you have installed the SDK in your application, the first step is to initialize Kameleoon. All of your application's interactions with the SDK, such as triggering an experiment, are accomplished using this Kameleoon client object.

create()​

Call this method before any others to initialize the SDK. This method is in KameleoonClientFactory. This creates an instance of KameleoonClient to manage all interactions between the SDK and your app.

You can customize the behavior of the SDK (for example, the environment, the credentials, and so on) by providing a configuration object. Otherwise, the SDK tries to find your configuration file and uses it instead.

let visitorCode = "visitorCode"
let siteCode = "a8st4f59bj"
do {
    // pass client configuration as an argument
    let config = try KameleoonClientConfig(
        clientId: "clientId", // optional
        clientSecret: "clientSecret", // optional
        refreshIntervalMinute: 15, // optional, 60 minutes by default
        dataExpirationIntervalMinute: 60*24*365, // optional, `Data.distantFuture` by default
        defaultTimeoutMillisecond: 10_000, // optional, 10_000 milliseconds by default
        trackingIntervalMillisecond: 500, // optional, 1000 milliseconds by default
        environment: "production", // optional
        isUniqueIdentifier: true, // optional, false by default
    )
    let kameleoonClient = try KameleoonClientFactory.create(
        sitecode: siteCode,
        visitorCode: visitorCode, // optional
        config: config // optional
    )
} catch KameleoonError.visitorCodeInvalid {
  // Provided visitor code is invalid
} catch KameleoonError.siteCodeIsEmpty {
  // Indicates that provided site code is empty
} catch {
    // Unexpected error occurred
}

do {
    // read client configuration from a file 'kameleoon-client-swift.plist'
    // visitor code isn't provided, so SDK generates a random visitor code which will be used in the future
    let kameleoonClient = KameleoonClientFactory.create(siteCode: siteCode)
} catch KameleoonError.visitorCodeInvalid {
  // Provided visitor code is invalid
} catch KameleoonError.siteCodeIsEmpty {
  // Indicates that provided site code is empty
} catch {
    // Unexpected error occurred
}

ready​

For mobile SDKs, the initialization of the Kameleoon Client is not immediate. The SDK needs to perform a server call to retrieve the current configuration for all active experiments. Check if the SDK is ready by calling this method before triggering an experiment. Alternatively, you can use the runWhenReady() method with a callback.

let ready = kameleoonClient.ready
Return value​
NameTypeDescription
readyBoolBoolean representing the status of the SDK (true if fully initialized, false if not ready to be used).

runWhenReady()​

  • 🔄 Performs an asynchronous request (if the configuration is outdated or missing)

For mobile SDKs, the KameleoonClient cannot initialize immediately, as it needs to perform a server call to retrieve the current configuration for all feature flags. Use the runWhenReady() method to wait until the client is ready for use. Additionally, you can set a maximum timeout period to control how long the client will wait before it becomes ready.

If ready=true, the KameleoonClient is fully initialized, and feature flags will be evaluated and assigned their respective variations. If the result is false or a timeout occurs, the initialization will not complete.

The callback or asynchronous code should handle applying the reference variation, as a timeout will exclude the user from the feature flag.

caution

Since the initial configuration may require a server call, this mechanism is asynchronous. Therefore, you should either:

  • Provide a completion callback as an argument to the method to ensure you are notified when the KameleoonClient is fully initialized and ready for use.
  • Use asynchronous operations.
func applyRecommendedProductsVariation() {
    let defaultValue = 5 // Default control number for recommended products
    kameleoonClient.runWhenReady(timeoutMilliseconds: 1000) { ready in
        guard ready else {
            applyVariation(recommendedProductsNumber: defaultValue)
            return
        }
        let variation = try? kameleoonClient.getVariation(featureKey: "featureKey")
        let recommendedProductsNumber = variation.variables["recommendedProductsNumber"]?.value as? Int ?? defaultValue

        applyVariation(recommendedProductsNumber: recommendedProductsNumber)
    }
}
Arguments​
NameTypeDescriptionDefault
timeoutMilliseconds (optional)IntTimeout for the initialization processdefaultTimeoutMillisecond or default_timeout_millisecond
callback (required)(Bool) -> VoidCallback object. It is a lambda expression that will get a Bool argument representing whether the KameleoonClient became ready before the timeout was reached.

Feature flags and variations​

isFeatureActive()​

  • 📨 Sends Tracking Data to Kameleoon (depending on the track parameter)
note

This method was previously named activateFeature, which was removed in SDK version 4.0.0.

To activate a feature toggle, call this method. This method accepts featureKey as a required argument to check if the specified feature will be active for a visitor.

If a visitor has never been associated with this feature flag, this method returns a random boolean value (true if the user should be shown this feature, otherwise false). If the visitor is already registered with this feature flag, this method returns the previous featureFlag value.

Make sure to implement error handling as shown in the example code to catch potential errors.

let featureKey = "new_checkout"
var hasNewCheckout = false

do {
    hasNewCheckout = try kameleoonClient.isFeatureActive(featureKey: featureKey)
    // disabling tracking
    hasNewCheckout = kameleoonClient.isFeatureActive(featureKey: featureKey, track: false);
} catch {
    switch error {
        case KameleoonError.sdkNotReady:
            // Exception indicating that the SDK has not completed its initialization yet.
            hasNewCheckout = false
        case KameleoonError.Feature.notFound:
		    // The feature key is not in the configuration file that has been fetched by the SDK.
            hasNewCheckout = false
        default:
            // Any other error.
            hasNewCheckout = false
    }
}

if hasNewCheckout
{
  // Implement new checkout code here
}
Arguments​
NameTypeDescription
featureKeyStringThe key of the feature you want to expose to a user. This field is required.
trackBoolAn optional parameter to enable or disable tracking of the feature evaluation (true by default).
Return value​
TypeDescription
BoolValue of the feature that is registered for the visitor.
Errors thrown​
TypeDescription
KameleoonError.sdkNotReadyException indicating that the SDK is not fully initialized yet.
KameleoonError.Feature.notFoundException indicating that the requested feature ID has not been found in the internal configuration of the SDK. This usually means that the feature flag has not yet been activated on Kameleoon's side (but code implementing the feature is already deployed in the web-application).

getVariation()​

  • 📨 Sends Tracking Data to Kameleoon (depending on the track parameter)

Retrieves the Variation assigned to a given visitor for a specific feature flag.

This method takes featureKey as a mandatory argument and track as an optional argument. The track argument is optional and defaults to true.

It returns the assigned Variation for the visitor. If the visitor is not associated with any feature flag rules, the method returns the default Variation for the given feature flag.

Ensure that proper error handling is implemented in your code to manage potential exceptions.

note

The default variation refers to the variation assigned to a visitor when they do not match any predefined delivery rules for a feature flag. In other words, it is the fallback variation applied to all users who are not targeted by specific rules. It's represented as the variation in the "Then, for everyone else..." section in a management interface.

let featureKey = "featureKey"
var variation: Types.Variation?
do {
    variation = try kameleoonClient.getVariation(featureKey: featureKey)
    // disabling tracking
    variation = kameleoonClient.getVariation(featureKey: featureKey, track: false);
} catch {
    switch error {
        case KameleoonError.sdkNotReady:
            // Exception indicating that the SDK has not completed its initialization yet.
        case KameleoonError.Feature.notFound:
		    // The feature key is not in the configuration file that has been fetched by the SDK.
        case KameleoonError.Feature.environmentDisabled:
		    // The feature flag is disabled for the environment.
        default:
            // Any other error.
    }
}

let title = variation?.variables["title"].value

switch variation?.key {
    case "on":
        // Main variation key is selected for visitorCode
    case "alternative_variation":
        // Alternative variation key
    default:
        // Default variation key
}
Arguments​
NameTypeDescriptionDefault
featureKey (required)StringKey of the feature you want to expose to a user.
track (optional)BoolAn optional parameter to enable or disable tracking of the feature evaluation.true
Return value​
TypeDescription
VariationAn assigned Variation to a given visitor for a specific feature flag.
Errors thrown​
TypeDescription
KameleoonError.sdkNotReadyException indicating that the SDK is not fully initialized yet.
KameleoonError.Feature.notFoundException indicating that the requested feature key wasn't found in the internal configuration of the SDK. This usually means that the feature flag is not activated in the Kameleoon app (but code implementing the feature is already deployed on your application).
KameleoonError.Feature.environmentDisabledException indicating that feature flag is disabled for the visitor's current environment (for example, production, staging, or development).

getVariations()​

  • 📨 Sends Tracking Data to Kameleoon (depending on the track parameter)

Retrieves a map of Variation objects assigned to a given visitor across all feature flags.

This method iterates over all available feature flags and returns the assigned Variation for each flag associated with the specified visitor. It takes onlyActive and track as optional arguments.

  • If onlyActive is set to true, the method getVariations() will return feature flags variations provided the user is not bucketed with the off variation.
  • The track parameter controls whether or not the method will track the variation assignments. By default, it is set to true. If set to false, the tracking will be disabled.

The returned map consists of feature flag keys as keys and their corresponding Variation as values. If no variation is assigned for a feature flag, the method returns the default Variation for that flag.

Proper error handling should be implemented to manage potential exceptions.

note

The default variation refers to the variation assigned to a visitor when they do not match any predefined delivery rules for a feature flag. In other words, it is the fallback variation applied to all users who are not targeted by specific rules. It's represented as the variation in the "Then, for everyone else..." section in a management interface.

do {
    let variations = kameleoonClient.getVariations();
    // only active variations
    let variations = kameleoonClient.getVariations(onlyActive: true);
    // disable tracking
    let variations = kameleoonClient.getVariations(track: false);
} catch KameleoonError.sdkNotReady {
    // Exception indicating that the SDK has not completed its initialization yet.
}
Arguments​
NameTypeDescriptionDefault
onlyActive (optional)BoolAn optional parameter indicating whether to return variations for active (true) or all (false) feature flags.false
track (optional)BoolAn optional parameter to enable or disable tracking of the feature evaluation.true
Return value​
TypeDescription
Dict<String, Variation>Map that contains the assigned Variation objects of the feature flags using the keys of the corresponding features.
Errors thrown​
TypeDescription
KameleoonError.sdkNotReadyException indicating that the SDK is not fully initialized yet.

getFeatureVariationKey()​

  • 📨 Sends Tracking Data to Kameleoon
note

This method is deprecated and will be removed in SDK version 5.0.0. Use getVariation() instead.

Use this method to get the feature variation key for a specific user. This method takes a featureKey as required argument to retrieve the variation key for the specified user.

If the visitor has never been associated with this feature flag, the SDK returns a randomly assigned variation key (according to the feature flag rules). If the visitor is already registered with this feature flag, this method returns the previous variation key. If the visitor does not match any of the rules, the default variation you defined in the Kameleoon app will be returned.

Make sure you set up proper error handling as shown in the example code to catch potential errors.

let featureKey = "new_checkout"
var variationKey = ""

do {
	variationKey = try kameleoonClient.getFeatureVariationKey(featureKey: featureKey)
    switch variationKey {
        case "variation 1":
            // The visitor has been bucketed with variation 1 key
        case "variation 2":
            // The visitor has been bucketed with variation 1 key
        default:
            //The visitor has been bucketed with the default variation or is part of the unallocated traffic sample
    }
} catch {
    switch error {
        case KameleoonError.sdkNotReady:
            // Exception indicating that the SDK has not completed its initialization yet.
        case KameleoonError.Feature.notFound:
		    // The feature key is not in the configuration file that has been fetched by the SDK. Trigger the old checkout for this visitor.
        case KameleoonError.Feature.environmentDisabled:
		    // The feature flag is disabled for the environment.
        default:
            // Any other error.
    }
}

getFeatureList()​

Returns a list of feature flag keys currently available for the SDK.

Return value​
TypeDescription
[String]List of feature flag keys
Example code​
let allFeatureList = kameleoonClient.getFeatureList()

getActiveFeatureList()​

note

This method is deprecated and will be removed in SDK version 5.0.0. Use getVariations() instead.

To get the list of feature flag keys currently available and active for the visitor.

Return value​
TypeDescription
[String]List of feature flag keys which are active for the visitor
Example code​
let activeFeatureFlags = kameleoonClient.getActiveFeatureList()

getActiveFeatures()​

note

This method is deprecated and will be removed in SDK version 5.0.0. Use getVariations() instead.

getActiveFeatures method retrieves information about the active feature flags that are available for the specified visitor code.

Return value​
TypeDescription
[String: Types.Variation]A dictionary that contains the visitor's assigned variations for each active feature using the keys of the corresponding active features.
Example code​
let activeFeatures = kameleoonClient.getActiveFeatures()

setForcedVariation()​

The method allows you to programmatically assign a specific Variation to a user, bypassing the standard evaluation process. This is especially valuable for controlled experiments where the usual evaluation logic is not required or must be skipped. It can also be helpful in scenarios like debugging or custom testing.

When a forced variation is set, it overrides Kameleoon's real-time evaluation logic. Processes like segmentation, targeting conditions, and algorithmic calculations are skipped. To preserve segmentation and targeting conditions during an experiment, set forceTargeting=false instead.

A forced variation is treated the same as an evaluated variation. It is tracked in analytics and stored in the user context like any standard evaluated variation, ensuring consistency in reporting.

The method may throw exceptions under certain conditions (e.g., invalid parameters, user context, or internal issues). Proper exception handling is essential to ensure that your application remains stable and resilient.

let experimentId = 9516
do {
    // Forcing the variation "on" for the experiment 9516 for the visitor
    try kameleoonClient.setForcedVariation(experimentId: experimentId, variationKey: "on")

    // Forcing the variation "on" while preserving segmentation and targeting conditions during the experiment
    try kameleoonClient.setForcedVariation(experimentId: experimentId, variationKey: "on", foceTargeting: false)

    // Resetting the forced variation for the experiment 9516 for the visitor
    try kameleoonClient.setForcedVariation(experimentId: experimentId, variationKey: nil);
} catch {
    // Handling the exception
}
Arguments​
NameTypeDescriptionDefault
experimentId (required)IntExperiment Id that will be targeted and selected during the evaluation process.
variationKey (required)StringVariation Key corresponding to a Variation that should be forced as the returned value for the experiment. If the value is nil, the forced variation will be reset.
forceTargeting (optional)BoolIndicates whether targeting for the experiment should be forced and skipped (true) or applied as in the standard evaluation process (false).true
Errors thrown​
TypeDescription
KameleoonError.sdkNotReadyException indicating that the SDK is not fully initialized yet.
KameleoonError.Feature.experimentNotFoundException indicating that the requested experiment id has not been found in the SDK's internal configuration. This is usually normal and means that the rule's corresponding experiment has not yet been activated on Kameleoon's side.
KameleoonError.Feature.variationNotFoundException indicating that the requested variation key(id) has not been found in the internal configuration of the SDK. This is usually normal and means that the variation's corresponding experiment has not yet been activated on Kameleoon's side.
info

In most cases, you only need to handle the basic error, KameleoonError/KameleoonError.Feature, as demonstrated in our example. However, if you need to respond to different types of errors, you can handle each one separately based on your requirements. Additionally, for enhanced reliability, you can (or should) also handle general language errors by including Error.

Variables​

getFeatureVariable()​

  • 📨 Sends Tracking Data to Kameleoon
note
  • This method is deprecated and will be removed in SDK version 5.0.0. Use getVariation() instead.
  • This method was previously named obtainFeatureVariable(), which was removed in SDK version 4.0.0.

Call this method to get the feature variable of a variation key associated with a user.

This method takes featureKey, and variableKey as required arguments to get the variable of the variation key for a given user.

If a visitor has never been associated with this feature flag, the SDK returns a variable value for the variation key that it randomly assigns according to the feature flag rules. If the user is already registered with this feature flag, the SDK returns the variable value for previously associated variation. If the user does not match any of the rules, the default variable is returned.

String featureKey = "myFeature"
String variableKey = "myVariable"

try {
	let variable = kameleoonClient.getFeatureVariable(featureKey: featureKey, variableKey: variableKey)
    // your custom code, depending on variableValue
} catch {
    switch error {
        case KameleoonError.sdkNotReady:
            // Exception indicating that the SDK has not completed its initialization yet.
        case KameleoonError.Feature.notFound:
		    // The Feature Key is not in the configuration file that has been fetched by the SDK. Trigger the old checkout for this visitor.
        case KameleoonError.Feature.environmentDisabled:
		    // The feature flag is disabled for the environment.
        case KameleoonError.Feature.variableNotFound:
            // Exception indicating that the requested variable has not been found. Check that the variable's key matches the one in your code.

        default:
            // Any other error.
    }
}
Arguments​
NameTypeDescription
featureKeyStringIdentification key of the feature you want to retrieve. This field is required.
variableKeyStringName of the variable you want to get a value for. This field is required.
Return value​
TypeDescription
AnyData associated with this feature flag. The values can be Int, String, Bool or Dictionary (depending on the type defined on the web interface).
Errors thrown​
TypeDescription
KameleoonError.sdkNotReadyException indicating that the SDK is not fully initialized yet.
KameleoonError.Feature.notFoundException indicating that the requested feature ID has not been found in the internal configuration of the SDK. This usually means that the feature flag has not yet been activated on Kameleoon's side (but code implementing the feature is already deployed in the web-application).
KameleoonException.Feature.environmentDisabledException indicating that the feature flag is disabled for the visitor's current environment (for example, production, staging, or development).
KameleoonError.Feature.variableNotFoundException indicating that the requested variable wasn't found. Check that the variable's key in the Kameleoon app matches the one in your code.

getFeatureVariationVariables()​

note
  • This method is deprecated and will be removed in SDK version 5.0.0. Use getVariation() instead.
  • This method was previously named: getFeatureAllVariables, which was removed in SDK version 4.0.0 release.

To retrieve all of the variables for a feature, call this method. You can modify your feature variables in the Kameleoon app.

This method takes one argument, featureKey. It returns the data with the [String: Any] type, as defined on the web interface. It will throw an exception (KameleoonError.Feature.notFound) if the requested feature has not been found in the internal configuration of the SDK.

let featureKey = "myFeature"
let variationKey = "on"

do {
	allVariables = try kameleoonClient.getFeatureVariationVariables(featureKey: featureKey, variationKey: variationKey);
} catch KameleoonError.Feature.notFound {
	// The feature is not activated in Kameleoon.
} catch KameleoonError.Feature.environmentDisabled {
	// The feature flag is disabled for the environment.
} catch  {
    // This is a generic Exception handler that will handle all errors.
}
Arguments​
NameTypeDescription
featureKeyStringIdentification key of the feature you want to retrieve. This field is required.
variationKeyStringThe key of the variation you want to retrieve. This field is required.
Return value​
TypeDescription
[String: Any]Data associated with this feature flag. The values can be Int, String, Bool or Dictionary (depending on the type defined on the web interface).
Errors thrown​
TypeDescription
KameleoonError.sdkNotReadyException indicating that the SDK is not fully initialized yet.
KameleoonError.Feature.notFoundException indicating that the requested feature ID has not been found in the internal configuration of the SDK. This usually means that the feature flag has not been activated in the Kameleoon app (but code implementing the feature is already deployed in the web application).
KameleoonException.Feature.environmentDisabledException indicating that the feature flag is disabled for the visitor's current environment (for example, production, staging, or development).
KameleoonError.Feature.variationNotFoundException indicating that the requested variation key has not been found in the internal configuration of the SDK. This means that the feature flag has not yet been retrieved by the SDK. This may happen if the SDK is in polling mode.
Example code​
let featureKey = "myFeature"
let variationKey = "on"

do {
	allVariables = try kameleoonClient.getFeatureVariationVariables(featureKey: featureKey, variationKey: variationKey);
} catch KameleoonError.Feature.notFound {
	// The feature is not activated in Kameleoon.
} catch KameleoonError.Feature.environmentDisabled {
	// The feature flag is disabled for the environment.
} catch  {
    // This is a generic Exception handler that will handle all errors.
}

Goals​

trackConversion()​

  • 📨 Sends Tracking Data to Kameleoon

Use this method to track conversions. This method requires goalId to track conversion on this particular goal. In addition, this method also accepts revenue as a third optional argument to track revenue.

The trackConversion() method doesn't return any value. This method is non-blocking as the server call is made asynchronously.

let goalId = 83023
kameleoonClient.trackConversion(goalId: goalId, revenue: 10.0)
Arguments​
NameTypeDescription
goalIdIntID of the goal. This field is required.
revenueFloatRevenue of the conversion. This field is optional.
Errors thrown​
TypeDescription
KameleoonError.sdkNotReadyError indicating that the SDK has not completed its initialization yet.

Events​

updateConfigurationHandler()​

The updateConfigurationHandler() method allows you to handle the event when configuration has updated data. It takes one input parameter, handler. The handler that will be called when the configuration is updated using a real-time configuration event.

kameleoonClient.addData(CustomData(id: 20, values: "true", "20"))
kameleoonClient.addData(Conversion(goalId: 32, revenue: 10.0, negative: false))
kameleoonClient.flush()
Arguments​
NameTypeDescription
handlerOptional<(() -> Void)>The handler that will be called when the configuration is updated using a real-time configuration event.
kameleoonClient.updateConfigurationHandler {
  // configuration was updated
}

Visitor data​

visitorCode​

Returns unique visitor code used in SDK.

let visitorCode = kameleoonClient.visitorCode
Return value​
TypeDescription
StringString representing a unique visitor code used in SDK.

addData()​

The addData() method adds targeting data to storage so other methods can use the data to decide whether or not to target the current visitor.

The addData() method does not return any value and does not interact with Kameleoon back-end servers on its own. Instead, all the declared data is saved for future transmission using the flush() method. This approach reduces the number of server calls made, as the data is typically grouped into a single server call that is triggered the flush().

The trackConversion() method also sends out any previously associated data, just like the flush(). The same holds true for getVariation() and getVariations() methods if an experimentation rule is triggered.

tip

Each visitor can only have one instance of associated data for most data types. However, CustomData is an exception. Visitors can have one instance of associated CustomData per index.

kameleoonClient.addData(CustomData(id: 20, values: "true", "20"))
kameleoonClient.addData(Conversion(goalId: 32, revenue: 10.0, negative: false))

kameleoonClient.addData([
    CustomData(id: 20, values: "true", "20"),
    Conversion(goalId: 32)
])
Arguments​
NameTypeDescription
data (required)Kameleoon.../[KameleoonData]Collection of Kameleoon data types.

flush()​

  • 📨 Sends Tracking Data to Kameleoon

The flush() method collects the Kameleoon data linked to the visitor. It then sends a tracking request, along with all data added using the addData method, which has not yet been sent using one of these methods. flush() is non-blocking as the server call is made asynchronously.

flush allows you to control when data associated with a given visitorCode is sent to our servers. For instance, if you call addData() a dozen times, it would be inefficient to send data to the server each time addData() is invoked. So, all you have to do is call flush() once.

Arguments​
NameTypeDescription
instantBoolBoolean flag indicating whether the data should be sent instantly (true) or according to the default tracking interval (false) set with the SDK parameter trackingIntervalMillisecond in KameleoonClientConfig or tracking_interval_millisecond. This field is optional.
Errors thrown​
TypeDescription
KameleoonError.sdkNotReadyError indicating that the SDK has not completed its initialization yet.
kameleoonClient.addData(CustomData(id: 20, values: "true", "20"))
kameleoonClient.addData(Conversion(goalId: 32, revenue: 10.0, negative: false))

kameleoonClient.flush() // Interval tracking (most performant way for tracking)
kameleoonClient.flush(instant: true) // Instant tracking

getRemoteData()​

  • 🔄 Performs an asynchronous request
note

This method was previously called retrieveDataFromRemoteSource, which was removed in SDK version 4.0.0 release.

Use this method to retrieve data from a remote Kameleoon server based on your active siteCode and the key argument (or the active visitorCode if you omit the key). The visitorCode and siteCode are specified in KameleoonClientFactory.create(). You can quickly and conveniently store data on our highly scalable remote servers using the Kameleoon Data API. Your application can then retrieve the data using this method.

caution

Since a server call is required, this mechanism is asynchronous. Therefore, you should either:

  • Provide a completion callback as an argument to the method to ensure you are notified when the data has been successfully fetched.
  • Use asynchronous operations.
struct Test1: Decodable {
  let value: String

  private enum CodingKeys: String, CodingKey {
    case value = "json_value"
  }
}

kameleoonClient.getRemoteData(key: "test") { (result: Result<Test1, Error>) in
    switch result {
        case .success(let test1):
            // test1 is a decoded value for Test1 type
        case .failure:
            // error includes informaion about request's failure
    }
}

kameleoonClient.getRemoteData(key: "test") { (data: Result<Data, Error>) in
    switch result {
        case .success(let data):
            if let json = try JSONSerialization.jsonObject(with: data) as? [String: Any] {
                print(json)
            }
        case .failure:
            // error includes informaion about request's failure
    }
}
Arguments​
NameTypeDescriptionDefault
key (optional)StringThe key that the data you try to get is associated with.""
completion (required)(Result<T: Decodable, Error>) -> VoidThe callback that processes the received data.

getRemoteVisitorData()​

  • 🔄 Performs an asynchronous request

getRemoteVisitorData() is an asynchronous method for retrieving Kameleoon Visits Data for the visitor from the Kameleoon Data API. The method adds the data to storage for other methods to use when making targeting decisions.

Data obtained using this method plays an important role when you want to:

  • use data collected from other devices.
  • access a user's history, such as custom data collected during previous visits.

Read this article for a better understanding of possible use cases.

caution

By default, getRemoteVisitorData() automatically retrieves the latest stored custom data with scope=Visitor and attaches them to the visitor without the need to call the method addData(). It is particularly useful for synchronizing custom data between multiple devices.

Since a server call is required, this mechanism is asynchronous. Therefore, you should either:

  • Provide a completion callback as an argument to the method to ensure you are notified when the data has been successfully fetched and added to the visitor.
  • Use asynchronous operations.

We recommend checking only for failed results. However, if necessary, you can verify that the data has been added to the visitor and is available for targeting purposes (or for debugging, though it is better to use logging for debugging). Additionally, you can manage the data manually if the addData=false parameter is passed.

// Fetch visitor data and automatically add it
kameleoonClient.getRemoteVisitorData { result in
    switch result {
        case .success(let visitorData):
            // visitorData includes all retrieved data that was added for the visitor
        case .failure:
            // Handle the error, which contains information about the request failure
    }
}

// Fetch visitor data without automatically adding it
kameleoonClient.getRemoteVisitorData(addData: false) { result in
    switch result {
        case .success(let visitorData):
            // visitorData includes all retrieved data that was added for the visitor
        case .failure:
            // Handle the error, which contains information about the request failure
    }
}

// Fetch a custom list of data types
let filter = Types.RemoteVisitorDataFilter(
    previousVisitAmount: 25, currentVisit: true, conversions: true, experiments: true, geolocation: true
)
kameleoonClient.getRemoteVisitorData(filter: filter) { result in
    switch result {
        case .success(let visitorData):
            // visitorData includes all retrieved data that was added for the visitor
        case .failure:
            // Handle the error, which contains information about the request failure
    }
}
Arguments​
NameTypeDescriptionDefault
filter (optional)RemoteVisitorDataFilterFilter that selects which data should be retrieved from visit history. By default, the method retrieves CustomData from the current and latest previous visit.RemoteVisitorDataFilter.default
addData (optional)BooleanA boolean indicating whether the method should automatically add retrieved data for a visitor.true
completion (required)(Result<[KameleoonData], Error>) -> VoidThe callback that processes the received visitor data.
Using parameters of RemoteVisitorDataFilter​

The getRemoteVisitorData() method offers flexibility by allowing you to define various parameters when retrieving data on visitors. Whether you're targeting based on goals, experiments, or variations, the same approach applies across all data types.

For example, let's say you want to retrieve data on visitors who completed a goal "Order transaction". You can specify parameters within the getRemoteVisitorData() method to refine your targeting. For instance, if you want to target only users who converted on the goal in their last five visits, you can set the previousVisitAmount parameter to 5 and conversions to true.

The flexibility shown in this example is not limited to goal data. You can use parameters within the getRemoteVisitorData() method to retrieve data on a variety of visitor behaviors.

note

Here is the list of available Types.RemoteVisitorDataFilter options:

NameTypeDescriptionDefault
previousVisitAmount (optional)IntNumber of previous visits to retrieve data from. Number between 1 and 251
currentVisit (optional)BoolIf true, current visit data will be retrievedtrue
customData (optional)BoolIf true, custom data will be retrieved.true
conversions (optional)BoolIf true, conversion data will be retrieved.false
experiments (optional)BoolIf true, experiment data will be retrieved.false
geolocation (optional)BoolIf true, geolocation data will be retrieved.false
kcs (optional)BoolIf true, Kameleoon Conversion Score (KCS) will be retrieved. Requires the AI Predictive Targeting add-onfalse
visitorCode (optional)BoolIf true, Kameleoon will retrieve the visitorCode from the most recent visit and use it for the current visit. This is necessary if you want to ensure that the visitor, identified by their visitorCode, always receives the same variant across visits for Cross-device experimentation.true
personalization (optional)BoolIf true, personalization data will be retrieved. This is required for the personalization conditionfalse

getVisitorWarehouseAudience()​

  • 🔄 Performs an asynchronous request

Retrieves all audience data associated with the visitor in your data warehouse. The optional warehouseKey parameter is typically your internal user ID. The customDataIndex parameter corresponds to the Kameleoon custom data that Kameleoon uses to target your visitors. You can refer to the warehouse targeting documentation for additional details.

caution

Since a server call is required, this mechanism is asynchronous. Therefore, you should either:

  • Provide a completion callback as an argument to the method to ensure you are notified when the data has been successfully fetched and added to the visitor.
  • Use coroutines for asynchronous handling.

We recommend checking only for failed results. However, if necessary, you can verify that the data has been added to the visitor and is available for targeting purposes (or for debugging, though it is better to use logging for debugging).

// Fetch visitor warehouse audience data
kameleoonClient.getVisitorWarehouseAudience(customDataIndex: 10) { result in
    switch result {
        case .success(let customData):
            // Data was added. You can access it from `customData`
        case .failure:
            // Handle the error, which contains information about the request failure
    }
}

// Fetch visitor warehouse audience data with a specific warehouse key
kameleoonClient.getVisitorWarehouseAudience(
    warehouseKey: "warehouseKey", customDataIndex: 10
) { result in
    switch result {
        case .success(let customData):
            // Data was added. You can access it from `customData`
        case .failure:
            // Handle the error, which contains information about the request failure
    }
}
Arguments​
NameTypeDescriptionDefault
warehouseKey (optional)StringThe unique key to identify the warehouse data (usually, your internal user ID).""
customDataIndex (required)IntAn integer representing the index of the custom data you want to use to target your BigQuery Audiences.
completion(Result<CustomData, Error>) -> VoidThe callback that processes the received data.

setLegalConsent()​

You must use this method to specify whether the visitor has given legal consent to use their personal data. Setting the legalConsent parameter to false limits the types of data that you can include in tracking requests. This helps you adhere to legal and regulatory requirements while responsibly managing visitor data. You can find more information on personal data in the consent management policy.

Arguments​
NameTypeDescription
legalConsentbooleanA boolean value representing the legal consent status. true indicates the visitor has given legal consent, false indicates the visitor has never provided, or has withdrawn, legal consent. This field is required.
Example code​
kameleoonClient.setLegalConsent(true)

Data types​

This section lists the data types supported by Kameleoon. We provide several standard data types as well as the CustomData type that allows you to define custom data types.

Conversion​

Store information about conversion events.

NameTypeDescription
goalIDStringID of the goal. This field is required.
revenueFloatConversion revenue. This field is optional.
negativeBoolDefines if the revenue is positive or negative. This field is optional.
Example code​
try? kameleoonClient.addData(Conversion(goalId: 32, revenue: 10.0, negative: false))

CustomData​

Define your own custom data types in the Kameleoon app or the Data API and use them from the SDK.

NameTypeDescription
indexIntThe index a (a unique ID) of the custom data to store. This field is required.
valueStringValue of the custom data to store. This field is required.
valuesString... or [String]Value(s) of the custom data to store.
note

You can find the index (ID) for your custom data in the Kameleoon app, in the Custom data configuration page. Be careful: this index starts at 0, so the first custom data you create for a given site has an ID value of 0, not 1.

Example code​
try? kameleoonClient.addData(CustomData(id: 1, value: "some custom value"))

try? kameleoonClient.addData(CustomData(id: 1, value: "first value", "second value"))

try? kameleoonClient.addData(CustomData(id: 1, values: ["first value", "second value"]))

Device​

Store information about the user's device.

NameTypeDescription
deviceDeviceList of devices: phone, tablet, desktop. This field is required.
Example code​
try? kameleoonClient.addData(Device.desktop);

Geolocation​

Geolocation contains the visitor's geolocation details.

tip
  • Each visitor can have only one Geolocation. Adding a second Geolocation overwrites the first one.
kameleoonClient.addData(Geolocation(country: "France", region: "Île-de-France", city: "Paris"));
NameTypeDescription
country (required)StringThe country of the visitor.
region (optional)String?The region of the visitor.
city (optional)String?The city of the visitor.
postalCode (optional)String?The postal code of the visitor.
latitude (optional)Double?The latitude coordinate representing the location of the visitor. Coordinate number represents decimal degrees.
longitude (optional)Double?The longitude coordinate representing the location of the visitor. Coordinate number represents decimal degrees.

Returned Types​

Variation​

Variation contains information about the assigned variation to the visitor (or the default variation, if no specific assignment exists).

NameTypeDescription
keyStringThe unique key identifying the variation.
idIntThe ID of the assigned variation (or -1 if it's the default variation).
experimentIdIntThe ID of the experiment associated with the variation (or -1 if default).
variables[String: Variable]A map containing the variables of the assigned variation, keyed by variable names. This could be an empty collection if no variables are associated.
note
  • The Variation object provides details about the assigned variation and its associated experiment, while the Variable object contains specific details about each variable within a variation.
  • Ensure that your code handles the case where id or experimentId may be -1, indicating a default variation.
  • The variables map might be empty if no variables are associated with the variation.
Example code​
// Retrieving the variation key
let variationKey: String = variation.key

// Retrieving the variation id
let variationId: Int = variation.id

// Retrieving the experiment id
let experimentId: Int = variation.experimentId

// Retrieving the variables map
let variables: [String: Variable] = variation.variables

Variable​

Variable contains information about a variable associated with the assigned variation.

NameTypeDescription
keyStringThe unique key identifying the variable.
typeStringThe type of the variable. Possible values: BOOLEAN, NUMBER, STRING, JSON.
valueAny?The value of the variable, which can be of the following types: Bool, Int, Double, String, [String: Any] (json object), [Any] (json array).
Example code​
// Retrieving the variables map
let variables: [String: Variable] = variation.variables

// Variable type can be retrieved for further processing
let type: String = variables["isDiscount"]?.type ?? ""

// Retrieving the variable value by key
let isDiscount: Bool = variables["isDiscount"]?.value as? Bool ?? false

// Variable value can be of different types
let title: String = variables["title"]?.value as? String ?? ""