The macro editor is implemented as a client-side override and doesn't go through the same rendering process as other connect components, which prevents it from supporting any variable substitution at the moment.

We already use a variable transformer for the injected JS, however, so it may be possible to support page-level variables (not macro-specific ones, however).

A client-side JS API to get the page context would be an alternative if variable substitution doesn't work.