You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tagging links is useful for tracking certain aspects of the Shlink ecosystem. The drawback is that these tags must be manually applied to any generated link.
What are your thoughts on having a "rules engine" where you can specify that if x then apply tag y?
For instance, if I wanted to track all links which are "media links", I could have a rule like:
if domain in ["youtube.com", "vimeo.com", "twitch.tv"], then apply ["media", "medium-retention"] tags
I think this would be quite useful, even if the rules engine is only capable of parsing the destination link for the standard fields: scheme, domain, path, params, etc.
Beyond this, tagging links based on other metadata could also be useful:
Tagging based on which API key was used to generate said link
Tagging based on time of day
Tagging based on incoming IP address
etc.
But this increases the scope. Even just URL parsing tagging is desirable. IMO.
The text was updated successfully, but these errors were encountered:
Summary
Tagging links is useful for tracking certain aspects of the Shlink ecosystem. The drawback is that these tags must be manually applied to any generated link.
What are your thoughts on having a "rules engine" where you can specify that
if x then apply tag y
?For instance, if I wanted to track all links which are "media links", I could have a rule like:
if domain in ["youtube.com", "vimeo.com", "twitch.tv"], then apply ["media", "medium-retention"] tags
I think this would be quite useful, even if the rules engine is only capable of parsing the destination link for the standard fields: scheme, domain, path, params, etc.
Beyond this, tagging links based on other metadata could also be useful:
But this increases the scope. Even just URL parsing tagging is desirable. IMO.
The text was updated successfully, but these errors were encountered: