Deleting tokens in program templates

[Anonymous]

I'm trying to delete some tokens in program templates, and am not able to as it says the tokens are in use. I think I scoured everywhere looking for each instance and removed, but I must be missing something.

Is there a way to see where a particular token is being used, so you can remove it form that asset and then delete the token?

Thank you

[Amy_Goldfine]

Reach out to support and they'll delete them for you. It's a known issue.

[Diego_Lineros2]

I did and this is not the point... to delete a token we need to reach support, great product 👏. And, if it is a known issue since last decade, why it hasn't been fixed?

[Amanda_Thomas6]

Karenna Glover  This would be a good idea to post! I'd vote for a feature that lists where the tokens are being used.

[Grégoire_Miche2]

Ideas on this already exist multiple times. read the post I mentionned earlier.

-Greg

[Diego_Lineros2]

2020 and still deleting tokens is a roulette, what a Joke Marketo!!

[Grégoire_Miche2]

HI Karen,

There is known bug about token deletion and false "token in use" message. Look at 1-9 and 4-2 in here: Just do it! Marketo so-called minor missing features

-Greg

[Anonymous]

Thanks for the info and link. Guess we'll leave them in for now.

[Grégoire_Miche2]

Hi again Karenna,

The trick is to renames them. We rename them "zz-To Be Deleted-#x".

-Greg

[Anonymous]

Thanks, Grégoire Michel . Funny enough, renaming worked for one token deletion, but not the second. I will reach out to support, too, Christina Zuniga

Thanks

[Anonymous]

If that doesn't work you can have Support delete it. Renaming didn't work for one of my tokens but support was able to clear it out.

[Josh_Hill13]

No, but it's probably in the email or page code or even the Template.

Why do you want to delete all of them?

[Anonymous]

Thanks for replying Josh. I don't want to delete all; just the ones that aren't being used.

[Geoff_Krajeski1]

Check the templates, emails & pages, as well as your flow steps in any campaigns!

If it still is giving the error then I'd lean towards the response below by Grégoire Michel