How to Use Exit Strategies in ATAS

Exit strategies in trading involve a range of actions traders take to protect their capital from losses. Since losses are inherent to the profession, developing an exit strategy involves finding, achieving, and maintaining an optimal balance where losses are offset by profits.

This article will delve into the tools for implementing exit strategies available in the ATAS platform.

Contents:

Types of Exit Strategies
Capabilities of the ATAS Exit Strategies Block
Fixed Stop-Loss Strategy
Breakeven Strategy
Trailing Stop Strategy
Pros and Cons of Exit Strategies
FAQ
How to Apply Exit Strategies in Practice

Start to use ATAS absolutely free of charge! The first two weeks of use of the platform give access to its full functionality with 7-day history limit.

To try ATAS free of charge

Types of Exit Strategies

Developing an exit strategy depends on financial goals, the trading system used, experience, the trader’s individual preferences, and other factors.

The following types of exit strategies are available to traders and investors:

Diversification. Allocating capital among various assets (and/or trading systems) aims to reduce risk since negative changes in one area can be offset by positive changes in another.
Position sizing management helps control risk by limiting the size of each position according to the overall trading capital. For example, a trader with a $10,000 capital may open each position with a volume of $500.
Using options and futures. These derivative instruments (including hedging) can be used for more advanced exit strategies. For instance, to protect a long position in futures, a trader may decide to purchase a put option, which insures against potential price declines.
Psychological preparation. To minimize the risk of making impulsive decisions, traders are encouraged to develop detailed trading plans, learn to manage emotions, extend timeframes (allowing more time for analysis), use clearer indicators, and practice trading in a simulator.

However, the most obvious and common way to protect your capital is by setting stop-loss and take-profit orders:

stop-loss is an order to close a position automatically when the price reaches a specific level, preventing further losses.
take-profit is an order that closes a position when the price reaches a predetermined profit level. The execution of the take-profit order cancels the stop-loss order: the higher the probability of the take-profit order being triggered, the lower the probability of the protective stop-loss order being triggered.

Before we delve into describing ATAS functionality for managing stop-losses and take-profits, let’s highlight some important drawing tools that help you plan position openings in a proficient and visually easy way.

These tools are called Long (planning to buy positions) and Short (planning to sell positions) and can be found in the drawing objects menu (1). They can also be placed on the left panel (2) for quick access.

The screenshot displays a red-green construction created using the Long tool, consisting of two rectangles, which will:

visually demonstrate the risk-reward ratio based on the levels at which the trader plans to set SL and TP;
calculate the position size based on the specified percentage of allowable risk.

More details about the Long and Short tools can be found on the respective page in the Knowledge Base. Now, let’s focus on the exit strategies block located on the Chart Trader panel (to access it, press ‘T’).

Capabilities of the ATAS Exit Strategies Block

The ATAS platform is constantly evolving. In its current configuration, users have access to a user-friendly and functional exit strategies block:

The block consists of two tabs (1):

the SL/TP tab has functionality for working with stop-loss and take-profit orders;
the Advanced tab provides options for setting take-profit and stop-loss orders not for the entire position, but for its parts, offering more flexibility in capital management.

On the SL/TP tab, you will find:

settings (2) for placing fixed stop-loss and/or take-profit orders;
settings (3) for transitioning a position to breakeven;
settings (4) for a trailing stop-loss.

The Advanced tab will be discussed further in the text. For now, let’s focus on examples of using the functionality that has already been introduced.

Fixed SL and/or TP Strategy

This is the easiest strategy where a trader has well-defined rules (logic) for placing stop-loss and take-profit orders.

For instance, if a trader has opened a long position on BTC/USD, they can set fixed values for SL and TP using either:

a functional marker on the chart;
the exit strategies block.

Functionality for setting stop-loss and take-profit orders

Option 1. If you look at the marker reflecting data about an open position near the price scale on the chart, you will see buttons for SL and TP. By dragging them to the desired price levels, you can set levels of acceptable risk and acceptable profit.

Pros: visual, convenient, simple.
Cons: there is a risk of making a human error: accidentally placing an order at the wrong level or not doing it quickly enough. Or forgetting about it.

Option 2. Let’s use the exit strategies block on the Chart Trader panel.

For example, you want to set a protective stop order 0.1% below the current price immediately after opening a position. To do this:

