It turns out program tokens can be in use in very strange ways, which makes it a necessity to have the "used by" functionality for program tokens. A use case I came across today:
- Original token is set up in a campaign folder.
- Someone erroneously made changes to the inherited token in a program that was stored inside that campaign folder.
- The program with the incorrectly overridden token was then cloned to an entirely different campaign folder.
The cloned program retained its reference to the erroneously overridden token in the source program. Therefore, when we tried to remove the token this was not possible as it was still in use. We needed Marketo Support to trace where that was, because in the UI it was impossible to figure out.
Although it can be argued that the link to the original overridden token should be broken in the cloning, providing visibility on where a program token is used prevents this confusion already quite well.
.png)