Community Metrics Keys (List)
Originally posted in https://community.khoros.com/t5/Admin-Metrics/About-Community-Admin-Metrics-and-Definitions/tac-p/745216#M76 but most likely people in need of such a list are not gonna find this directly, so I make it a separate post that hopefully can be found more easily. As it has been difficult (like forever) to find a comprehensive list of all available metric keys for a variety of use cases like building ranking formulas, badge rules, API queries etc. I have parsed various resources and compiled the following JSON list of metric keys. As I mentioned in the original post, this is a programmatically extracted and compiled list, there might be errors (please let me know if you find any, and also if you know of other sources I've missed with keys that are not present in the list or information about keys that should be added, as description for example) and these keys have not been tested if they work for various features (like not all metrics can be used for badge rules for example). { "abandoned_registrations": { "source": [ "admin/metrics/advanced", "pdf/2017" ], "title": "Abandoned Registrations", "desc": "The number of new users registered, who abandoned during the process. Viewing Account Report Metrics The Lithium reports on a variety of metrics that are of interest in to those who are monitoring account activity for a community. The Account Reports metrics section lets you run reports on these metrics for users, roles, or for any node in the community (the community as a whole, categories, forums, or chats). You can also set the granularity of these reports (hourly, daily, weekly, or monthly) and select a start and end date. You can report on a single metric, or select up to five metrics to be included in a report." }, "abandons": { "title": "Abandoned Turns", "desc": "The number of times a user left a waiting queue voluntarily before reaching the chatting list. A user can leave the waiting queue multiple times during a single session. Incremental Abandonment", "source": [ "pdf/2017" ] }, "accepted_solutions": { "source": [ "admin/metrics/advanced", "api/v1/users/metrics", "pdf/2017" ], "title": "Accepted Solutions*", "desc": "The number of times messages were accepted as solutions. This metric counts solutions written and accepted as a solution by anyone in the community." }, "accepted_solutions_to_threads_ratio": { "source": [ "admin/metrics/advanced", "api/v1/users/metrics", "pdf/2017" ], "title": "Topics Ratio", "desc": "The number of Net Accepted Solutionsdivided by the number of Net Forum Topics. This metric gives an indication of the percent of topics that are being solved in the community, category, or forum. Topics Posted to Solution Accepted" }, "action_requests": { "source": [ "admin/metrics/advanced", "pdf/2017" ], "title": "Action Requests", "desc": "The total number of server requests that occur when a user post…631ViewsSign in to react to this post0Comments- ViewsSign in to react to this postComments
For now, authentication is still done with the APIv1 authentication mechanisms.
Email bounce handling on Khoros communities
Hello and a Happy New Year! 1. Does Khoros by default "from: [email protected]" apply bounce logic to notifications sent by the community? Inspecting the email sources I can see Variable envelope return path (VERP) being setup, so my assumption for this is yes, but how can we tell from an API if the user has a valid email address? 2. Upon changing the default "from" to "[email protected]" the return path no longer is what it was, instead it is the same as the from address, meaning I should be somehow responsible for dealing with bounces, is this assumption correct? 3. Is there a recommended approach on how to tell what emails coming to that address are bounced mails? How to tell which target email has bounced and what type it was? Searching the internet didn't provide much in terms of SDKs (we cannot use 3rd party providers like zerobounce / mailchimp etc) 4. How would I notify Khoros through the api to have feature parity, for detected bounces? Trying to investigate this myself, I found the following. Searching for user by email: v2 does not have this feature v1 returns 1 account for an email even though multiple exist (contradicting uniqueness described at rest v1 docs ) Updating user email verified status: neither allows setting the status v2 is read-only Updating user email notification preferences: v1 doesn't have an option to change email only preferences, all the other options are there v2 can only change "email_excluded" property Would this suffice from a product level? 5. Can Khoros be configured to use a custom SMTP relay for sending messages? no such configuration is available from the admin, and to my knowledge we are required to do through a company policy. Thank you in advance! Similar question https://community.khoros.com/t5/Developer-Discussion/Using-Hard-Bounce-Info-to-unsubscribe-people-in-their-IDP-and/m-p/669322ViewsSign in to react to this postCommentsCustom profile attributes tracking
We're storing some information on custom profile attributes that are located in the user's settings somewhere - REST CALL - /users/id/some_user_id_here/settings/name/custom_profile.course_1 . We need to be able to make those custom rest calls from every user and also see all users that accessed the page and check their custom attributes. Do you have suggestions on how this might work? We want to have this information in a DW.ViewsSign in to react to this postCommentsUsing Hard Bounce Info to unsubscribe people in their IDP and other connected email marketing tools?
I'm curious if anyone has implemented a way to use hard bounces to unsubscribe people from their community or even back to their database of record if they're using SSO? People join our site of which the community is a portion of what we offer them. I notice that some of the emails bounce back either because the person has disabled or deleted the account. Another portion of the people entered invalid email addresses. I am wondering if there was a way to use the hard bounce information from SendGrid or whatever platform is sending the community emails to inform our IDP that the email address is no longer working so we should unsubscribe them from receiving emails. Ideally by feeding this up to our IDP it would then also inform our email marketing tools to stop sending messages until the person has updated their account and provided a valid email address. Ideally I'd also like to make accounts that have failures switch to an "inactive state" if notifications are hard bouncing but not ban them incase they log back in and update their email address to a valid one. This will give me a sense of how many users go inactive. We do use SSO so I don't think we could set them to an unverified state if email bounces.ViewsSign in to react to this postCommentsAccess Denied Issues on developer.khoros.com
Hi all, We're experiencing some access issues for customers trying to get to bookmarked and shared links to developer.khoros.com. UPDATE (4/6/21 3:50PST): We're making progress with our hosting platform. Please continue to use the workaround if you're experiencing issues. We are working with our hosting platform to resolve the issues. Workaround: Access developer.khoros.com via Atlas. From the main Atlas menu, select Dev Network and then select the area of the Dev Docs you'd like to work with (Community, Care, Marketing). Please accept my apologies for the inconvenience.ViewsSign in to react to this postCommentsWhere do I store a large amount of data, for reference?
Hi folks, planning a custom component which will basically check the user's id against a pre-existing list. I imagine this list could grow into the thousands. What are my options for storing this data/list? One option I use for smaller datasets is a hidden post and simply store it as a comma separated string. Another option might be to store a string in a custom metadata field, I guess? Any ideas how large that could be? (I don't have access to a separate server.)ViewsSign in to react to this postCommentsAPI 2 not returning user who got role 25 minutes ago
Hi everyone. Curious about this. I added the role Moderator to a user 25 minutes ago, yet, when I use this query it doesn't return that user.. <#assign query = restadmin("2.0","/search?q=" + "SELECT id FROM users WHERE roles.name IN('Moderator') LIMIT 50"?url)/> <#list query.data.items as q> ${q.id}<br/> </#list> Does anyone know how long it takes for the API to catch up, or how long it should take? I think it shouldn't take this long..?ViewsSign in to react to this postComments
Freezing Kudos on a Topic on Classic
Hi all, Is there a way via either rest v1 or v2 (preferably the latter) to freeze the kudos for a given topic? I see that I can make a topic read only, but don't seen an obvious way to disable kudoing. Not sure if this is possible, but given gaps in the docs, I'm hoping that it's doable but that the field to update is not available with a select * query in the API browser. Thanks!ViewsSign in to react to this postCommentsNot able to access V1 API's form reference index.
Not able to access V1 API's form reference index. https://developer.khoros.com/khoroscommunitydevdocs/reference/community-api-1-object-index https://devdocportal.khoros.com/t5/Community-API-v1-Reference/bd-p/restv1docs?section=commv1&branch=AlbumViewsSign in to react to this postComments
631Views
0Comments