activate the Stop-Loss slider;
in the settings, specify the distance = 0.1% (you can set it in percentages, ticks, or currency – rounding in calculations is acceptable);
click Apply to use the settings;
open a position.

In the screenshot above, we see the BTC/USDT market, data from the Binance futures exchange. We observe the result – the stop-loss was automatically set higher immediately after opening a short position.

If the position is closed when the take-profit is reached or manually, the existing stop-loss will be automatically canceled.

In another scenario, if a trader opens a position with an automatic stop-loss set at 1%, but later decides to reduce the stop to 0.5%, they can change the value in the settings and click Apply. ATAS will immediately adjust the existing protective stop-loss to a closer level.

Pros:

you can set stop-loss and take-profit orders automatically;
you can configure setting stop-loss and take-profit orders using values in percentages, ticks, or currency;
you can adjust the balance between stop and take;
you can configure stop-loss and take-profit orders independently. For instance, a strict stop will be automatically set to a predefined risk value for a trade, while a take-profit can be manually adjusted based on market conditions.

Cons:

High market volatility or setting stops and takes too close may result in them triggering immediately after being set.

Breakeven Strategy

This exit strategy involves activating an option to move the stop-loss to the position’s opening level if the price moves a specified distance in the desired direction.

The implementation of this strategy is expected to make the deposit growth curve smoother. On the other hand, it can be disappointing if the price hits the breakeven point and then continues to move in the initially predicted direction.

Simply put, here is how it works:

The trader buys an asset at $100, setting a stop at $99. The worst-case scenario for them is losing $1.
The asset rises to $102. The trader moves the stop to the entry level = $100. Now, the worst-case scenario for them is breaking even, but there is no risk of loss (excluding commissions, slippage, and gaps).

To implement a trading strategy with automatic break-even, you need to:

activate the corresponding option (1);
adjust the Breakeven and Offset parameters;
apply the settings (2).

The Breakeven parameter sets a trigger for moving the stop-loss to a specified level. It can be set in ticks or percentages.

By default, the value is set to 5 ticks. This means that if the price moves by 5 ticks in the desired direction, the stop-loss will be moved.

The Offset parameter determines the break-even level to which the stop-loss will be moved.

It can be set in ticks or percentages.

For example, if Offset = 0, the stop will be moved precisely to the opening price.

If Offset = 1 Tick (by default), then the stop will be moved 1 tick above the opening price for long positions or 1 tick below the opening price for short positions.

Example. ES market, E-mini S&P-500 futures.

Initially, a long position was opened with a stop-loss, but when the price moved up by 5 ticks, the stop-loss order was moved one tick above the opening price (technically, the previous one was canceled, and a new one was set). This moment is precisely captured in the screenshot.

An important point: For the breakeven function to work correctly, it is necessary to initially place and configure the stop-loss. Otherwise, what will be moved to breakeven?

Pros of breakeven: it reduces psychological pressure on the trader, partially protects capital, helps smooth out the growth curve.
Cons: it may lead to prematurely closing trades that could have potentially been profitable.

Trailing Stop Strategy

This exit strategy is based on a stop-loss that automatically follows the position:

if a long position is opened, the stop-loss is progressively raised as the price increases;
if a short position is opened, the stop-loss is progressively lowered as the price decreases.

For example, a trader buys an asset at $100, initially setting the stop-loss at $93. The settings are as follows: Trailing Stop = 10, Trailing Step = 5.

When the price reaches or exceeds $110, the Stop Loss order will be moved to $98. Next, when the price reaches $120, the Stop order will be moved to $103, and so on.

It is assumed that the trailing stop helps the trader trade more effectively with the trend and save effort. While the momentum is developing, the profit grows. On the other hand, the position may close during a correction – especially if the trailing stop closely follows the price.

To use the trailing feature, you need to:

activate the function by checking the box (1);
adjust the Stop and Step parameters;
click Apply (2) to use the settings.

Stop (specified in ticks or percentages) serves as a trigger to indicate the distance the price should move in the desired direction. After this, the stop-loss will be moved.

Step (also specified in ticks or percentages) denotes the distance by which the stop loss will be moved.

For example, let’s consider the E-mini S&P-500 futures market. Let’s see step by step how the trailing feature will work with these settings: Trailing Stop = 5 ticks, Trailing Step = 3 ticks.

