Dev guideAPI Reference
Dev guideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

Cross-project events

Describes Optimizely Feature Experimentation cross-project events, which help large optimization teams track consistent, program-level metrics across multiple projects for the Optimizely Feature Experimentation.

An event lives and is tracked only in the project where it was created. Cross-project events help you track key events across all your Optimizely Feature Experimentation projects.

With cross-project events, you can:

  • Use the event as a metric in other projects.
  • Create a set of program-level metrics and reuse them for all your sites.
  • Define metrics for a global component that crosses into property-specific events.



Cross-project events require Optimizely Feature Experimentation SDKs released after February 2021. See SDK compatability matrix.

For example, your company has multiple web properties that are split into separate Optimizely Feature Experimentation projects. One set of program-level metrics manages all properties, such as a key metric to track engagement with the search bar in the enterprise site and all local store sites. To track this same metric in all properties, you would ordinarily have to set it up in every project. You can add the predefined event to any Optimizely Feature Experimentation project with cross-project events.


Cross-project events are intended for scenarios such as the following:

You have two projects:

  • Project 1 – Website.
  • Project 2 – iOS application.

You run an experiment in your iOS application. To measure the performance of this experiment, you want to include an event that is tracked on the website.

For example, you add a "My Account" section to your iOS application, and you want to measure if this new feature influences the number of page views of the "My Account" page on your website. You expect the number of page views on the website to go down because some of your users will now use the new "My Account" feature in the application.

You can add the "Viewed My Account Page" event from Project 1 as a metric to your experiment in Project 2. This does not cause the event to be added to the datafile for Project 2, because the event is still going to be tracked on the website. That is where the event lives and is tracked.

The cross-project part is that the conversions tracked in Project 1 can be added as a metric in Project 2. The event cannot be tracked in Project 2; that is only possible using the datafile from Project 1.

For other scenarios, consider the following suggestions:

  • Initialize the Project 1 datafile in the iOS application as well to track any events from Project 1.
  • Move to a single project for both the website and the app.
  • Use the event API from the app to track any events that go across.

See Track events across platforms for information.

Create a cross-project event

If you have cross-project events, they are automatically enabled in your projects. All your events are cross-project events. Create an event as usual, and it is available in projects for which you have a collaborator role.

Add a cross-project metric

By default, the rules configuration panel shows events in the current project. To include cross-project events:

  1. Go to Flags and select the flag you want.
  2. Under Rules, select your environment and select the experiment you want.
  3. Under Metrics, select All projects.



You will only see cross-project events for which you are a collaborator.

add cross project metric

Click to enlarge image

  1. Select your metrics to add them. Click Save to confirm your changes.

Edit a cross-project event

To edit a cross-project event, you will need to go to the project where it was originally created. To find the project name, look under the event name in the Metrics dropdown in the flag rule configuration panel. Then, follow the steps in Create events to edit your event in the original project.

edit a cross project metric

Click to enlarge image