Data Integrations


Introduction (Pull vs Push)
Zerista Pull
Zerista Push
List of Registration Systems Integrated With


Introduction:

Zerista data integration involves transferring of data from registration systems to Zerista powered client websites and mobile apps. Zerista integrates with various registration systems to transfer data pertaining to attendees, events, speakers, posters and exhibitors. The data integration process can be performed in one of 2 ways:

  • Zerista Pull (Zerista retrieves or “pulls” data from a registration system using their API.)
  • Zerista Push (Clients would load or “push” data into Zerista using Zerista’s API.)

Both processes have their advantages. Here’s more information on how these processes work:

Back to Top


Zerista Pull:

  • Data pertaining to a client’s conference (attendees, events, exhibitors etc) is generally stored in registration systems or client maintained custom databases.
  • Client’s provide Zerista access to their data via API’s or Web Services.
  • Zerista uses client provided API’s and develops integration functionality to transfer client data from registration system to Zerista supported client websites and mobile apps.
  • Examples of registration system API’s: RegOnline, Certain, Salesforce .
  • Pros:
    • Zerista does the coding work and saves time for client from learning about our API.
    • Zerista performed over 200 data integrations with over 50 different registration systems and is well versed with the integration process.
    • Zerista guides client through any data related issues (reporting data errors, suggesting client specific data changes for better attendee experience etc)
    • Data Integration cost is generally included in overall pricing model (No additional integration costs unless integration is heavily customized. May vary from client to client.)
  • Cons:
    • Transfer of data is not real time. Zerista pulls data from registration systems periodically. Typical “pull” times range from 5 minutes to once a day. So when an attendee registers in a registration system, there will be a “wait” time before he/she gets access to Zerista website or mobile app.

Back to Top


Zerista Push:

  • Data pertaining to a client’s conference (attendees, events, exhibitors etc) is generally stored in registration systems or client maintained custom databases.
  • Zerista provides client with an API that they use to transfer or “push” their data to Zerista.
  • Client develops integration functionality (writes code or hires developers to write code) to “push” their data into Zerista using Zerista’s API.
  • Information about core Zerista API’s (Users, Events, Exhibitors) can be found on this very site.
  • Pros:
    • Client can push data in real time. When an attendee registers in a registration system client could push that attendee into Zerista in real time giving the attendee access to Zerista platform almost immediately.
  • Cons:
    • Client might have to incur development costs for the integration to be developed.
    • Client (or integration development team hired by client) will have to keep track of any data issues (maintain error reports of failed data pushes, communicate the same with Zerista in order to fix them etc).

Integration Statistic: 85 percent of the integrations Zerista handled fall under the “Zerista Pull” category.

Back to Top


List of Zerista Integrated Registration Systems:

Talk to your Zerista sales/account rep to find out if we support your provider!

Back to Top