Export traffic data as csv/excel/ods document

[garethjax]

Summary

Shlink it fantastic, but i think it would greatly benefit from a tabellar export.

Context

many people who use url shorteners regularly, for business reasons, need to present data in a "digestible" format. A Pdf export would be a quick answer to that, but it's feasible only for a single "project" and the data is "static" and cannot be further analyzed.

An export of data in tabellar form is quite more useful, because you can further process it in a Spreadsheet (excel, open office, google docs, etc.).

What should be the format of the export

This is just a feature proposal, not an order :)

In its simplest form, the client could simply output the "table" as a file, with the fields enclosed by double quotes, to prevent import issues. (the export in excels or open office, should prevent this case).

The current selected date should work as filter.

Most people skilled in spreadsheet could then filter them and pivot to obtain the data desired.

optional

In a separate sheet (so it's a feature only for excel or open office), the client may output a list of hits sorted by date to replicate the main chart seen on screen.

I've seen it happens in the Google search console export feature, it's probably used to generate the chart quickly.

That's some ideas i've thought so far, thanks for this nice shortener!

[acelaya]

Sounds good 🙂

Also, for more complex integrations, remember that shlink already exposes a fully-featured API (the one consumed by shlink-web-client to generate the charts and the table), in case you need other custom systems to represent the data on a different way (see https://shlink.io/documentation/api-docs/).

But yeah, exporting directly from the UI is also something nice to have an useful in many scenarios.

[garethjax]

Awesome! Il giorno lun 14 dic 2020 alle ore 13:30 Alejandro Celaya < notifications@github.com> ha scritto:

…

Sounds good 🙂 Also, for more complex integrations, remember that shlink already exposes a fully-featured API (the one consumed by shlink-web-client to generate the charts and the table), in case you need other custom systems to represent the data on a different way. But yeah, expiring directly from the UI is also something nice to have an useful in many scenarios. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#349 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2MUETJXJ4ZAZDU4NVLTRLSUYANFANCNFSM4U2MRLCA> .

-- Kind regards *Andrea Scarpetta* Seo And Ceo mobile:(+39) 3291413121 blog:http://www.andreascarpetta.com