Stage 1. We open a long position at 4821 with a stop loss set at 10 ticks (automatically placed at 4818.50, as the tick size on this market is 0.25 points).

Opening a position using a trailing stop

Stage 2. As the price moved up by 5 ticks, the stop loss was adjusted by 3 ticks – specifically to the 4819.25 level (note that after the first triggering of the trailing stop, the stop loss value changed – instead of being 10 ticks, the stop loss is now indicated as a specific price level of 4819.25).

Stage 3. The price continues to rise. The second automatic adjustment of the stop loss occurs. Instead of the initial risk of 10 ticks, the risk is now reduced to 4 ticks.

Assuming the process is clear, let’s skip some intermediate stages to see how the position closes. The screenshot below indicates a significant bullish momentum before bears became active.

During this process, the trailing function moved the stop-loss over a considerable distance. However, the activation of bearish sentiment led to the closing of the long position:

Closing the position with the trailing stop

The white triangles indicate the moments of buying and selling.

Pros of trailing: it automatically follows the price, protecting profits; it operates in real-time mode and closes the position when the market trend changes.
Cons: it may be triggered during a correction if it follows the price too closely; it may lead to significant missed profits.

Closing a position via trailing often comes with some disappointment – ‘I should have closed earlier, then there would have been more profit!’ But keep in mind that the primary function of trailing is not to take profit (that is what the take-profit is for), but to gradually reduce risks if the price moves in the desired direction.

Partial Position Closing

Let’s explore the functionality located on the Advanced tab. Here, you can configure partial position closing.

This feature can be useful in many cases:

for instance, a trader opens a long position;
sets a fixed stop-loss at a level where the price convincingly proves the fallacy of their reasoning;
and for take-profit, the trader has 2 levels – let’s call them ‘TP1 – conservative’ (closer) and ‘TP2 – optimistic’ (farther, higher).

Now, you need to set up automatic:

closing of 50% of the position at the TP1 level,
and the remaining 50% at the TP2 level.

Here is how to do it using the functionality available on the Advanced tab.

First, you need to specify that the volume of the opened position (1) will be equal to two contracts.
Then, in the Advanced block, you need to add a layer by clicking on the plus sign. Then the first layer will be responsible for closing half of the position at TP1, and the second one for closing at TP2.
Make sure that all settings are correct and click on the confirming green checkmark.

When a long position of 2 contracts is initiated, the take profits and stop losses specified in the settings on the Advanced tab will be automatically applied – as depicted in the screenshot above.

When the price reaches the TP1 level, partial profit-taking occurs:

It is important to ensure that the protective layers on the Advanced tab fully safeguard the volume of open positions (unless intentionally desired otherwise).

Pros of Advanced protective layers: automation + maximum flexibility, allowing gradual position reduction depending on where the price is heading.
Cons: high risk of human error – especially if the position is split into a large number of parts.

By the way, to help users track open positions in different markets, ATAS has a Positions window. To open it, click on the corresponding button in the main menu or select the Positions option by clicking on the plus sign at the bottom as shown in the screenshot.

In the Positions window, there is a special column for managing SL and TP levels. Check out how easy it will be to use.

Pros and Cons of Exit Strategies

What are the pros and cons of the discussed capital protection measures related to setting stop-losses, trailing stops, breakeven levels, and take-profits?

Pros:

Protection. The main advantage is that exit strategies prevent the worst-case scenario from occurring.
Systematic approach. They help better manage and control the trading process, optimizing SL and TP levels.
Psychological impact. Stop-loss orders help maintain composure, knowing that capital is protected in adverse situations.

Cons:

Exit strategies tend to limit profit potential. If a stop-loss is triggered too early (e.g., due to volatility spikes), the trader may miss out on the intended part of the trend.
Subjectivity. Determining levels for setting stop-loss orders involves additional analysis and decision-making, which can be prone to errors.
Psychological pressure. Frequent stop-loss triggers can lead to disappointment and a decrease in confidence, sometimes causing traders to refrain from setting stop-losses altogether.

FAQ

Can a trailing stop and breakeven be used simultaneously?

