Need advice on how to properly extend your tracked url system for smses. It appears that you only allow for “contactfield” tokens to be placed in tracked urls. I need the ability to have custom fields tokenized but still tracked.
The only solution I can find is to just override or by-pass your page redirect implementation with my own custom version of it. I have considered chaining the redirect by inserting my own redirect before the Mautic redirect when doing the url shortening but I’d like to avoid having too many redirects so just by-passing your implementation seems like the only recourse in this version of the software.
I realize you have this “clickthrough” that you pass to the redirect which would be the ideal place to inject custom fields but your redirect controller only replaces tokens which are considered “contactfields” and I don’t see any way to inject custom contact fields on the fly. I don’t want them to be added to the contact schema because they are dynamic and will change with every sms send.
For example, I want to be able to pass the “stat” tracking hash as a url parameter to a landing page. Ideally there should be a way to pass any custom field as a tokenized url parameter.
Steps to produce:
Create a “Text Message” with a url in it. Use a custom token like {mycustomtoken=somevalue} in the url. For instance "https://demo.com?p={mycustomtoken=somevalue}.