Admins can now generate and manage short links with built-in UTM tracking parameters to monitor engagement across campaigns; this new Short Links Tracking feature makes it easy to see exactly where clicks are coming from. By configuring a custom slug and adding UTM details, you’ll get precise insights into how users interact with your call links.
Follow these steps to create and configure short links in the site; placeholders for screenshots are included so you can add images later.
First, navigate to the call you’re working with; then, open the About section and scroll down to the Links area. Here, you have two options:
Click Create link under the Link to call detail page or Direct link to create a submission option; the difference being where the user will be directed to, the first option will direct them to the call page where they will need to manually start a submission while the second option will direct them directly to the form submission.
A pop-up will appear showing the full URL to your call’s detail page. This is the destination URL for the short link.
In the same pop-up, you can now configure your short link:
https://sla.yt/e/{yourcompany}-
. For example, if your company slug is acme
and you enter presentation_phase
, the short link will become https://sla.yt/e/acme-presentation_phase
.As you fill in the slug and UTM values, you’ll notice the Full URL at the top of the pop-up updates in real time to reflect your configuration.
When everything looks correct, click Create Short Link. Your new short link, complete with UTM tracking, is now live and ready to use.
After creation, all your short links appear in the Links section under that call; you can edit, deactivate, or delete any link from this list. Editing a short link lets you update its slug or UTM values at any time, ensuring your tracking remains accurate as campaigns evolve.
spring_sale
, newsletter_may
).If your short link isn’t redirecting properly, verify the following:
%20
if necessary.If you still see issues, contact support to investigate any backend configuration problems.