Technically, it is possible. ATAS will systematically execute commands embedded in both functions as conditions are met. However, it is not entirely logical, so we may recommend choosing one or the other. Otherwise, there is a possibility that with certain settings, these functions may conflict and disrupt the system’s consistency. When using both a trailing stop and breakeven simultaneously, it is important to have a clear understanding of why this is done and how the system will operate under different price behavior scenarios.

Is it necessary to set stop-loss orders?

A position can be opened without a stop-loss. Technically, when a position is opened, it does not have a stop-loss. Setting a protective order is not mandatory, but highly advisable, as it will prevent critical scenarios where capital may be either completely destroyed or irreversibly reduced.

What are mental stop-losses?

This is for experienced traders. They closely monitor the market while keeping in mind the levels of mental stop-losses. When these levels are reached, traders conduct an analysis considering new data and decide what to do next: either manually close (reduce/increase) the position, continue holding, or choose another option. This adds flexibility, eliminates the risk of stop-loss being triggered by a volatility spike, but leaves open the scenario with catastrophic consequences. Use mental stops only when fully aware of everything you are doing.

What are mathematical stop-losses?

In simple terms, this is when a trader sets a stop-loss not based on an extreme point, a level of significant volume, or any other element of the chart, but by using a formula. A simple example is a stop-loss set at 0.1% of the asset’s price from the entry point.

Can stop-loss and take-profit orders be saved when restarting ATAS?

Yes, since the beginning of 2024, SL/TP orders can be saved after restarting the platform.

How to Apply Exit Strategies

Properly applying stop-losses and take-profits can make a significant difference in trading outcomes. Some say that in trading, it is not just about where you enter, but also where you exit – and that is precisely what is determined when using SL and TP.

To start, it is important to assess your risk tolerance, your strategy’s characteristics, and the current market conditions. Trading is not a one-size-fits-all method, so every trader needs to find their own approach that aligns with their style, knowledge, and preferences.

To quickly learn how to fully use the exit strategies available in the ATAS platform, and to assess how they affect your performance, launch the ATAS Market Replay. It is an integrated simulator for traders. Analyzing statistics for the Replay account will help you find an acceptable balance between risk and potential profit without losing capital. Gain valuable experience in setting stop-losses and take-profits as if trading were happening in real time.

Conclusions

When it comes to risk management, it is generally advised not to stake more than 2% of your total deposit on any single trade. However, a balance between risk and potential reward should ideally range from 1:2 to 1:3 or even higher.

To effectively control risks and secure profits, ATAS offers exit strategies. These are tailored to provide users with flexibility, convenience, and help them maintain control over their portfolios, avoiding emotional decisions that could result in substantial losses.

Download ATAS, professional software for working with exchange volumes. It is free. During the trial period, you will get full access to the platform’s tools to experiment with horizontal and other volumes. Moreover, you can continue using the program for free even after the 14-day trial period is over, whether it is for cryptocurrency trading and/or learning, conducting market analysis.

Do not miss the next article on our blog. Subscribe to our YouTube channel, follow us on Facebook, Instagram, Telegram, or X, where we publish the latest ATAS news.

Information in this article cannot be perceived as a call for investing or buying/selling of any asset on the exchange. All situations, discussed in the article, are provided with the purpose of getting acquainted with the functionality and advantages of the ATAS platform.

