Skip to content
  • There are no suggestions because the search field is empty.

Integration with MapYourShow (MYS)

If you are using MapYourShow (MYS) for your event management and have a Gleanin Pro subscription, you can seamlessly import your exhibitor data through our data integration feature.

Integration setup
Data import
Outbound integration
Data reference

Setting up the integration

The MYS integration requires Pro and needs a one-time activation by your MYS account manager before you can connect.

  1. Once your event is set up in MYS, ask your MYS account manager to email hello@gleanin.com to confirm that the event and the MYS Event ID you wish to integrate are owned by your organisation. Include the MYS Event ID in the email — do not share passwords or access keys.
  2. Once we have added the ID, log in to your Gleanin account and go to Integrations in the left-hand menu.
  3. Click the plus icon and select MYS.
  4. Choose the type of integration: Speakers & Sessions or Exhibitors.
  5. Select your Map Your Show Event ID from the dropdown. If the correct event ID is not shown, contact us at hello@gleanin.com.
  6. Click Next to verify your credentials. If correct, you will move to the formatting options step to complete setup.
  7. If setup fails, check with your MYS account manager that the Event ID is correct and that access has been granted to Gleanin. If problems persist, contact us at hello@gleanin.com.

Data import

Once connected, you trigger syncs manually:

  1. Go to Integrations in the main menu.
  2. Click the import icon on the right side of your MYS integration.
  3. A green dot on the clock icon confirms a successful import.

Sync time varies with data volume — typically a few seconds, occasionally up to an hour. A red background on the integration card means the sync failed; try again. If it stays pending for over an hour or fails repeatedly, contact us at hello@gleanin.com.

Outbound integration

Once your exhibitor data is imported and your campaign is configured, you can send personalised exhibitor links back to MYS. This feature is available for exhibitor campaigns only.

  1. Complete the inbound data sync first.
  2. Ask your MYS account manager to add a custom field named gleaninexhibitorlink for exhibitors on that event.
  3. In your Gleanin account, go to Integrations and click the plus icon next to the Outbound section on your MYS integration.
  4. Select the campaign whose links you want to send to MYS.
  5. Click Check custom field to verify it has been added on the MYS side.
  6. If verification passes, click Create.
  7. Click the Initiate Export icon to transfer campaign links to your MYS event.

To remove the outbound integration, click the Trash icon. This will not remove any links already sent to MYS.

Data reference

The tables below show which MYS fields Gleanin reads by default and what each is used for. Any other MYS attribute can be mapped to a Gleanin field or custom field per event, so these are the defaults rather than the limit.

Speakers

MYS field What we use it for
firstname Speaker's name (joined with lastname)
lastname Speaker's name (joined with firstname)
title Job title
company Company name
photourl Speaker photo — ignored unless it points at an actual image file
email Speaker's email
speakerid The ID we match on, so re-syncs update the speaker instead of duplicating them
schedules[] Source of the speaker's sessions and the speaker↔session links
conferenceid Tells us which conferences to fetch speakers for
speakersessionstatus

Filtering — only speakers marked "Approved" are imported. If this field isn't present, all speakers are imported

Sessions

Sessions are derived from each speaker's schedules[] array. The same session appears once per speaker assigned to it; Gleanin de-dupes by sessionid.

MYS field What we use it for
sessiontitle Session title
starttime Session schedule (combined with endtime into one display string)
endtime Session schedule (combined with starttime)
sessionid The ID we match on and de-dupe by

Exhibitors

MYS field What we use it for
exhid The ID we match on and use to fetch each full exhibitor record
exhname Exhibitor name
booths[0].boothnumber Stand code (can be pointed at a different field per event)
email Exhibitor's email — or the first contact's email if that option is enabled for the event
logo Exhibitor logo
vipcode Discount code
isactive Filtering — exhibitors where this is not set to 1 are skipped
contacts[] Fallback source for the email address