Optimizely will be sunsetting Full Stack Experimentation on July 29, 2024. See the recommended Feature Experimentation migration timeline and documentation.

Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySumbit a ticketLog In
GitHubNuGetDev CommunitySumbit a ticket

Manage config (datafile)

This topic describes the datafile, which is a JSON representation of your Full Stack project configuration (OptimizelyConfig) in a given environment.

OptimizelyConfig management

The datafile is a JSON representation of your Full Stack project configuration (OptimizelyConfig) in a given environment. It contains all the data needed to deliver and track your flags and experiments. Learn more about the datafile.

You have the following options for synchronizing the datafile between your Optimizely project and your application:

  • (recommended) "Pull" method: Our SDKs provide a polling-based datafile management implementation, handling the fetching of the latest version at whatever frequency you set when you instantiate the SDK.
  • “Push” method: use webhooks to fetch and manage datafiles based on application changes.
  • Custom method: If you need to customize or extend the way you access the datafile for your implementation, you can access the datafile using the Optimzely CDN link. For more information, see Get the datafile.

Other important considerations for datafile management include:

  • Caching and persistence (Optimizely mobile SDKs offer datafile offline caching and persistence).
  • Synchronization between SDK instances (for example, see Multiple SDK languages).
  • Network availability.

📘

Note

To ensure webhook requests originate from Optimizely, secure your webhook using a token in the request header.