API Reference

Get Exhibitor Analytics By Exhibitor Id

  • API used at host side event admin, super admin, and organizer admin can access this API.
  • This API will return all exhibitor data like exhibitor name, chat message count, click count average lead rating, document downloaded, meeting booked, etc.
  • We need to pass an authorization token here, which is generated after successful login into the account.

Attribute

Description

Id

It will return the unique id of the exhibitor

Click Count

It will return a count of how many, attendees click on the Request more information button. this will give more information about the product

Views By Unique Users Count

It will return the count of how many unique attendees go through the expo page.
unique means if attendees have only one email address (not a duplicate account with the same email )

Document Download

It will return a count of how many attendees downloaded the documents

Unique Document Download

It will return a count of how many unique attendees downloaded the documents.
unique means if attendees have only one email address (not a duplicate account with the same email )

Average Lead Rating

It is an average rating for the leads like
Hot: high interest in the product
Warm: medium interest in the product
cold: low interest in the product

Product Views

It will return the count of how many attendees go through the product view page

Chat Messages Count

It will return the count of how many, attendees
are chatting in the expo

  • Here are the possible error messages that return if any condition fails or required data is missing for processing.

Error Code

Description

200

Ok

400

The request could not be understood by the server due to malformed syntax

401

You are not authorized to view the resource

403

Accessing the resource you were trying to reach is forbidden

404

The resource you were trying to reach is not found

4030201

Not Event Host

4040027

Exhibitor Not Found

Language
Credentials
Header
Click Try It! to start a request and see the response here!