Content
Introduction
In this guide, you’ll learn…
Creating and Managing Event Configurations: Setting up recurring events, defining parameters, and configuring activities.
Activity and Parameter Management: Choosing between predefined sets or custom configurations for structured event execution.
Recurrence Setup: Configuring events to repeat based on cooldown periods or weekly schedules, ensuring no overlaps.
Validation & Troubleshooting: Avoiding scheduling conflicts and resolving errors when setting event occurrences.
Event Scheduling with Segment Changes: Handling segment-based scheduling logic using Offset and Weekly recurrence models.
Recurring Event Configuration
Recurring events automate event scheduling by allowing predefined activities and parameters to repeat over time. These events can be configured with fixed cooldown periods or weekly recurrence.
Perform the following steps to configure a Recurring Event :
Navigate to Configurations, and click [+Add Configurations] in the upper right corner.
Click Recurring Event.
Fill in the fields to create a configuration:
See theEvents Fields table for more details.
When you select an Event type, the parameters from event type appear. For recurring events, the recurrence configuration becomes available only after adding activities and configuring their duration.
- Click the [+Serve the configuration to players toggle] to inactivate the configuration. Players will not be served this particular configuration and the parameters section will no longer be displayed.
Default: the toggle is on and the configuration is active and will be served to players.
If a player qualifies for an event where a configuration isn't served, and there is another event of the same type with a higher priority, the player won't receive the second event's configuration, even if the first doesn't serve a configuration.
Activity and Parameter Configuration
Configuring Parameters
When setting parameters for your event, you can either:
Select a Parameter Set :
Choose a pre-defined parameter set to manage consistent configurations across all occurrences of the event.Define Parameters Directly in the Event :
Specify parameter values directly in the event for more customisation.
Selecting a Parameter Set
For parameters , you can select a parameter set, which allows you to manage configurations across different occurrences of the event in a structured manner.
Follow the steps in the Parameter Sets and Activity Sets pages for more details.
Defining Parameters Directly in the Event
You can define specific parameter values directly in the event itself.
The parameters section comprises a list of parameters with Name, Key, Value, Type, and Default Value fields already defined in the event type configuration.
You can modify the pre-defined Value fields however the rest of the fields can only be modified at the time of configuring the event type.
Configuring Activities
When configuring activities for your event, you can either:
Select an Activity Set :
Use a pre-defined activity set to simplify the process by reusing a standard list of activities.Define Activities Directly in the Event :
Create and configure activities directly within the event if custom configurations are required.
Selecting an Activity Set
For activities , you can select an activity set, which allows you to manage configurations across different occurrences of the event in a structured manner.
Follow the steps in the Configuring Parameter Set and Activity Set pages for more details.
Defining Activities Directly in the Event
You can define specific activity values directly in the event itself. Follow the steps in this section for more details.
- From the dropdown, select the _ Same across all occurrences _ option.
A new section will open where you will be able to specify:
Duration : the entire duration of the activity. Based on this duration the recurrence configuration for the events will occur.
The Activity configuration per segment : Click [+Segment] to add a segment.
Select the relevant segment from the dropdown and click [+Add].
Click [+Segment] to add more segments.
Each segment can be served a different activity configuration but the timeline will be the same for all segments.
However, please note that the segments (tabs) are sorted by priority within the activity. If player qualifies for more than one segment, they will have configuration served from their segment with highest priorityActivity Type: Select the relevant activity from the dropdown. See the Configuring Activities page for more information.
Activity Configuration : Select the available configuration for the activity.
Click [+Add Activity] to add more activity configurations.
Adding more than one of the activities allows you to specify the cooldown period between consecutive activities.
The event type can restrict the number of activities that can be added. Once the limit from the event type is reached, the button becomes disabled.
Specify the cooldown time period between activities.
This field is configurable only with more than one activities.Review the Duration Summary
Players are assigned to a segment during the preload, and even if they change segments, they will stay in the previously assigned event until the next preload of an event!
Recurrence configuration becomes available only after setting the durations for all activities. After you’ve configured the activity durations, scroll back up to enable and customise the recurrence settings.
Recurrence Configuration
You can configure event recurrences in two ways:
Cooldown-based: Set a cooldown period between consecutive occurrences.
Weekly-based: Choose specific days of the week for the event to recur.
The following table explains the available fields and steps for each configuration method.
| Field | Description | Default/Options | Steps to Configure |
| --- | --- | --- | --- |
| Limit number of occurrences | Allows you to limit how many times the event occurs. | Default: OFF (unlimited occurrences) | Toggle ON to enable. Enter the number of occurrences (e.g., 5, 10) in the "Number of occurrences" field that appears. |
| Number of Occurrences | Allows you to specify the number of occurrences. | Only available when the Limit Number of occurrences toggle is on. | Specify the number of occurrence for the event. |
| Duration of event occurrence | Displays the total duration of each event cycle (non-editable). | Based on activities and durations set earlier. | No input needed. This field is auto-calculated based on the event's duration (e.g., 10 days). |
| Occurrence Frequency | Allows you to choose how often the event recurs: Cooldown-based or Weekly-based. | Options: Cooldown-based (default), Weekly-based | Select one of the two options: Cooldown-based or Weekly-based. |
| Occurrence Details | Displays the status of the event occurrences. The Next Occurrences are also listed, providing a schedule for when future occurrences of the event will happen. The Refresh button allows you to manually update the list of occurrences. This is important because changes to the configuration are not automatically calculated. | Based on Occurrence configuration | No input needed. This field is auto-calculated |
Cooldown-based Recurrence
Cooldown-based recurrences allow you to define a specific cooldown period between consecutive event occurrences.
This means the event will restart after a defined waiting period, such as 2 days or 12 hours, regardless of the day of the week.
| Field | Description | Default/Options | Steps to Configure |
| --- | --- | --- | --- |
| Cooldown between occurrences | Defines the waiting period between consecutive event occurrences (Cooldown-based). | Days, Hours, Minutes | Input the cooldown period in days, hours, and minutes (e.g., 2 days, 0 hours, 0 minutes). |
Weekly-based Recurrence
Weekly-based recurrences enable you to set specific days of the week on which the event will repeat, such as every Monday and Thursday, or at an interval of every two weeks.
| Field | Description | Default/Options | Steps to Configure |
| --- | --- | --- | --- |
| Start of occurrence | Defines the day(s) of the week the event will start (Weekly-based). | Days of the week: Monday, Tuesday, Wednesday, etc. | Select one or more days for the event to start (e.g., Monday and Thursday). |
| Repeat every [X] weeks | Defines how frequently the event repeats in weeks (Weekly-based). | Default: 1 | Input the number of weeks between recurrences (e.g., to repeat every 2 weeks, enter 2). |
For weekly-based recurring events, the start time of each occurrence will align with the event’s configured start time, not midnight. For example, if an event's start time is set to 10:00 AM, all weekly occurrences will also start at 10:00 AM.
Note: Ensure that the event’s start time is configured correctly to match the desired occurrence start time, as it will automatically propagate to all occurrences.
Validation: Avoid Overlapping Event Occurrences
When configuring an event that recurs on multiple days in a week (e.g., Monday and Thursday), it’s crucial to ensure that the duration of the event does not cause the occurrences to overlap. Overlapping occurs when a new event starts while a previous one is still ongoing.
Scenario:
If your event's duration is long (e.g., 6 days), and you select two or more start days (e.g., Monday and Thursday), and the event repeats every week , the system may detect an overlap between occurrences and prevent saving the event configuration.
Example Configuration:
Event Duration : 6 days
Occurrence Days : Monday and Thursday
Repeat Every : 1 week
With this configuration, the system identifies a conflict because:
First event starts on Monday and lasts for 6 days (Monday to Saturday).
The second event is scheduled to start on Thursday of the same week, which falls within the duration of the first event.
This causes an overlap , as the Thursday occurrence would begin before the Monday occurrence has ended.
System Validation:
As this overlap is detected, the system will display an error message like "Occurrences are overlapping."
The system will not allow you to save the event configuration until the overlap is resolved.
How to Resolve the Overlap:
There are two ways to resolve this issue:
Reduce the Event Duration :
Increase the Time Between Recurrences :
Key Points to Remember :
Ensure that event durations don’t overlap with the next occurrence. Either reduce the event duration or increase the time between recurrences to avoid overlap.
If you select multiple occurrence days in the same week (e.g., Monday and Thursday), ensure that the total event duration allows enough time between these days.
If your occurrences are longer than a week, ensure that you don’t repeat the event every week.
If you receive the “Occurrences are overlapping” error, review your event duration and recurrence settings to make necessary adjustments.
Once you’re done with your configuration, click [Save] on the bottom left side of the screen.
Event Recurrence Logic
Let us understand the event recurrence logic with the help of an example.
Example: Configuring a Recurring Event Every Wednesday and Friday (Every 2 Weeks)
You want to create a recurring event that happens every Wednesday and Friday , repeating every 2 weeks. The event starts on Thursday, 19th September.
Configuration Details
Event Start Date: Thursday, 19th September.
Event Days: Wednesday and Friday.
Recurrence Interval: Every 2 weeks.
Expected Event Occurrences: (When number of occurrences are not limited)
First Event: Friday, 20th September.
Second Event: Wednesday, 2nd October.
Third Event: Friday, 4th October.
Fourth Event: Wednesday, 16th October.
Fifth Event: Friday, 18th October.
Sixth Event: Wednesday, 30th October.
Seventh Event: Friday, 1st November.
How It Works:
The event starts on the first available day after the start date (Friday, 20th September).
A 1-week gap is added after the first event to maintain the recurrence interval of 2 weeks for both event days (Wednesday and Friday).
The week break refers to skipping an entire Monday-to-Sunday week, regardless of how many days pass between the last event and the next. This ensures that events are spaced by full calendar weeks rather than simply counting a set number of days.
The event will occur in the same week (on Wednesday and Friday) every 2 weeks from that point onward.
Event Scheduling Logic with Segment Changes
Let us understand the event scheduling logic when the player changes segments with the help of visual representations of two types of event scheduling logic for recurring events: Offset and Weekly.
Offset Event Scheduling
This type of scheduling applies an offset period between the recurrence of events for different segments.
The diagram shows how the player receives different events based on their segment over the course of a week.
Event Start Date: 1st April 2024
Event End Date: 31st December 2024
Duration: 1 day
Offset: 1 day
Timeline Breakdown:
Monday:
Tuesday:
Wednesday:
Thursday:
Friday:
This configuration demonstrates that after an event occurs for a specific segment, there is a 1-day delay (offset) before the next event is triggered for a new segment. This ensures players in different segments don’t overlap event days immediately after switching.
Weekly Event Scheduling
This configuration follows a weekly schedule for recurring events. In this example, the events are triggered on specific days of the week (Monday and Thursday), and then they repeat weekly.
Event Start Date: 1st April 2024
Event End Date: 31st December 2024
Duration: 1 day
Occurrence Days: Monday and Thursday
Timeline Breakdown:
Monday:
Tuesday & Wednesday:
Thursday:
Friday & Weekend (Saturday-Sunday):
Next Monday:
This configuration shows a more regular and predictable schedule, with events occurring on specific days of the week and repeating according to a defined schedule (e.g., every Monday and Thursday). There are no offsets between different segment events in this type of configuration.
Visibility of Parameter Sets and Activity Sets Based on Event Type Configuration
| Scenario | Parameter Set | Activity Set | Description |
| --- | --- | --- | --- |
| Both parameter set and activity set are configured for the selected event type | ✔ | ✔ | Both parameter set and activity set will appear for the selected event type. |
| Only parameter set is configured for the selected event type | ✔ | ❌ | Only the parameter set will appear for the selected event type. |
| Only parameter set is configured for the selected event type | ❌ | ✔ | Only the activity set will appear for the selected event type. |
| Neither parameter set nor activity set is configured for the selected event type | ❌ | ❌ | Neither parameter set nor activity set will appear for the selected event type. |
If your event is part of an A/B experiment, you can define separate parameter configurations for each variant in the experiment.
On the Parameter Sets page, you can see which events are using each parameter set in the In-Use column.
You cannot delete a parameter set if it is linked to an event with an active or pre-live status.
Chunks 4
# Introduction
In this guide, you’ll learn…
- Creating and Managing Event Configurations: Setting up recurring events, defining parameters, and configuring activities.
- Activity and Parameter Management: Choosing between predefined sets or custom configurations for structured event execution.
- Recurrence Setup: Configuring events to repeat based on cooldown periods or weekly schedules, ensuring no overlaps.
- Validation & Troubleshooting: Avoiding scheduling conflicts and resolving errors when setting event occurrences.
- Event Scheduling with Segment Changes: Handling segment-based scheduling logic using Offset and Weekly recurrence models.
* * *
# Recurring Event Configuration
Recurring events automate event scheduling by allowing predefined activities and parameters to repeat over time. These events can be configured with fixed cooldown periods or weekly recurrence.
Perform the following steps to configure a **Recurring Event** :
1. Navigate to Configurations, and click **[+Add Configurations]** in the upper right corner.
2. Click **Recurring Event**.
3. Fill in the fields to create a configuration:
See the[Events Fields](https://tripledotstudios.atlassian.net/wiki/spaces/KB/pages/3583279198/Configuring+Events#Event-Fields-table) table for more details.
When you select an Event type, the parameters from event type appear. For recurring events, the recurrence configuration becomes available **only after adding activities and configuring their duration.**
1. Click the [**+Serve the configuration to players toggle**] to inactivate the configuration. Players will not be served this particular configuration and the parameters section will no longer be displayed.
Default: the toggle is on and the configuration is active and will be served to players.
If a player qualifies for an event where a configuration isn't served, and there is another event of the same type with a higher priority, the player won't receive the second event's configuration, even if the first doesn't serve a configuration.
**Activity and Parameter Configuration**
### **Configuring Parameters**
When setting parameters for your event, you can either:
1. **Select a Parameter Set** :
Choose a pre-defined parameter set to manage consistent configurations across all occurrences of the event.
2. **Define Parameters Directly in the Event** :
Specify parameter values directly in the event for more customisation.
#### Selecting a Parameter Set
For **parameters** , you can select a parameter set, which allows you to manage configurations across different occurrences of the event in a structured manner.
Follow the steps in the [Parameter Sets](https://tripledotstudios.atlassian.net/wiki/x/agDR9Q) and [Activity Sets](https://tripledotstudios.atlassian.net/wiki/x/DQDS9Q) pages for more details.
#### Defining Parameters Directly in the Event
You can define specific parameter values directly in the event itself.
The parameters section comprises a list of parameters with Name, Key, Value, Type, and Default Value fields already defined in the event type configuration.
You can modify the pre-defined **Value** fields however the rest of the fields can only be modified at the time of configuring the event type.
### **Configuring Activities**
When configuring activities for your event, you can either:
1. **Select an Activity Set** :
Use a pre-defined activity set to simplify the process by reusing a standard list of activities.
2. **Define Activities Directly in the Event** :
Create and configure activities directly within the event if custom configurations are required.
#### **Selecting an Activity Set**
For **activities** , you can select an activity set, which allows you to manage configurations across different occurrences of the event in a structured manner.
Follow the steps in the [Configuring Parameter Set](https://tripledotstudios.atlassian.net/wiki/x/agDR9Q) and Activity Set pages for more details.
#### **Defining Activities Directly in the Event**
You can define specific activity values directly in the event itself. Follow the steps in this section for more details.
1. From the dropdown, select the _ **Same across all occurrences** _ option.
A new section will open where you will be able to specify:
- **Duration** : the entire duration of the activity. Based on this duration the recurrence configuration for the events will occur.
- The **Activity configuration per segment** : Click **[+Segment]** to add a segment.
- Select the relevant segment from the dropdown and click **[+Add].**
- Click **[+Segment]** to add more segments.
Each segment can be served a different activity configuration but the timeline will be the same for all segments.
However, please note that the segments (tabs) are **sorted by priority** within the activity. If player qualifies for more than one segment, they will have configuration served from their segment with highest priority
- **Activity Type:** Select the relevant activity from the dropdown. See the [Configuring Activities](https://tripledotstudios.atlassian.net/wiki/x/CgCy2Q) page for more information.
- **Activity Configuration** : Select the available configuration for the activity.
- Click **[+Add Activity]** to add more activity configurations.
Adding more than one of the activities allows you to specify the cooldown period between consecutive activities.
The event type can restrict the number of activities that can be added. Once the limit from the event type is reached, the button becomes disabled.
- Specify the cooldown time period between activities.
This field is configurable only with more than one activities.
- Review the Duration Summary
**Players are assigned to a segment during the preload, and even if they change segments, they will stay in the previously assigned event until the next preload of an event!**
Recurrence configuration becomes available only after setting the durations for all activities. After you’ve configured the activity durations, scroll back up to enable and customise the recurrence settings.
Recurrence Configuration
You can configure event recurrences in two ways:
- **Cooldown-based:** Set a cooldown period between consecutive occurrences.
- **Weekly-based:** Choose specific days of the week for the event to recur.
The following table explains the available fields and steps for each configuration method.
| **Field** | **Description** | **Default/Options** | **Steps to Configure** |
| --- | --- | --- | --- |
| **Limit number of occurrences** | Allows you to limit how many times the event occurs. | Default: OFF (unlimited occurrences) | Toggle ON to enable. Enter the number of occurrences (e.g., 5, 10) in the "Number of occurrences" field that appears. |
| **Number of Occurrences** | Allows you to specify the number of occurrences. | Only available when the Limit Number of occurrences toggle is on. | Specify the number of occurrence for the event. |
| **Duration of event occurrence** | Displays the total duration of each event cycle (non-editable). | Based on activities and durations set earlier. | No input needed. This field is auto-calculated based on the event's duration (e.g., 10 days). |
| **Occurrence Frequency** | Allows you to choose how often the event recurs: Cooldown-based or Weekly-based. | Options: Cooldown-based (default), Weekly-based | Select one of the two options: Cooldown-based or Weekly-based. |
| **Occurrence Details** | Displays the status of the event occurrences. The **Next Occurrences** are also listed, providing a schedule for when future occurrences of the event will happen. The **Refresh** button allows you to manually update the list of occurrences. This is important because changes to the configuration are **not automatically calculated**. | Based on Occurrence configuration | No input needed. This field is auto-calculated |
#### **Cooldown-based Recurrence**
**Cooldown-based** recurrences allow you to define a specific cooldown period between consecutive event occurrences.
This means the event will restart after a defined waiting period, such as 2 days or 12 hours, regardless of the day of the week.
| **Field** | **Description** | **Default/Options** | **Steps to Configure** |
| --- | --- | --- | --- |
| **Cooldown between occurrences** | Defines the waiting period between consecutive event occurrences (Cooldown-based). | Days, Hours, Minutes | Input the cooldown period in days, hours, and minutes (e.g., 2 days, 0 hours, 0 minutes). |
#### **Weekly-based Recurrence**
**Weekly-based** recurrences enable you to set specific days of the week on which the event will repeat, such as every Monday and Thursday, or at an interval of every two weeks.
| **Field** | **Description** | **Default/Options** | **Steps to Configure** |
| --- | --- | --- | --- |
| **Start of occurrence** | Defines the day(s) of the week the event will start (Weekly-based). | Days of the week: Monday, Tuesday, Wednesday, etc. | Select one or more days for the event to start (e.g., Monday and Thursday). |
| **Repeat every [X] weeks** | Defines how frequently the event repeats in weeks (Weekly-based). | Default: 1 | Input the number of weeks between recurrences (e.g., to repeat every 2 weeks, enter 2). |
For weekly-based recurring events, the start time of each occurrence will align with the event’s configured start time, **not midnight**. For example, if an event's start time is set to 10:00 AM, all weekly occurrences will also start at 10:00 AM.
**Note:** Ensure that the event’s start time is configured correctly to match the desired occurrence start time, as it will automatically propagate to all occurrences.
#### Validation: Avoid Overlapping Event Occurrences
When configuring an event that recurs on **multiple days** in a week (e.g., Monday and Thursday), it’s crucial to ensure that the **duration** of the event does not cause the occurrences to overlap. Overlapping occurs when a new event starts while a previous one is still ongoing.
**Scenario:**
If your event's **duration** is long (e.g., 6 days), and you select **two or more start days** (e.g., Monday and Thursday), and the event repeats **every week** , the system may detect an overlap between occurrences and prevent saving the event configuration.
**Example Configuration:**
1. **Event Duration** : 6 days
2. **Occurrence Days** : Monday and Thursday
3. **Repeat Every** : 1 week
With this configuration, the system identifies a conflict because:
- **First event** starts on **Monday** and lasts for 6 days (Monday to Saturday).
- The second event is scheduled to start on **Thursday** of the same week, which falls **within the duration of the first event**.
- This causes an **overlap** , as the Thursday occurrence would begin **before the Monday occurrence has ended**.
**System Validation:**
- As this overlap is detected, the system will display an error message like **"Occurrences are overlapping."**
- The system will not allow you to save the event configuration until the overlap is resolved.
**How to Resolve the Overlap:**
There are two ways to resolve this issue:
1. **Reduce the Event Duration** :
2. **Increase the Time Between Recurrences** :
**Key Points to Remember** :
- **Ensure that event durations don’t overlap with the next occurrence**. Either reduce the event duration or increase the time between recurrences to avoid overlap.
- If you select **multiple occurrence days** in the same week (e.g., Monday and Thursday), ensure that the total event duration allows enough time between these days.
- If your occurrences are longer than a week, ensure that you don’t repeat the event every week.
- If you receive the **“Occurrences are overlapping”** error, review your event duration and recurrence settings to make necessary adjustments.
Once you’re done with your configuration, click **[Save]** on the bottom left side of the screen.
### **Event Recurrence Logic**
Let us understand the event recurrence logic with the help of an example.
**Example: Configuring a Recurring Event Every Wednesday and Friday (Every 2 Weeks)**
You want to create a recurring event that happens every **Wednesday** and **Friday** , repeating **every 2 weeks**. The event starts on **Thursday, 19th September**.
#### Configuration Details
- **Event Start Date:** Thursday, 19th September.
- **Event Days:** Wednesday and Friday.
- **Recurrence Interval:** Every 2 weeks.
**Expected Event Occurrences:** (When number of occurrences are not limited)
1. **First Event:** **Friday, 20th September**.
2. **Second Event:** **Wednesday, 2nd October**.
3. **Third Event:** **Friday, 4th October**.
4. **Fourth Event:** **Wednesday, 16th October**.
5. **Fifth Event:** **Friday, 18th October**.
6. **Sixth Event:** **Wednesday, 30th October**.
7. **Seventh Event:** **Friday, 1st November**.
**How It Works:**
- The event starts on the first available day after the start date (Friday, 20th September).
- A **1-week gap** is added after the first event to maintain the recurrence interval of 2 weeks for both event days (Wednesday and Friday).
- The **week break** refers to skipping an entire **Monday-to-Sunday** week, regardless of how many days pass between the last event and the next. This ensures that events are spaced by full calendar weeks rather than simply counting a set number of days.
- The event will occur **in the same week** (on Wednesday and Friday) every 2 weeks from that point onward.
Event Scheduling Logic with Segment Changes
Let us understand the event scheduling logic when the player changes segments with the help of visual representations of two types of event scheduling logic for recurring events: **Offset** and **Weekly**.
**Offset Event Scheduling**
This type of scheduling applies an **offset** period between the recurrence of events for different segments.
The diagram shows how the player receives different events based on their segment over the course of a week.
- **Event Start Date:** 1st April 2024
- **Event End Date:** 31st December 2024
- **Duration:** 1 day
- **Offset:** 1 day
**Timeline Breakdown:**
- **Monday:**
- **Tuesday:**
- **Wednesday:**
- **Thursday:**
- **Friday:**
This configuration demonstrates that after an event occurs for a specific segment, there is a 1-day delay (offset) before the next event is triggered for a new segment. This ensures players in different segments don’t overlap event days immediately after switching.
**Weekly Event Scheduling**
This configuration follows a **weekly schedule** for recurring events. In this example, the events are triggered on specific days of the week (Monday and Thursday), and then they repeat weekly.
- **Event Start Date:** 1st April 2024
- **Event End Date:** 31st December 2024
- **Duration:** 1 day
- **Occurrence Days:** Monday and Thursday
**Timeline Breakdown:**
- **Monday:**
- **Tuesday & Wednesday:**
- **Thursday:**
- **Friday & Weekend (Saturday-Sunday):**
- **Next Monday:**
This configuration shows a more regular and predictable schedule, with events occurring on specific days of the week and repeating according to a defined schedule (e.g., every Monday and Thursday). There are no offsets between different segment events in this type of configuration.
**Visibility of Parameter Sets and Activity Sets Based on Event Type Configuration**
| **Scenario** | **Parameter Set** | **Activity Set** | **Description** |
| --- | --- | --- | --- |
| Both parameter set and activity set are configured for the selected event type | ✔ | ✔ | Both parameter set and activity set will appear for the selected event type. |
| Only parameter set is configured for the selected event type | ✔ | ❌ | Only the parameter set will appear for the selected event type. |
| Only parameter set is configured for the selected event type | ❌ | ✔ | Only the activity set will appear for the selected event type. |
| Neither parameter set nor activity set is configured for the selected event type | ❌ | ❌ | Neither parameter set nor activity set will appear for the selected event type. |
* * *
- If your event is part of an A/B experiment, you can define separate parameter configurations for each variant in the experiment.
- On the **Parameter Sets** page, you can see which events are using each parameter set in the **In-Use** column.
- You cannot delete a parameter set if it is linked to an event with an active or pre-live status.
* * *