Can I label or comment my alerts?

Autoview · Guide

Yes. Autoview has a comment line, and it is the right tool when you want a human-readable label sitting next to the trades an alert fires. Start a line with two slashes and the rest of that line becomes a comment. It does not place an order, change sizing, or touch your account. It writes a note. When you later open your log and try to work out which strategy sent which order, that note is what tells you.

Here is the whole feature in one example:

// RSI oversold long, v3
e=oanda s=EUR_USD b=long q=2% sl=1.2%

Two lines, two commands. The first is the comment. The second is the trade. Autoview reads the comment, prints it, and moves on to the order underneath.

The rule: a line that starts with //

A comment is any command line whose first characters are //. Everything after the slashes, trimmed of surrounding spaces, is the comment text. That is the entire syntax. There is no label= parameter and no comment= parameter you type yourself. The marker is the // at the start of the line.

So Autoview does not have a separate "label" feature and a separate "comment" feature. There is one mechanism, the comment line, and a label is just a short comment. If you came here looking for tags or categories, this is the thing that does that job.

What it actually does

A comment line is parsed as its own command, and Autoview treats it specially. It logs the text and then stops, on that line, before anything trades. Concretely:

  • It never sends an order. A line beginning with // can't open, close, or cancel anything. That's by design.
  • It doesn't merge into the trade below it. The comment and the trade are separate lines, so the comment never alters the order's exchange, side, size, or stops.
  • It prints the text to your log so you can read it back later.

Because it is a full line of its own, you can stack comments, put one above each command in a multi-line alert, or drop reminders to yourself between trades.

Where you'll see the label afterward

The comment surfaces in your event log, the running record of what each alert did. In the log it shows up as its own entry, styled as a muted note rather than a trade row, so a label reads as a label and not as an order. When you scan a busy log, the comment lines are the signposts: the trade rows tell you what happened, the comment rows tell you which alert made it happen.

This is exactly why people use it. A funded account firing dozens of alerts produces a wall of near-identical order rows. Sprinkle a comment above each command and the log turns readable. You stop guessing which TradingView alert, which script, or which strategy version sent a given order.

Writing a useful label

A few habits make comments worth the keystrokes.

  • Put the comment first. A comment above the trade reads in the order things happen: here's the note, here's the order it describes.
  • Name the strategy and the version. // Donchian breakout v2 tells you far more in six months than // long does.
  • Spaces are fine. The whole rest of the line is the comment, so you do not need quotes around a multi-word label. // momentum entry, half size works as written.

Keep it short enough to scan. The point of a label is that you can read it at a glance while the orders below it do the real work.

One thing to know about placeholders

If your alert comes from TradingView, you might reach for a placeholder like {{close}} to stamp the price into a comment. That won't fill in the way you expect. {{close}} is a TradingView placeholder, substituted by TradingView before the alert is ever sent, so whether it resolves depends on the sender, not on Autoview.

There is also a separate, Autoview-level limitation. Autoview's own replacement values, the :name=value tokens you can define in an alert, are not applied inside the comment text that gets logged. A comment is logged as written. If you want a number to appear in the note, the platform sending the alert has to put a literal value there before Autoview ever sees it. For a strategy label, that rarely matters, because the useful labels are static text like a strategy name, not live prices.

What this is not

Don't confuse the comment marker with the c= parameter. They look related and aren't. c= is the cancel-or-close control: c=position closes a position, c=order cancels resting orders. That one acts on your account. The comment marker is the leading // and it acts on your log. Different jobs entirely.

Putting it together

Here's a small multi-line alert with labels doing their job:

// --- ETH momentum strategy ---
// open
e=kraken s=ETHUSD b=long q=25% sl=2%
// scale-in trigger handled separately
e=kraken s=ETHUSD b=long q=10%

Three comment lines, two trades. Nothing in the comments touches the orders. But open the log after this fires and you can read it like a sentence: ETH momentum strategy, an open, a scale-in. That is the entire value of the feature, and it costs you two slashes.

For everything the trade lines themselves can do, side, sizing, stops, order type and the rest, see the command reference or the full alert syntax page.

Read the command reference