# Retriving click rates via Admin API

**URL:** <https://forum.ghost.org/t/retriving-click-rates-via-admin-api/41702>\
**Category:** Integrations & API\
**Created:** [October 7, 2023, 9:18pm UTC](https://forum.ghost.org/t/retriving-click-rates-via-admin-api/41702 "2023-10-07T21:18:28Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sobird](https://avatars.discourse-cdn.com/v4/letter/s/6f9a4e/32.png) [@sobird](https://forum.ghost.org/u/sobird)\
**Post date:** [October 7, 2023, 9:18pm UTC](https://forum.ghost.org/t/retriving-click-rates-via-admin-api/41702/1 "2023-10-07T21:18:28Z")

</div>

I’ve been looking into creating my own backend setup for an automated onboard sequence (see [previous discussion](https://forum.ghost.org/t/diy-email-sequence-via-scheduled-unpublish-republish-of-posts/38479)). Currently the plan is to use labels on users to track where they are in the sequence, and create and send a duplicate of each email in the sequence to the labelled segment.

This will create a lot of duplicate posts, so I plan to have a cleanup that runs every X days, pulls the email statistics (eg number of opens) from the duplicate post to store somewhere and then deletes the duplicate.

I notice Ghost [now tracks clicks](https://ghost.org/help/post-analytics/) and other things like conversions and feedback response (which is awesome, thank you so much) and offers CSV export of that. The page also states that you can see which post a member converted on in the Member management. However, this new data doesn’t seem to be reflected in the [example post response in the Admin API](https://ghost.org/docs/admin-api/#the-post-object), or in the Member or Subscription objects.

My plan is still very early stages, so I don’t have a Mailgun instance to test against. Is this new analytics information available in the Admin API? Thank you.

(Also FYI the link on setting a custom source in that Post analytics page 404’s)

---

<div class="post-metadata">

**Author:** ![Cathy\_Sarisky](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cathy_sarisky/32/25750_2.png) [@Cathy\_Sarisky](https://forum.ghost.org/u/Cathy_Sarisky)\
**Post date:** [October 7, 2023, 9:36pm UTC](https://forum.ghost.org/t/retriving-click-rates-via-admin-api/41702/2 "2023-10-07T21:36:54Z")

</div>

I’d take a look at what the admin API is doing when you access those stats in /ghost. Open dev tools (F12), go to the network tab, and look at the endpoint and payload.

(This is seriously my best tip for all sorts of API work. Since the Ghost Admin page at /ghost is basically just making API calls, you can learn to do what it does just by copying it!)

---

<div class="post-metadata">

**Author:** ![sobird](https://avatars.discourse-cdn.com/v4/letter/s/6f9a4e/32.png) [@sobird](https://forum.ghost.org/u/sobird)\
**Post date:** [October 7, 2023, 10:24pm UTC](https://forum.ghost.org/t/retriving-click-rates-via-admin-api/41702/3 "2023-10-07T22:24:36Z")

</div>

That’s a great tip, thanks!

I have noticed that the API docs mark some elements as experimental, and the network seems to be querying endpoints that aren’t documented (such as member/events) to pull the statistics. So I guess my question shifts to whether there are plans to expose these as stable endpoints in the docs in future.

---

<div class="post-metadata">

**Author:** ![Cathy\_Sarisky](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cathy_sarisky/32/25750_2.png) [@Cathy\_Sarisky](https://forum.ghost.org/u/Cathy_Sarisky)\
**Post date:** [October 7, 2023, 11:22pm UTC](https://forum.ghost.org/t/retriving-click-rates-via-admin-api/41702/4 "2023-10-07T23:22:51Z")

</div>

The members endpoints are relatively new. I’m sure they’ll be stable and documented at some point. :)

---

<div class="post-metadata">

**Author:** ![sobird](https://avatars.discourse-cdn.com/v4/letter/s/6f9a4e/32.png) [@sobird](https://forum.ghost.org/u/sobird)\
**Post date:** [October 8, 2023, 12:02am UTC](https://forum.ghost.org/t/retriving-click-rates-via-admin-api/41702/5 "2023-10-08T00:02:34Z")

</div>

Ahh, I didn’t realise they were new. Thanks for your insights. :)
