> For the complete documentation index, see [llms.txt](https://kylin-inc.gitbook.io/spider-browser/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kylin-inc.gitbook.io/spider-browser/other-modules/configure-event-time.md).

# Configure Event Time

## How To Configure Event Time

Some releases will release performances at different times at the same time. If you need to purchase performances with a specified event time, you need to configure the event time. When creating a task, configure the event time in the performance time field, as shown in the figure

<figure><img src="/files/8vBbLtM4w4WK5Q8crzUE" alt=""><figcaption></figcaption></figure>

First, you need to select the time zone where the performance time is located. Remember to check the range, and then add a time range. Double-click "Start Time" and "End Time" to open the configuration time cleanser, and then configure a time range, preferably around 24-48 hours. , this range needs to include the target performance time, and the best performance time is in the middle of this range

<figure><img src="/files/IQ67yWZweRY3MMLZz0a0" alt=""><figcaption></figcaption></figure>

If you need to configure the priorities of different performance times, configure multiple ranges. Each range includes a performance time, and the purchase priority is from top to bottom, as shown in the figure:

<figure><img src="/files/2BKyKO8CbqK0LzTEOzVG" alt=""><figcaption></figcaption></figure>

If event time is not configured, the task will randomly purchase tickets for any performance time.

## Tips

* It is recommended to only match intervals. The best time span for an interval is 24-48 hours.
* Confirm that a range can only contain one performance time, not multiple
* The performance time within an interval is best in the middle of the interval, not at the beginning or end.