최근 검색


최근 검색 없음

Andrew Dietrich's Avatar

Andrew Dietrich

가입한 날짜: 2021년 4월 14일

·

마지막 활동: 2021년 10월 27일

팔로잉

0

팔로워

0

총 활동 수

34

투표 수

5

플랜 수

24

활동 개요

님의 최근 활동 Andrew Dietrich

Andrew Dietrich님이 에 댓글을 입력함

커뮤니티 댓글 Discussion - Tips and best practices from the community

Hi Sajan,

The coloring of the text looks good from what I can see, but I can't see the end of your code  -- are you using the closing script tag? And what are the errors?

댓글 보기 · 2019년 2월 20일에 게시됨 · Andrew Dietrich

0

팔로워

0

투표 수

0

댓글


Andrew Dietrich님이 에 댓글을 입력함

커뮤니티 댓글 Discussion - Tips and best practices from the community

Hey Matt,

 

Unfortunately we wouldn't capture that by default. The workaround detailed in this post includes OS data, though. 

댓글 보기 · 2018년 11월 29일에 게시됨 · Andrew Dietrich

0

팔로워

0

투표 수

0

댓글


Andrew Dietrich님이 에 댓글을 입력함

커뮤니티 댓글 Discussion - Tips and best practices from the community

Hey Matt,

To clarify since you mentioned mobile OSs -- are these requests that are via the mobile Help Center access through a browser, or are they requests from a Mobile SDK implementation? The two capture different sets of information.

If you go to the events view of a ticket submitter through a mobile browser, the initial comment will have a user agent string that looks something like this:

  • Mozilla/5.0 (Linux; Android 6.0; LGUS991) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.80 Mobile Safari/537.36
  • 107.77.206.22
  • IL, United States

The top bullet point is called a user agent string and can be decoded using a site like http://www.useragentstring.com/ to see what browser they are using. Note that this string does not include the OS version nor the model/make; just the mobile browser info.

Meanwhile if you go to the events view of a ticket submitted via the SDK, you get something like this:

  • Zendesk-SDK/2.0.0 Android/23 Variant/Support
  • 12.345.6.78
  • 12, India

This includes the OS and SDK version, but not the make/model. However, if you hit the ticket audits API endpoint of the ticket, the SDK does capture that data in a "metadata" object. It looks like this:

"custom": {
"sdk": {
"device_used_memory": "825",
"device_manufacturer": "samsung",
"device_os": "6.0.1",
"device_total_memory": "1383",
"device_battery": "100",
"device_name": "j5lte",
"device_model": "SM-J500F/j5lte",
"device_low_memory": "false",
"device_api": "23"
}
}

More about the ticket audits api endpoint here:

  https://developer.zendesk.com/rest_api/docs/support/ticket_audits 

댓글 보기 · 2018년 11월 27일에 게시됨 · Andrew Dietrich

0

팔로워

0

투표 수

0

댓글


Andrew Dietrich님이 에 댓글을 입력함

커뮤니티 댓글 Q&A - Help center and community

Hi Jo! Sounds like a unique use-case. I've opened up a ticket for further investigation on this -- you should receive an email shortly.

댓글 보기 · 2016년 7월 28일에 게시됨 · Andrew Dietrich

0

팔로워

0

투표 수

0

댓글


Andrew Dietrich님이 에 댓글을 입력함

커뮤니티 댓글 Discussion - Tips and best practices from the community

Hi Cristin,

At this time there is no workaround for this, unfortunately. If a customer would like to change their rating after its initial setting, they need to log in.

댓글 보기 · 2015년 5월 10일에 게시됨 · Andrew Dietrich

0

팔로워

0

투표 수

0

댓글