Hello,
Thanks for the detailed explanation.
I think the current setup makes sense, but the weak point is Ticketmaster’s metadata consistency, not really your script. Different countries and organizers classify events very differently, so even a solid fallback matcher will sometimes get it wrong.
That said, since Tmomatic already exposes Ticketmaster’s own classification fields like %%item_classification_genre%% and %%item_classification_subgenre%%, I’d probably simplify the setup and use those directly instead of relying on post-import detection logic. Those values should generally be more reliable.
Your current code is actually very good as a normalization fallback, but using the native classification data directly should reduce mismatches.
Let me know if this helped.
Regards,
CodeRevolution