An Order instance (let's call it order) carries an attribute data which is the asset on which the order has been issued. The ticker name should be available as: (where _name is the name you have assigned when using adddata)

Names are actually a late addition to backtrader, because one of the underlying design concepts is that the development of a trading idea should, ideally, not be bound to a specific asset.

A signal / indicator has (like a Strategy) receives an array of the available data feeds in the environment in which they are instantiated (an Indicator can be instantiated inside a Strategy or inside another Indicator)

If your Strategy has 4 data feeds, the indicator will default to receiving 4 data feeds, which will be available in the iterable self.datas and as self.data0, ..., self.data3. Most indicators actually only use 1 data feed. One can actually declare that a given indicator must receive more than 1 data feed.

See: Blog - Crossing over numbers

Notice that it defaults to receiving the data feeds from the environment.. Because if the user specifies which data feeds go by passing them to the instantiation, those will be the ones passed.

Another reason not to rely on names is that an indicator can receive another indicator as data feed. For example:

sma_on_sma = bt.ind.SMA(bt.ind.SMA(self.data1, period=10), period=20)

The outer SMA receives the inner SMA as data feed. And this data feed carries no name, even if it's calculating the simple moving average of self.data1. We still don't know what self.data1 is. It could be an RSI for example. See:

class MyInd1(bt.Indicator): lines = ('sma_on_sma',) def __init__(self): self.lines.sma_on_sma = bt.ind.SMA(bt.ind.SMA(self.data1, period=10), period=20) class MyInd2bt.Indicator): lines = ('myline',) def __init__(self): self.lines.myline = MyInd1(, bt.ind.RSI(

MyInd2 passes 2 data feeds, one is the main data feed received (which can be anythin) and the 2nd is the RSI. As such MyInd1 receives an RSI instance as self.data1, but it doesn't know it. It simply does an SMA on it and then a 2nd SMA

If your signal is going to be name-bound, it will be limited to real data feeds which carry a _name attribute and will fail to be generic for any kind of actual data feed, like in the examples above.

class MyInd3(bt.Indicator): lines = ('name_bound',) def __init__(self): if self.data0._name == 'my-preferred-name': self.lines.name_bound = bt.ind.SMA(self.data3) else: self.lines.name_bound = bt.ind.SMA(self.data2)

At least data0 must be a real data feed with a name in that example.