There is no native integration of Campaign with TinyUrl. I’m not sure how you are generating the TInyUrl but some customers like to generate the URL on fly within the workflow.
So assuming you are sending SMS to 500 recipients, if you wish to pass custoemrID in URL you need 500 tinyUrls, given the fact CustomerID will be unique for each.
I’m assuming you trying to bypass this, have a single tinyURL for the webApp and somehow pass CustomerID in it. If yes, then you can simple append the CustomerID query parameter in the tinyURL using personalisation block. Campaign will allow you to do it.
How to map it with the webApp URL is something that TInyURL API team has to explain. I’m not sure how you are generating tinyURLs but if you are using API, please see if there is a possibility there.
Do you have any clear working examples about how a workflow would be set-up that, queries data to target, defines SMS message content (including long URL), makes an API call to shorten each individual URL (appreciate provider would differ, but just looking for generic example), send SMS.