Cookie	Duration	Description
__utm*	Cookies are stored following the Freshworks company Privacy and Cookie Policy	No description
_BEAMER_	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Cookie files, used by Beamer Notifications to manage their data
_ga	Cookies are stored following the Freshworks company Privacy and Cookie Policy	It registers a unique identifier used to generate statistical data on how visitors use the website
_gat	Cookies are stored following the Freshworks company Privacy and Cookie Policy	It uses Google Analytics to analyze the number of requests on the website
_gat_gtag_	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Google is set up to distinguish between users
_gid	Cookies are stored following the Freshworks company Privacy and Cookie Policy	It registers a unique identifier that is used to generate statistical data on how the visitor uses the website
_helpkit_session	Cookies are stored following the Freshworks company Privacy and Cookie Policy	The secret key for verifying cookie session data integrity. If you change this key, all old sessions become invalid
_hp2_*	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Cookie files, used by Heap Analytics to manage data
_x_m	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Contains the shard ID at which the account runs
_x_w	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Contains the state of the shard
.AspNetCore.Antiforgery.RCuQdhHRBFg	session	Serves for security purposes to prevent forged requests
ATAS.Billing	10 day	Authorized user token
aviaCookieConsent	1 year	This cookie indicates that you agree to our use of cookies on our website
aviaPrivacyEssentialCookiesEnabled	1 day	This cookie indicates that you agree to our use of cookies on our website
aviaPrivacyRefuseCookiesHideBar	1 day	This cookie indicates that you agree to our use of cookies on our website
BillingAuthorized	10 day	This cookie is used to show if the user is logged in
bulkTime	1 year	Wordpress ShortPixel Image Optimizer
cookielawinfo-checkbox-advertisement	1 year	Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-analytics	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional	11 months	The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others	11 months	This cookie file is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other"
cookielawinfo-checkbox-performance	11 months	This cookie file is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance"
falcon_enabled	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Indicates if falcon_ui is enabled for an account
filter_name	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Used to set the filter's name in agents tickets list page for default and custom views
fm_sid_*	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Refer to Freshmarketer cookies
helpdesk_node_session	Cookies are stored following the Freshworks company Privacy and Cookie Policy	An encrypted hash that stores the secret key and id of the login attempt
helpdesk_url	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Contains the URL for the Freshdesk L2 dev portal. The default value is freshdeskl2dev.freshdesk.com
language	session	This cookie is used to store the language preference of the user
LanguageSwitcher	session	This cookie is used to save the user's language preferences
oftinf	never	This cookie is used to record the ID of the partner who led the user
order	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Used to check the order in which the tickets are filtered for default ticket filters, e.g., due_by, agent_responded_at, requester_responded_at, etc
order_type	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Used to check if the order is ascending or descending for default ticket filters
PHPSESSID	session	This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed
return_uri/return_to	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Used to return to the page where the app was installed
scenario_show_tab	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Filter used to show the page view for /admin/scenario_automations page (default value: shared)
session_state	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Hash values that are used to check if FreshID V2 is enabled
session_token	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Contains the fresh_id token encrypted hash
tag_sort_key	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Indicates the order of the tags used in /admihttps://www.getbeamer.com/docsn/tags
template_show_tab	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Filter used to show the page view for /admin/ticket_templates page (default value: shared)
viewed_cookie_policy	11 months	The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
wf_order	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Used to check in which order the tickets are filtered for custom ticket filters, e.g., due_by, agent_responded_at, requester_responded_at, etc
wf_order_type	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Used to check if the order is ascending or descending for custom ticket filters
wp-wpml_current_language	1 day	It saves the current language. Wordpress Plugin WPML
zarget_*	Cookies are stored following the Freshworks company Privacy and Cookie Policy	Refer to Freshmarketer cookies

