Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using URL shorteners when distributing surveys #95

Open
AndrejKiri opened this issue Feb 19, 2025 · 1 comment
Open

Using URL shorteners when distributing surveys #95

AndrejKiri opened this issue Feb 19, 2025 · 1 comment

Comments

@AndrejKiri
Copy link
Contributor

I noticed that in sig-end-user, we use URL shorteners when posting on socials. URL shorteners can be helpful when conducting surveys. They often track data about impressions and engagements, that we can use to calculate survey KPIs like response rates (Google Forms do not collect this data). Also, by creating multiple links for each distribution channel, we can break down the KPIs per channel. Right now, we are not doing that.

I suggest to:

  1. Find out what URL shortener do we use and how (who is the owner, how does it fit to the process of survey distribution currently, etc.)
  2. Explore what features are available and how can we make use of them
  3. Document guidelines around using it in the Community survey best practices

Example screenshot from a LinkedIn post promoting one of our surveys:
Image

@AndrejKiri
Copy link
Contributor Author

I reviewed Buffer.com that OpenTelemetry folks use for posting on social media (LinkedIn, Bluesky, Mastodon). Unfortunately, it is not very helpful for the use case I am describing above. Drawbacks:

  1. Not possible, create a shortened link that we would be able to use, e.g. on a website banner. This way we inevitably end up with an incomplete picture.
  2. Link analytics works only for LinkedIn but not for Bluesky and Mastodon. Again, even more incomplete picture.
  3. It automatically creates a unique shortened link for each post, what is annoying if you need to do calculations per survey.

My conclusion is that if this is interesting for us, we should look into a specialized shortening tool, like bit.ly. Having said that, Buffer has a lot of its own benefits, so I am not suggesting to drop using it.

Thanks for the Buffer.com access @avillela. Feel free to remove me from the org.

As a next step, I will look into bit.ly and suggest how we might start using it to better track survey KPIs.

FYI @reese-lee @danielgblanco

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant