All Collections
Exhibitors
My Leads
Exporting my team's connections and leads
Exporting my team's connections and leads
Updated this week

Participating in an event as an Exhibitor, you might find it useful to export, in an XLS file or via API, your team's connections and generated leads, including any notes, scores, and qualification forms of your team members. This facilitates their upload into another platform, like a CRM system.

🚫 Feature Access Restrictions
Access to exporting specific leads and using the Exhibitor API is at the discretion of the event organizer. If you wish to collect more leads or utilize the API, please reach out to the organizer for permission.

How to export my leads as an exhibitor

1. Export my leads in a .xls (Excel) file

You can export all your leads in a single Excel file (.XLS) at any moment.

Access the Exhibitor Center, and click into Leads tab located in the left sidebar, and then click on the Export leads button on the top right corner.

You have the ability to Export all leads or Define specific dates and leads to exports.

Exhibitor can define which leads to export and during which time range, and export them in an Excel file.

2. Export my leads via API

You also have the option to automate the export of your leads directly to your CRM or Marketing Automation Tool using the Exhibitor API, provided you have obtained permission from the event organizer.

To do this, navigate to the Exhibitor Center, select Leads, and then API Keys.

Here, you can create a new key by clicking on Create key. Assign it a name, click Generate key, and then ensure you copy and securely store the key. Remember, once you close the modal window, you won’t be able to view the key again. If it is lost, you will need to generate a new one.

Next, utilize the GraphQL Exhibitor API to export all your leads. You can access the API documentation here.

Remember, all GraphQL API queries necessitate a valid access token.

Incorporate your API key as an Authorization header in every API query you make.

For platform security, verify that the user linked to the token is assigned a role with the necessary permissions.

Did this answer your question?