Cookie	Duration	Description
___dc	10 years	It is used to identify website users in the Roistat system
_clck	1 year	The browser stores the Clarity user identifier and preferences, which are unique to this website. This ensures that the behaviour is applied to the same user identifier on subsequent visits to the same website.
_clsk	1 day	It combines multiple user pageviews into a single Clarity session record
_ga	2 years	It registers a unique identifier used to generate statistical data on how visitors use the website
_gat	1 day	It uses Google Analytics to analyze the number of requests on the website
_gat_gtag_UA_51120514_1	1 minute	Google is set up to distinguish between users
_gat_gtag_UA_51120514_2	1 minute	Google is set up to distinguish between users
_gcl_au	3 months	Google Tag Manager provides anexperimental evaluation of theeffectiveness of advertising onwebsites that use its services
_gid	1 day	It registers a unique identifier that is used to generate statistical data on how the visitor uses the website
_ym_d	1 day	It stores information about how visitors use the website while generating an analytical report on website performance. Some of the collected data contains the number of visitors, their source and the pages visited in Incognito mode
_ym_isad	1 year	This cookie is used to collect information about the user, such as user features, website behaviour and desired actions.
_ym_retryReqs	never	It registers statistical data about user behaviour on the website; it is also used for internal analysis
_ym_uid	1 year	This cookie is used to collect non-personally identifiable information about visitor behaviour on the website and non-personally identifiable visitor statistics.
abTesting		It is used to identify website users in the Roistat system
ANONCHK	1 day	It registers visitor data from multiple visits and multiple websites. This information is used to evaluate the effectiveness of advertising on websites.
b24_crm_guest_pages	never	A unique identifier for a specific user was identified. Using the chat functionality, this allows the website to purposefully offer the relevant offers to the user
b24_crm_guest_utm	never	A unique identifier for a specific user was identified. Using the chat functionality, this allows the website to purposefully offer the relevant offers to the user
c.gif	session	No description
CLID	1 year	It is a Behavioural Analysis Tool that helps to understand user experience
metrika_enabled	session	It is used to track visitors across multiple websites to show relevant advertising based on the visitor's preferences
MUID	1 year	Microsoft is widely used as a unique user identifier. This cookie allows you to track the user when synchronizing identifiers across multiple Microsoft domains
roistat_ab	past	It is used to identify websiteusers in the Roistat system
roistat_abTests	never	It is used to identify website users in the Roistat system
roistat_call_tracking	7 day	It is used to identify website users in the Roistat system
roistat_emailtracking_email	7 day	It is used to identify website users in the Roistat system
roistat_emailtracking_emails	7 day	It is used to identify website users in the Roistat system
roistat_emailtracking_tracking_email	7 day	It is used to identify website users in the Roistat system
roistat_first_visit	10 years	The number of the user's firstvisit is generated in Roistat
roistat_geo_data	1 day	It is used to identify website users in the Roistat system
roistat_geo_data	never	It is used to identify website users in the Roistat system
roistat_is_need_listen_requests	session	It is used to identify website users in the Roistat system
roistat_is_save_data_in_cookie	session	Used to identify website users in the Roistat system
roistat_isMultiDomain	never	It is used to identify website users in the Roistat system
roistat_isNeedToListenRequests	never	It is used to identify website users in the Roistat system
roistat_last_settings_update_time	never	It is used to identify website users in the Roistat system
roistat_leadHunterEnabled	never	It is used to identify website users in the Roistat system
roistat_leadHunterTargetPagesMap	never	It is used to identify website users in the Roistat system
roistat_metrika_counter_id	never	It is used to identify website users in the Roistat system
roistat_multiwidgetEnabled	never	It is used to identify website users in the Roistat system
roistat_multiwidgetFBEnabled	never	It is used to identify website users in the Roistat system
roistat_multiwidgetFBLink	never	It is used to identify website users in the Roistat system
roistat_multiwidgetTelegramEnabled	never	It is used to identify website users in the Roistat system
roistat_multiwidgetTelegramLink	never	It is used to identify website users in the Roistat system
roistat_multiwidgetViberEnabled	never	It is used to identify website users in the Roistat system
roistat_multiwidgetViberLink	never	It is used to identify website users in the Roistat system
roistat_multiwidgetVKEnabled	never	It is used to identify website users in the Roistat system
roistat_multiwidgetVKLink	never	It is used to identify website users in the Roistat system
roistat_multiwidgetWhatsAppEnabled	never	It is used to identify website users in the Roistat system
roistat_multiwidgetWhatsAppLink	never	It is used to identify website users in the Roistat system
roistat_onlineChatEnabled	never	It is used to identify website users in the Roistat system
roistat_onlineChatSettings	never	It is used to identify website users in the Roistat system
roistat_promo_code	never	It is used to identify website users in the Roistat system
roistat_proxy_forms	never	It is used to identify website users in the Roistat system
roistat_settings_saved	never	It is used to identify website users in the Roistat system
roistat_settings_version	never	It is used to identify website users in the Roistat system
roistat_visit	14 days	The number of the user's firstvisit is generated in Roistat
roistat_visit_cookie_expire	14 days	It is used to identify website users in the Roistat system
roistat-leadhunter-form-template	never	It is used to identify websiteusers in the Roistat system
roistat-leadhunter-pulsator-settings	never	It is used to identify websiteusers in the Roistat system
roistat-leadhunter-pulsator-template	never	It is used to identify websiteusers in the Roistat system
roistat-multiwidget-pulsator-settings	never	It is used to identify websiteusers in the Roistat system
roistat-multiwidget-pulsator-template	never	It is used to identify websiteusers in the Roistat system
roistat-online-chat-iframe-template	never	It is used to identify websiteusers in the Roistat system
roistat-online-chat-pulsator-template	never	It is used to identify websiteusers in the Roistat system
SM	session	It is used when synchronizing MUIDs between Microsoftdomains
SRM_B	1 year 24 day	It is a Behavioural Analysis Tool that helps to understand user experience
utm_campaign	never	Referral user data
utm_content	never	Referral user data
utm_medium	never	Referral user data
utm_source	never	Referral user data
utm_term	never	Referral user data
yabs-sid	1 year	It registers statistical data about user behaviour on the website; it is also used for internal analysis and website optimization
yandexuid	1 year	It registers statistical data about user behaviour on the website; it is also used for internal analysis and website optimization
ymex	1 year	It registers statistical data about user behaviour on the website; it is also used for internal analysis and website optimization
yuidss	1 year	It collects information about user behaviour across multiple websites. This information is used to optimize the relevance of advertising on the website

