4.24.1. See the C# SDK changelog for release notes, or the SDK changelog index for all SDKs.
Developer guide
Getting started
This guide helps you integrate the SDK into your C# applications.Starter kit
To help with getting started, Kameleoon provides a starter kit and demo app to test the SDK. The starter kit includes a fully configured app with examples that demonstrate how to use SDK methods in an app. The starter kit, demo app, and detailed instructions are available at Starter kit for .NETInstall the C# client
You can use the NuGet, .NET CLI, or Paket package manager to install the C# client.- NuGet Package Manager
- .NET CLI
- Paket CLI
Additional configuration
Create a.properties configuration file to provide credentials and customize the SDK’s behavior. You can also download a sample configuration file. Save this file in the default path /etc/kameleoon/client-csharp.conf. If you place the file in another location, you’ll need to pass the path as an argument to KameleoonClientFactory.Create(). With the current version of the C# SDK, these are the available keys:
Initialize the Kameleoon client
After you’ve installed the SDK and configured your credentials and SDK behavior, create the Kameleoon client in your app code. For example:IKameleoonClient is a singleton object that connects your app to the Kameleoon platform. It includes all the methods and features you need to run an experiment.
As a developer, you must ensure your app uses the correct logic for A/B testing with Kameleoon. Exclude a visitor from the experiment if you haven’t launched it yet. Excluding fits the default logic for variations, so it’s simple.
Activating a feature flag
Assigning a unique ID to a user
To assign a unique ID to a user, you can use theGetVisitorCode() method. If a visitor code doesn’t exist (from the request headers cookie), the method generates a random unique ID or uses a defaultVisitorCode that you would have generated. The ID is then set in a response headers cookie.
If you are using Kameleoon in Hybrid mode, calling the GetVisitorCode() method ensures that the app file engine.js (previously named, kameleoon.js) and the SDK share the unique ID (visitor code).
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 theGetVariation() 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.
You can use the IsFeatureActive() method 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 feature flag targets the user, finds the visitor’s assigned variation, and saves it to storage. When track=true, the SDK sends the exposure event to the specified experiment on the next tracking request, which it triggers automatically based on the SDK’s tracking_interval_millisecond. The default interval is 1000 milliseconds (1 second).
The GetVariation() method allows you to control whether the SDK tracks the visitor. If track=false, the SDK sends no exposure events. This option 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 theAddData() method to add these data points to the user’s profile.
To retrieve data points collected on other devices or to access past user data (collected client-side when using Kameleoon in Hybrid mode), use the GetRemoteVisitorData() method. This method asynchronously fetches data from the servers. It’s important to call GetRemoteVisitorData() before retrieving the variation or checking if the feature flag is active, because the SDK might need this data to assign a user to a given variation.
To learn more about available targeting conditions, see the 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 and browser. Kameleoon Hybrid mode automatically collects a variety of data points on the client-side, making it easy to break down your results based on these pre-collected data points. 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.
To ensure your results are accurate, it’s recommended to filter out bots by using the
UserAgent data type.Tracking goal conversions
When a user completes a desired action (such as making a purchase), it’s recorded as a conversion. To track conversions, use theTrackConversion() method and provide the required visitorCode and goalId parameters.
The SDK sends the conversion tracking request along with the next scheduled tracking request, which occurs 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.
Sending events to analytics solutions
To track conversions and send exposure events to your customer analytics solution, you must first implement Kameleoon in Hybrid mode. Then, use theGetEngineTrackingCode() method.
The GetEngineTrackingCode() method retrieves the unique tracking code required to send exposure events to your analytics solution. Using this method allows you to record events and send them to your desired analytics platform.
Error handling
Every error the SDK raises is aKameleoonException, so a single handler for that type catches every SDK failure. Handle a specific error type when your app needs to react to a particular failure, for example to fall back to your default behavior when a feature flag isn’t in the configuration or the SDK isn’t initialized yet. The reference section of each method lists the errors it can raise.
The SDK throws errors as exceptions. KameleoonException derives from Exception, and every specific error is a nested class of it, so you can catch a single error such as KameleoonException.FeatureNotFound, or the base KameleoonException. Asynchronous methods such as WaitInit() don’t throw synchronously: the returned Task faults with the error, which await rethrows (.Wait() and .Result wrap it in an AggregateException).
SDK errors are expected behavior, not crashes: a feature flag that isn’t activated yet, an SDK that is still loading its configuration, or a network failure are all normal conditions. When feature evaluation fails, log the error and fall back to your default behavior so the visitor still gets a working experience.
Cross-device experimentation
To support visitors who access an app from multiple devices, Kameleoon allows the synchronization of previously collected visitor data across each of the visitor’s devices and reconciliation of their visit history across devices through cross-device experimentation. Case studies and detailed information on how Kameleoon handles data across devices are available in the article on cross-device experimentation.Synchronizing custom data across devices
Although custom mapping synchronization aligns visitor data across devices, it’s not always necessary. Below are two scenarios where custom mapping sync isn’t required: Same user ID across devices If you use the same user ID consistently across all devices, the SDK handles synchronization automatically without a custom mapping sync. It’s enough to call theGetRemoteVisitorData() 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’s assumed that you use the same unique identifier (in this case, the visitorCode, also known as userId) consistently between the two devices for accurate data retrieval.
If you want to sync collected data in real time, you need to choose the scope Visitor for your custom data.
Device A
Device B
Using custom data for session merging
Cross-device experimentation allows for combining a visitor’s history across each of their devices (history reconciliation). History reconciliation allows merging different visitor sessions into one. To reconcile visit history, useCustomData to provide a unique identifier for the visitor. For more information, see the dedicated documentation.
After you enable cross-device reconciliation, calling GetRemoteVisitorData() with the parameter userId retrieves all known data for a given user.
Sessions with the same identifier always see 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. The cross-device experimentation documentation outlines these limitations.
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 addedUniqueIdentifier(true)- to retrieve data for all linked visitors.TrackConversion()orFlush()with addedUniqueIdentifier(true)data - to track some data for specific visitor that’s associated with another visitor.
GetVisitorCode() method. After the user logs in, the app associates the anonymous visitor with the user ID and uses it as a unique identifier for the visitor.
Using a custom bucketing key
By default, Kameleoon uses a unique, anonymous visitor ID (visitorCode) to assign users to feature flag variations. This ID is typically generated and stored on the user’s device (in a browser cookie for client-side and server-side SDKs, and in persistent storage for mobile SDKs). However, in certain scenarios you may need to ensure all users of the same organization see the same variant of a feature flag.
The Custom Bucketing Key option allows you to override this default behavior by providing your own custom identifier for bucketing. This override ensures that Kameleoon’s assignment logic uses your specified key instead of the default visitorCode.
Use cases
Using a custom bucketing key is essential for maintaining consistency and accuracy in your feature flag assignments, particularly in these situations:- Account-level or organizational experiments: For B2B products or scenarios where you want to assign all users from the same organization to the same variation, you can use an identifier like an
accountId. Custom bucketing keys are crucial for A/B testing features that impact an entire team or company.
Technical details
When you configure a custom bucketing key for a feature flag, you provide Kameleoon with a specific identifier from your app’s data:- Providing the custom key: You provide your custom identifier to the Kameleoon SDK using the
AddData()method. In this method, you will pass your chosen custom bucketing key as aCustomDataobject. Here,newVisitorCoderefers to the identifier you wish to use for your bucketing (for example, the newuserIdoraccountId).
- Bucketing logic: Once you provide a custom bucketing key through the
AddData()method, all hash calculations for assigning users to variations use thisnewVisitorCode(your custom key) instead of the defaultvisitorCode. Using thenewVisitorCodemeans that the bucketing decision depends on your custom identifier, ensuring consistent assignments across various contexts where that identifier is present. - Data tracking and analytics: It’s crucial to note that while the
newVisitorCode(your custom key) is used for bucketing decisions, the SDK sends all subsequent data (tracking events and conversions, for example) and associates it with the originalvisitorCode. This separation ensures that your analytics accurately reflect individual user journeys and interactions within your experiment’s broader context, even when you bucket at a higher level (like an account) or across multiple devices/sessions. Your original visitor data remains intact for comprehensive reporting.
Technical requirements
To effectively use a custom bucketing key:- The key must be a
string. - It must be unique for the entity you intend to bucket (for example, if using a
userId, each user’s ID should be unique). - The key must be available to the SDK at the exact moment it evaluates the feature flag decision for that user or request.
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.Custom handling of logs
The SDK writes its logs to the console output by default. This behaviour can be overridden.The SDK limits logging by log level separately from the log handling logic.
Reference
The sections below document the full C# SDK.Initialization
Create()
To start using the SDK, you need to initialize it. Your app interacts with the SDK through theKameleoonClient class found in Kameleoon.IKameleoonClient. You can create this object using the static method Kameleoon.KameleoonClientFactory Create().
Parameters
Return value
Exceptions thrown
WaitInit()
UseWaitInit() when your app should wait for the Kameleoon client to finish initialization before it evaluates feature flags.
The call returns the result of the configuration fetch: it completes successfully when the client finishes initializing, and fails if the initial configuration fetch fails before the client becomes ready. Background retries continue after that first failure. Once a retry succeeds, subsequent calls return a successful result. If no initialization result is available before the timeout expires, the call fails. If you don’t provide a timeoutMilliseconds value, the SDK uses the default timeout from KameleoonClientConfig.DefaultTimeoutMilliseconds.
Parameters
Return value
Exceptions thrown
IsReady
IsReady checks whether the SDK is ready for use, which means its configuration has been successfully loaded. Unlike WaitInit(), this method returns immediately without blocking or throwing.
Return value
Feature flags and variations
IsFeatureActive()
- 📨 Sends Tracking Data to Kameleoon (depending on the
trackparameter)
This method was previously called
ActivateFeature, which the SDK removed in version 4.0.0.IsFeatureActive method.
This method requires a visitorCode and a featureKey (or featureID) to check if a user can access a specific feature.
If the user has no link to this feature yet, the SDK randomly decides whether to activate it, returning either true (the user can access the feature) or false (the user can’t). If the user with the given visitorCode already has a link to this feature, the system returns the previous value of the featureFlag.
Make sure to include proper error handling in your code, as shown in the example, to catch any potential errors.
If you specify a visitorCode, the IsFeatureActive() method uses it as the unique visitor identifier, which is useful for cross-device experimentation. When you specify a visitorCode and set the isUniqueIdentifier parameter to true, the SDK links the flushed data with the visitor associated with the specified identifier.
Use
UniqueIdentifier instead of the deprecated isUniqueIdentifier parameter.The isUniqueIdentifier parameter can be useful in unique situations. For example, if you can’t access the anonymous visitorCode for a visitor, but you can use an internal ID linked to that visitor through session merging.Kameleoon uses tracking to count sessions and visitors when you call certain methods, such as
IsFeatureActive(), GetVariation() or GetVariations().Use the default true value for the track parameter when you expose visitors to a variation and need to count them. Set the track parameter to false only if you call these methods before you expose visitors.For example, if you call GetVariations() to retrieve all variations before you expose visitors, set the track parameter to false. This setting prevents Kameleoon from prematurely counting a session. You can then trigger tracking later when you explicitly expose the visitor.Kameleoon sends tracking data every second by default. You can configure this interval up to 5 seconds using the tracking interval configuration option. Kameleoon groups tracking events into a single session as long as the interval between events is less than 30 minutes. If more than 30 minutes elapse between tracking events, Kameleoon counts the events as separate sessions. A visit appears in your reports 30 minutes after the last recorded event in the session.Parameters
Return value
Exceptions thrown
GetVariation()
- 📨 Sends Tracking Data to Kameleoon (depending on the
trackparameter)
Variation assigned to a given visitor for a specific feature flag.
This method takes a visitorCode and featureKey as mandatory arguments. The track argument is optional and defaults to true.
It returns the assigned Variation for the visitor. If the visitor isn’t associated with any feature flag rules, the method returns the default Variation for the given feature flag.
Ensure your code includes proper error handling to manage potential exceptions.
The default variation refers to the variation assigned to a visitor when they don’t match any predefined delivery rules for a feature flag. In other words, it’s the fallback variation applied to all users who aren’t targeted by specific rules. It’s represented as the variation in the “Then, for everyone else…” section in a management interface.
Parameters
Return value
Exceptions thrown
GetVariations()
- 📨 Sends Tracking Data to Kameleoon (depending on the
trackparameter)
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 visitorCode as a mandatory argument, while onlyActive and track are optional.
- If you set
onlyActivetotrue, the methodGetVariations()returns feature flag variations only if the visitor isn’t bucketed with theoffvariation. - The
trackparameter controls whether the method tracks the variation assignments. By default, it’strue. If it’sfalse, the method doesn’t track variation assignments.
Variation as values. If the SDK assigns no variation for a feature flag, the method returns the default Variation for that flag.
Implement proper error handling to manage potential exceptions.
The default variation refers to the variation assigned to a visitor when they don’t match any predefined delivery rules for a feature flag. In other words, it’s the fallback variation applied to all users who aren’t targeted by specific rules. It’s represented as the variation in the “Then, for everyone else…” section in a management interface.
Parameters
Return value
Exceptions thrown
GetFeatureList()
This method was previously named
ObtainFeatureList(), which the SDK removed in version 4.0.0.Return value
SetForcedVariation()
The method allows you to programmatically assign a specificVariation to a user, bypassing the standard evaluation process. The method is especially valuable for controlled experiments where the usual evaluation logic isn’t required or you need to skip it. It can also be helpful in scenarios like debugging or custom testing.
When you set a forced variation, it overrides Kameleoon’s real-time evaluation logic. The SDK skips processes like segmentation, targeting conditions, and algorithmic calculations. To preserve segmentation and targeting conditions during an experiment, set forceTargeting=false instead.
Simulated variations always take precedence in the execution order. If a simulated variation calculation starts, the SDK fully processes and completes it first.
Parameters
Exceptions thrown
In most cases, you only need to handle the basic error,
KameleoonException, as the example demonstrates. However, if different types of errors require a response, handle each one separately based on specific requirements. Additionally, for enhanced reliability, you can handle general language errors by including Exception.EvaluateAudiences()
- 📨 Sends Tracking Data to Kameleoon
EvaluateAudiences() after you set or update all relevant visitor data, and just before getting a feature variation or checking a feature flag. This approach ensures that Kameleoon evaluates the visitor against the most current data available, allowing for accurate audience assignment based on all criteria.
After calling this method, you can perform a detailed analysis of segment performance in Audiences Explorer.
Parameters
Exceptions thrown
In most cases, you only need to handle the basic error,
KameleoonException, as the example demonstrates. However, if different types of errors require a response, handle each one separately based on specific requirements. Additionally, for enhanced reliability, you can handle general language errors by including Exception.GetDataFile()
Return value
Visitor data
GetVisitorCode()
This method was previously called
ObtainVisitorCode, which the SDK removed in version 4.0.0.GetVisitorCode() method. This method is crucial in environments where front-end and back-end systems must consistently identify users. Here’s how it works:
- Check for a kameleoonVisitorCode cookie or query parameter in the current HTTP request. If you find one, use that as the visitor identifier and skip the next step.
- If you don’t find a cookie or parameter, either randomly create a new identifier or use the defaultVisitorCode argument if it’s provided. Doing so lets you use your identifiers as visitor codes, making connecting Kameleoon visitors to your own users easier without needing extra look-ups.
- Set the server-side kameleoonVisitorCode cookie using the identifier value. The method returns this identifier value.
The
GetVisitorCode() method allows you to set simulated variations for a visitor. When cookies (from a request or document) contain the key kameleoonSimulationFFData, the method reads the cookie and stores the simulated variations for that visitor; its return value doesn’t change. Subsequent feature evaluations for the visitor, such as GetVariation() and IsFeatureActive(), then bypass the standard evaluation process and return the simulated Variation based on the provided data.You can apply simulations in two ways:- Automatically (recommended): If using Kameleoon Web Experimentation or the SDK in Hybrid mode, Kameleoon creates the cookie automatically when you simulate a variant’s display using the Simulation Panel.
- Manually: Set the
kameleoonSimulationFFDatacookie manually.
- Simulated variations: Affect the overall feature flag result.
- Forced variations: Are specific to an individual experiment.
kameleoonSimulationFFData cookie follows this format:kameleoonSimulationFFData={"featureKey":{"expId":10,"varId":20}}: Simulates the variation withvarIdof experimentexpIdfor the givenfeatureKey.kameleoonSimulationFFData={"featureKey":{"expId":0}}: Simulates the default variation (defined in the Then, for everyone else in Production, serve section) for the givenfeatureKey.
encodeURIComponent.Parameters
Return value
Exceptions thrown
AddData()
TheAddData() 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 doesn’t return any value and doesn’t interact with Kameleoon backend servers on its own. Instead, the SDK saves all the declared data 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’s triggered by 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.
Parameters
Exceptions
Flush()
- 📨 Sends Tracking Data to Kameleoon
Flush() method collects the Kameleoon data linked to the visitor. It then sends a tracking request along with all the data added with the AddData method that the SDK hasn’t yet sent using one of these methods. Flush() is non-blocking because the SDK makes the server call asynchronously.
Flush() lets you control when the SDK sends the data associated with a given visitorCode to the server. For instance, if you call AddData() a dozen times, it would be inefficient to send data to the server after each AddData() call, so all you have to do is call Flush() once at the end.
If you specify a visitorCode, the Flush() method uses it as the unique visitor identifier, which is useful for cross-device experimentation. When you specify a visitorCode and set the isUniqueIdentifier parameter to true, the SDK links the flushed data with the visitor associated with the specified identifier.
Use
UniqueIdentifier instead of the deprecated isUniqueIdentifier parameter.The isUniqueIdentifier parameter can be useful in unique situations. For example, if you can’t access the anonymous visitorCode for a visitor, but you can use an internal ID linked to that visitor through session merging.Parameters
GetRemoteData()
This method was previously named
RetrieveDataFromRemoteSource, which the SDK removed in version 4.0.0.GetRemoteData() is a method that lets you fetch data for a specific siteCode (set in KameleoonClientFactory.create()) from a remote Kameleoon server using a key you provide. The Data API stores this data on Kameleoon servers, which efficiently handle large amounts of data. Keep in mind that because this method involves a server call, it works asynchronously.
Parameters
Return value
Exceptions thrown
GetRemoteVisitorData()
GetRemoteVisitorData() is a method that retrieves Kameleoon visit data for a specific user using their VisitorCode. It works in the background and stores this data for other methods to make targeting decisions.
This data is important for several reasons:
- It helps you use information collected from different devices.
- It allows you to access a user’s history, such as previously visited pages from earlier visits.
- It lets you use data only available on the client side, such as datalayer variables and goals that only track conversions on the front-end.
Use
UniqueIdentifier instead of the deprecated isUniqueIdentifier parameter.The isUniqueIdentifier parameter can be useful in unique situations. For example, if you can’t access the anonymous visitorCode for a visitor, but you can use an internal ID linked to that visitor through session merging.Parameters
Return value
Exceptions thrown
Using parameters in GetRemoteVisitorData()
TheGetRemoteVisitorData() 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, suppose 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 isn’t limited to goal data. You can use parameters within the GetRemoteVisitorData() method to retrieve data on a variety of visitor behaviors.
Here is the list of available
Kameleoon.Types.RemoteVisitorDataFilter options:GetVisitorWarehouseAudience()
This method retrieves all audience data associated with the visitor in your data warehouse using the specifiedvisitorCode and warehouseKey. The warehouseKey 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. The method returns a CustomData object, confirming that the SDK added the data to the visitor and that the data is available for targeting purposes.
Parameters
Return value
Exceptions thrown
SetLegalConsent()
You must use this method to specify whether the visitor has given legal consent to use personal data. Setting thelegalConsent parameter to false limits the types of data that you can include in tracking requests. This method 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.
Parameters
Exceptions thrown
Consent revocation behavior
When you callsetLegalConsent() with consent=false, the SDK doesn’t delete the kameleoonVisitorCode cookie. Instead, it stops extending the cookie’s expiration date, allowing the cookie to persist until it naturally expires.
If your compliance requirements demand the immediate removal of the cookie file upon opt-out, you must delete it manually using your framework’s native cookie management methods. The SDK won’t remove the file automatically.
Goals and third-party analytics
TrackConversion()
- 📨 Sends Tracking Data to Kameleoon
visitorCode and goalId. In addition, this method also accepts an optional revenue, negative and metadata arguments. The visitorCode is usually identical to the one you used when triggering the experiment.
The TrackConversion() method doesn’t return any value. This method is non-blocking because the SDK makes the server call asynchronously.
The parameter
isUniqueIdentifier is deprecated. Use UniqueIdentifier instead.The isUniqueIdentifier can also 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 session merging connects to the anonymous visitor.Parameters
metadata values are accessible through raw data exports and the results page.If you provide the
metadata parameter, Kameleoon uses these specified values for the current conversion instead of what you previously collected using the AddData() method. If you omit the parameter, Kameleoon uses the last tracked values for those CustomData prior to the conversion and within the same visit.Kameleoon will only consider the metadata values that are explicitly passed as parameters to the TrackConversion() method.In the example below, Kameleoon will associate the conversion only with the custom data value explicitly provided as a parameter (here: index 5 with the value ‘Amex Credit Card’).Exceptions
GetEngineTrackingCode()
Kameleoon integrates with several analytics solutions, including Mixpanel, Google Analytics 4, and Segment. To track server-side experiments correctly, call theGetEngineTrackingCode() method after the visitor triggers an experiment. The SDK returns JavaScript queue commands for the experiments that the visitor triggered during the previous 5 seconds. When you insert this code into the page, Engine.js processes the commands and sends the exposure events through the active analytics integration.
Refer to hybrid experimentation for more information on implementing this method.
- To use this feature, implement both the C# SDK and Kameleoon Engine.js. Because this flow uses Engine.js only for tracking, you can install the asynchronous tag before the closing
</body>tag. - If you only want to track experiments in Kameleoon and don’t need to send exposure events to third-party analytics tools, use the JavaScript / TypeScript SDK. This option works well for serverless edge compute platforms. The JavaScript / TypeScript SDK automatically tracks variations when you call
getVisitorCode, as long as you add the corresponding experiment assignments towindow.kameleoonQueue. - You can insert the returned tracking code directly into an HTML
<script>tag.
123456 and 234567 are experiment IDs, and 7890 and 8901 are variation IDs. In your implementation, the SDK generates these values in the returned tracking code.Parameters
Return value
Events
SetEventHandler()
Use this method to register a handler for SDK events. The SDK calls the handler when the selected event occurs. Registering a new handler for the same event type replaces the previous handler. Passingnull as the handler removes the current handler for the selected event type.
- DataFileUpdate
- HttpRequest
Parameters
Data types
Data available in the SDK isn’t available for targeting and reporting in the Kameleoon app until it’s added. For example, add it with theaddData() method.
See use visit history to target users for more information.
If you are in hybrid mode, you can call
GetRemoteVisitorData() to automatically fill all data that Kameleoon collected previously.Kameleoon.Data.IData.
Browser
TheBrowser data set stored here can be used to filter experiment and personalization reports by any value associated with it.
PageView
The index (ID) of the referrer is available in the Back-Office in the Acquisition channel configuration page. Be careful: this index starts at 0, so the first acquisition channel you create for a given site would have the ID 0, not 1.
Conversion
TheConversion data set stored here can be used to filter experiment and personalization reports by any goal associated with it.
CustomData
CustomData allows any type of data to be easily associated with each visitor. You can then use it as a targeting condition in segments or as a filter/breakdown in experiment reports.
To learn more about custom data, refer to this article.
-
Each visitor can have only one
CustomDatafor each uniqueindex. Adding anotherCustomDatawith the sameindexwill replace the existing one. - Find the custom data ‘index’ in the Custom Data dashboard under the “INDEX” column.
- To prevent the SDK from sending data with the selected index to Kameleoon servers for privacy reasons, enable the option: Use this data only locally for targeting purposes when creating custom data.
-
Adding a
CustomDatainstance created with a name when the SDK instance configuration isn’t up to date or the name isn’t registered results in the SDK ignoring the data.
Device
UserAgent
Bot traffic is more likely to affect server-side experiments than client-side experiments. Kameleoon uses the IAB/ABC International Spiders and Bots List to tackle this issue and recognize known bots and spiders. Kameleoon also uses theUserAgent field to filter out bots and other unwanted traffic that might distort your conversion metrics. For more details, see the help article on bot filtering.
If you use internal bots, pass the value curl/8.0 of the userAgent to exclude them from your analytics.
UniqueIdentifier
If you don’t addUniqueIdentifier for a visitor, the SDK uses visitorCode as the unique visitor identifier, which is useful for Cross-device experimentation. When you add UniqueIdentifier for a visitor, the SDK links the flushed data with the visitor associated with the specified identifier.
The isUniqueIdentifier parameter can be useful in unique situations. For example, if you can’t access the anonymous visitorCode for a visitor, but you can use an internal ID linked to that visitor through session merging.
OperatingSystem
OperatingSystem contains information about the operating system on the visitor’s device.
Each visitor can only have one
OperatingSystem. Adding a second OperatingSystem overwrites the first one.Cookie
Cookie contains information about the cookie stored on the visitor’s device.
Each visitor can only have one
Cookie. Adding a second Cookie overwrites the first one.Geolocation
Geolocation contains the visitor’s geolocation details.
ApplicationVersion
ApplicationVersion represents the semantic version number of your application.
Returned types
DataFile
TheDataFile contains the SDK configuration details.
It can be extended with additional information if required by clients. If you need more details, contact your Customer Success Manager.
Variation
Variation contains information about the assigned variation to the visitor (or the default variation if no specific assignment exists).
- The
Variationobject provides details about the assigned variation and its associated experiment, while theVariableobject contains specific details about each variable within a variation. - Ensure that your code handles the case where
IdorExperimentIdmay beVariation.UndefinedId, indicating a default variation. - The
Variablesdictionary might be empty if the variation has no variables.
Variable
Variable contains information about a variable associated with the assigned variation.
Deprecated methods
GetFeatureVariationKey()
- 📨 Sends Tracking Data to Kameleoon
GetFeatureVariationKey().
Use
GetVariation() instead.visitorCode, the GetFeatureVariationKey() method uses it as the unique visitor identifier, which is useful for cross-device experimentation. When you specify a visitorCode and set the isUniqueIdentifier parameter to true, the SDK links the flushed data with the visitor associated with the specified identifier.
Use
UniqueIdentifier instead of the deprecated isUniqueIdentifier parameter.The isUniqueIdentifier parameter can be useful in unique situations. For example, if you can’t access the anonymous visitorCode for a visitor, but you can use an internal ID linked to that visitor through session merging.Parameters
Return value
Exceptions thrown
GetActiveFeatureListForVisitor()
- Use
GetActiveFeaturesinstead. - This method was previously called
ObtainFeatureListForVisitorCode(), which the SDK removed in version4.0.0.
visitorCode parameter. Return only the active feature flags for the specified visitor.
Parameters
Return value
GetFeatureVariable()
- 📨 Sends Tracking Data to Kameleoon
Use
GetVariation() instead.GetFeatureVariable() method of the SDK.
This method requires a visitorCode and a featureKey (or featureID) to check if a user can access a specific feature.
If the user has no link to this feature yet, the SDK randomly decides whether to activate it, returning either true (they can access the feature) or false (they can’t). If the user with the given visitorCode already has a link to this feature, the system returns the previous value of the featureFlag.
Make sure to include proper error handling in your code, as shown in the example, to catch any potential errors.
If you specify a visitorCode, the GetFeatureVariable() method uses it as the unique visitor identifier, which is useful for cross-device experimentation. When you specify a visitorCode and set the isUniqueIdentifier parameter to true, the SDK links the flushed data with the visitor associated with the specified identifier.
Use
UniqueIdentifier instead of the deprecated isUniqueIdentifier parameter.The isUniqueIdentifier parameter can be useful in unique situations. For example, if you can’t access the anonymous visitorCode for a visitor, but you can use an internal ID linked to that visitor through session merging.Parameters
Return value
Exceptions thrown
GetActiveFeatures()
Use
GetVariations() instead.GetActiveFeatures method retrieves information about the active feature flags that are available for the specified visitor code.
The
Kameleoon.Types.Variation.Id and Kameleoon.Types.Variation.ExperimentId properties of returned variations are optional. If not specified, the default value is Kameleoon.Types.Variation.UndefinedId.Parameters
Return value
Exceptions thrown
GetFeatureVariationVariables()
- Use
GetVariation()instead. - This method was previously called
GetFeatureAllVariables(), which the SDK removed in version4.0.0.
featureKey and variationKey. It returns the data with the Dictionary<string, object> type, as defined on the web interface. It will throw an exception (KameleoonException.FeatureNotFound) if the SDK’s internal configuration doesn’t contain the requested feature.
Parameters
Return value
Exceptions thrown
UpdateConfigurationHandler()
TheUpdateConfigurationHandler() 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.