Skip to content

campusM

← Have an idea for Ex Libris?

Your feedback matters to us. Help us improve campusM by telling us what you’d like to see using the message areas below. You can also can support something already posted.

We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.

For more information please review our FAQ and guidelines. Thank you.

How can we improve campusM?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

2 results found

  1. Add Delivered-Based Engagement Metrics

    At present, engagement rates are calculated using the number of notifications sent, rather than the number successfully delivered. This can produce misleading open rates, particularly where notifications are never received because, for example, the app has been uninstalled or the device is offline.

    It would be valuable to introduce delivery metrics alongside the existing analytics, allowing institutions to report on:

    Notifications sent
    Notifications successfully delivered
    Notifications opened
    Open rate based on delivered notifications rather than total sent

    We appreciate that defining what constitutes a "delivered" notification may not be straightforward (for example, where users have disabled push notifications), but having…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Analytics  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Improve Notification Analytics with Audience Breakdown and Notification IDs

    We're finding the current notification analytics difficult to interpret when a single notification is sent to multiple audience groups (e.g. students, staff and other users). The results are aggregated into a single dataset, making it impossible to understand how each audience has engaged.

    It would be valuable if analytics could:

    Break performance down by recipient group (e.g. Students, Staff, Other), rather than only showing combined figures.
    Include a Notification ID within the analytics export. This would allow institutions to map analytics back to the original notification, making reporting and analysis much easier.

    It would also be extremely useful if the…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Analytics  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?

campusM

Categories