Cookie	Duration	Description
_fbp	3 months	This cookie is set by Facebook inorder to display advertising onFacebook or the digital platformthat Facebook ads use after visitingthe website.
ads/ga-audiences	session	It uses Google AdWords to reevaluate visitors who are mostlikely to become customers basedon the visitor's online behaviour onvarious websites
CONSENT	2 years	It is used to determine if the visitorhas accepted the marketingcategory in the cookie banner. This cookie is necessary forwebsite complianceGDPR
fr	3 months	Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.
i	10 year	This cookie sets OpenX in order tolog anonymized user data such asIP address, geographic location,sites visited, advertisements theuser clicks on, etc. to providerelevant advertising
IDE	1 year	It uses Google DoubleClick, inorder to register and report websiteuser actions after viewing orclicking on advertisers'advertisements, to measure theeffectiveness of advertisementsand to offer targeted advertisingmaterials
pagead/1p-user-list/#	session	It tracks whether a user has showninterest in specific products orevents across multiple websitesand determines how the usernavigates between websites. It isused to evaluate advertising effortsand facilitate the payment ofreferral rewards between websites
Remixlang	1 year	It defines the visitor's preferredlanguage. It allows the website toset the preferred language after thevisitor re-logs in
test_cookie	15 minutes	It is used to determine if the user'sbrowser supports cookies.
tr	session	It uses Facebook to provide arange of advertising products suchas real-time bidding from thirdparty advertisers
VISITOR_INFO1_LIVE	5 months 27 days	It tries to estimate the duration of auser ban on pages that haveintegrated YouTube video clips
YSC	session	It registers a unique identifier inorder to store statistics aboutwhich YouTube videos have beenwatched by user
yt-remote-cast-available	session	Saving user's video player preferences
yt-remote-cast-installed	session	Saving user's video player preferences
yt-remote-connected-devices	constantly	Saving user's video player preferences
yt-remote-device-id	constantly	Saving user's video player preferences
yt-remote-fast-check-period	session	Saving user's video player preferences
yt-remote-session-app	session	Saving user's video player preferences
yt-remote-session-name	session	Saving user's video player preferences
yt.innertube::nextId	never	This cookie file, set by YouTube, registers a unique ID to keep statistics of what videos the user has seen on YouTube
yt.innertube::requests	never	This cookie file, set by YouTube, registers a unique ID to keep statistics of what videos the user has seen on YouTube

Cookie	Duration	Description
ls-popup-229	1 year	This is a cookie file that allows to remember how many times a popup window was displayed
ls-popup-last-displayed	2 years	It is a cookie that allows to remember how many times a popup has been displayed
qmb	session	No description
remixir	past	No description

How to Use Exit Strategies in ATAS

Types of Exit Strategies

Capabilities of the ATAS Exit Strategies Block

Fixed SL and/or TP Strategy

Breakeven Strategy

Trailing Stop Strategy

Partial Position Closing

Pros and Cons of Exit Strategies

FAQ

How to Apply Exit Strategies

Conclusions

Other blog articles:

Exit Strategies in Trading

Key Updates from ATAS in 2023 and Plans for 2024

ATAS Indicators: Types, Purpose and Configuration

Is it possible to combine the cluster analysis with the CCI indicator?

Six ways to speed up work with the ATAS platform

Heat map in ATAS functionality

Specific features and advantages of the Range XV chart

ATAS Market Replay – a unique exchange simulator for traders

Adding indicators in the ATAS platform