How to Import data from A2Z?

Modified on Tue, 3 Nov at 9:00 AM

Exhibitors (REST API)

Use the A2Z REST import to bring exhibitor data into the Conference App Builder. Ask your A2Z representative for the following two items:

  1. Event ID
  2. Tenant ID

To set up the import:

  1. Access the Conference App Builder (From our website, choose Organizer Login > EventPilot on the top right)
  2. Select your project
  3. Navigate to Expo > Exhibitors
  4. Click Add Import
  5. Give your data source a name, e.g. A2Z
  6. From the "Import Source Type" dropdown, choose A2Z (REST)
  7. Next
  8. In the Data step, enter the EventID and Tenant IDyou received from A2Z
    • Optional Fields:
      • Upgrade Mapping: To override the upgrade levels as provided in the A2Z data, enter a comma-separated list of the "upgradeLevelId" (1, 2, 3 etc...) and desired labels. Example: 
      • Custom Code: Used only if your organization has a custom parsing script
  9. Select Next and complete the field mapping. Common mappings include:
    • Exhibitor ID to Exhibitor ID
    • Title to Organization Name. A2Z supplies this from the exhibitor’s exhibiting-as name.
    • Description to Description. A2Z supplies this from the online profile. You can instead map Description plus Subcategories to append a Categories line containing product subcategories.
    • Type to Exhibitor Type when you use A2Z sponsorship or upgrade levels, such as Silver Sponsor or Gold Sponsor. The import uses the level description directly; no numeric level mapping is needed.
    • Default Type to Exhibitor Type instead of Type when all records should use the label Exhibitor.
    • URL to Organization Website
    • Email to Email when the booth contact email should appear in the exhibitor detail view. Otherwise choose -- Do Not Import --.
    • Image to Organization Logo
    • Location to Location for booth numbers. You can instead map location_padded for four-digit numeric padding, location_prefixed for a label such as Booth 0001, or loc_prefix_no_pad for Booth 1. Padding changes numeric sorting from 1, 10, 2, 20 to 0001, 0002, 0010, 0020.
    • Categories to an available filter field when attendees should filter exhibitors by product category.
    • Subcategories to an available filter field when attendees should filter exhibitors by product subcategory. Categories and subcategories use pipe-separated values, which also allow names containing commas.
    • Map any custom fields labeled CF: <field name> to appropriate available filter fields when you want to include them. Choose -- Do Not Import -- for fields you do not want to display.
  10. Next
  11. Your import will complete. Review the Results tab, which will let you know if any records were skipped.

Media (Press Releases & Social Media) — REST API

Both press releases and exhibitor social media links are available for import. 

  1. EventPilot App Builder > Media > Media Data
  2. Click Add Import
  3. Give your data source a name, e.g. A2Z Social Media
  4. From the "Import Source Type" dropdown, choose A2Z Social Media (REST) or A2Z Press Releases (REST)
  5. Next
  6. Enter the same EventID and Tenant ID used for the Exhibitors import
  7. Select Next and review the field mapping. Leave the automatic mapping in place. Common mappings include:
    • Media ID to Media ID
    • Exhibitor ID to Exhibitor ID so the item links to the correct exhibitor.
    • Title to Title
    • Type to Media Type
    • URL to URL for social media links.
    • Body to Description for press release content.
    • Subtitle to Subtitle when the press release should display the label Press Release.
    • Icon to HTML Icon
    • MediaType Filter to Filter 4 to identify Social Media or Press Release items.
    • The available fields depend on whether you selected social media or press releases.
  8. Your import will complete. Review the Results tab for any skipped records.
  9. Repeat these steps to set up the other import source, if you are using both. 

Press releases and social media links are retrieved automatically for exhibitors. No additional setup is required beyond the import sources above. Large exhibitor lists may take longer to import because press releases are retrieved for individual booths.

FAQ

How do I import changes after the initial setup?

Go to Expo > Exhibitors, expand the import card if needed, and click Import beside your existing source. Review the Results for skipped records. If you also use related media imports, re-run those sources as well.

Will importing changes immediately update the attendee app?

Importing updates the Conference App Builder. Use Publish Proof Data to review the changes in the proof version, then Publish Live Data when they are ready for attendees.

Can I exclude contact emails or other fields?

Yes. Set fields you do not want to display to -- Do Not Import -- in the field mapping.

When should I use Custom Code?

Leave Custom Code blank for the standard import. Use it only when your ATIV Project Manager provides instructions for a custom import.

Which A2Z import source should I choose?

Choose A2Z (REST) for exhibitors. This article covers the supported REST integration.

How do I import sponsorship levels?

Map Type to Exhibitor Type to use the upgrade level descriptions configured in A2Z, such as Silver Sponsor or Gold Sponsor. If you do not use sponsorship levels, map Default Type to assign Exhibitor to all records.

Do press releases and social media require separate imports?

Yes. Under Media > Media Data, add A2Z Press Releases (REST) and/or A2Z Social Media (REST). Use the same Event ID and Tenant ID as the exhibitor import and leave the automatic media field mapping in place.

Why is some exhibitor information missing?

Check that the information is populated in A2Z and that the corresponding field is mapped in the Conference App Builder. Review the import Results for skipped records. For missing press releases or social links, also check that the appropriate media source has been imported.