wordpress-mobile / wordpress-mobile/WordPress-Android
Zendesk Analytics
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
We'd like to implement some analytics events for Zendesk, however the current sdk we use doesn't have callbacks for events: https://developer.zendesk.com/embeddables/docs/android-support-sdk/nutshell whereas the v1 of the same SDK did: https://developer.zendesk.com/embeddables/docs/android/handle_events. We contacted Zendesk about this and waiting for a reply from them.
We discussed the situation with @aerych and we decided to only implement one event for now (PR incoming) support_help_center_viewed which fortunately doesn't need the callback functionality. For the other events listed below, we decided to wait for it as we can't implement the failed versions right now and not all the success versions can be tracked correctly. For example, the user could go to the Help Center and then create a ticket and the only way we can know about that is through a callback.
The events that still needs to be implemented:
SUPPORT_HELP_CENTER_USER_SEARCHED,
SUPPORT_NEW_REQUEST_CREATED,
SUPPORT_NEW_REQUEST_FAILED,
SUPPORT_NEW_REQUEST_FILE_ATTACHED,
SUPPORT_NEW_REQUEST_FILE_ATTACHMENT_FAILED,
SUPPORT_NEW_REQUEST_VIEWED,
SUPPORT_TICKET_LIST_VIEW_FAILED,
SUPPORT_TICKET_LIST_VIEWED,
SUPPORT_TICKET_USER_REPLIED,
SUPPORT_TICKET_USER_REPLY_FAILED,
SUPPORT_TICKET_USER_VIEWED,
SUPPORT_TICKET_VIEW_FAILED,
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Zendesk Android Support SDK event documentation linked in the issue and confirm whether the required callbacks are available. Track the listed support events once the SDK supports them, including failed variants where applicable; the work is done when the events can be recorded accurately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- analytics, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100