Feature Request – Surface documentation usage metrics

[chrisdeso]

Is your feature request related to a problem? Please describe. Currently, it's not possible to know how/if published documentation is being used.

Describe the solution you'd like Allow users/teams to pull metrics from published documentation.

Describe alternatives you've considered An API would be wonderful 😄.

[sankalp0o]

@chrisdeso metrics like?

[prashantagarwal]

@sankalp0o Just basic things like documentation views, referrer, location from where this documentation was viewed, average time spent by users on documentation page etc. I think Google analytics like metric will help a lot.

Also even better would be to offload all this to users only by allowing them to integrate third party plugins with our documentation, so they can integrate things like Hotjar, GA or Intercom etc if they want.

[keranm]

Hey there As a paying customer, it's pretty critical that I can do the following on documentation pages & buttons:

• Track page/section usage (to validate the spend & to work out what areas need improvement)
• Understand how many people are clicking the "Run in Postman" button, and where from (your site, our site etc)

I'd be totally cool with simply being able to add Google Analytics or Segment tracking to the pages - I don't expect Postman to write tools for this he he he .. just let us integrate the common tracking tools onto the pages

Thanks folks K.

[enviapaqueteria]

If you could let us integrate with Google Analytics would be enough!

[danioso]

Hi guys, what is the status of this? I would like to be able to include my own Google Analytics code

[pjohnson31]

"If You Can't Measure It, You Can't Improve It." Reporting and analytics are table stakes for any organization looking to iterate and improve their products. How many people are coming to our API docs site? what pages are they looking at? what pages take a long time to read? which pages aren't getting many views? How are they finding our site?

Without data/analytics - we cannot answer any of those questions above. If you cannot measure something, you cannot expect it to improve.

FWIW, I work at a company that makes customer support software- and we sell a while label help center product very similar to this (instead of API docs, we allow you to make FAQs and help articles). I totally understand that building a native analytics/reporting suite is a high level of effort and not the first thing you should build. But that doesn't mean you should stop us from integrating/supporting 3rd parties.

Adding a new setting to the page which allows you to embed code on the help center (or even a simple text input for adding your google analytics ID) should be an extremely trivial level of effort development wise. I'm shocked this doesn't exist.

[pkrish2]

Just being able to embed a tracking tag from Google Analytics would be enough! I, too, am shocked that this is not possible yet. I am thinking of moving off of Postman Documentation because I am not able to track anything on the webpage.

[eyalgrossdev]

We are a paying client and would also like the ability to add a Google Analytics tracking / ID code to the documentation.

[NicolasMassart]

Adding a Google Analytics or a Google Tag Manager would be very appreciated. We are currently using both doc systems as an experiment, our own API doc and Postman doc. But ours provides stats and not Postman. We can't decide which one suits users best. Long term, if Postman is not able to provide this basic feature, we will have to choose between just a nice Postman UI and a site that enables us to improve, know our users, and still be able to improve our UI...

[tank104]

We too would love to be able to drop either Google Tag Manager, or Google Analytics tag in to track page views. Tag Manager would allow more functionality (as we could use it in marketing to tell if a prospective user has more intent - since looking through our APIs would indicate more interest).

[rafal-bouncer]

I didn't really thought there might not be that feature when deciding to use postman for our public docs. This feature is crucial for inbound sales process.

[wrydere]

+1 for this. Really need to see the interaction between our API docs and the rest of our web properties, so we can understand feature usage!

[jardelvdm]

More than 4 years and this very important basic request has not even been considered?

[nickjuntilla]

Hi guys I was just asking for this feature and was sent here. Now that I see it's 4 years old I don't have much hope. Real question. Why does postman prioritize obscure edge features over core features?

[Gregb87]

Adding my voice to this request. Recently we have been asked by our Marketing team to implement some code for the Customer Data Platform 'Segment' they are using. Part of the implementation involves adding some basic tracking to webpages (somewhat similar to Google Analytics). However, doesn't seem that this is possible with Postman.

Thanks,

[Steve-Varga]

+1 for this. We really need this feature.

[zachtil]

As a paying client, we need to be able to track API Documentation usage, check analytics, but also integrate third-party tooling such as Google Tag Manager.

Voting for having this enabled.