Jomablue can be connected to external systems to facilitate programmatic data flow of registration data, interactions, engagement scoring and more. 

There are two methods of accessing data in Jomablue, either via the public API or using a Jomablue built connector.

Public API

Introduction
This Public API is available to all enterprise subscribers and is focused around querying data from Jomablue. You would use this API if you wanted to build your own functionality in BI tools or extend functionality of your existing systems. 

Example
You are a service provider of a BI tool and you would like to chart some data of people attending the event. You could make requests to the Jomablue Public API to determine the segments of people registered (eg: By Country, Business Type or Employee Counts)

When to Use it
Use the Public API when you are building your own extensions to your current products. 

Use this to build a Tableau or Domo connector, a widget for your own custom dashboards or build "click to view event data" functionality in your CRM.

Things to Consider

  • Available out of the box to enterprise subscription customers
  • Used if you want to create your own read only integration with Jomablue
  • Don't see what you need? It's extensible on request (may incur a fee)

Jomablue Connector

Introduction
A connector that is built and maintained by Jomablue that sits between Jomablue and an external system (Salesforce, Marketo etc) that is responsible for fetching, transforming, updating and batching data between the two systems. 


Example
You use Salesforce internally and you want to ensure Jomablue contributes to the data in Salesforce without the concern of disparate data. Jomablue build a connector that pushes new registration data to Salesforce along with realtime interaction data from the event. The connector is configured to transform data to be meaningful to the Salesforce users as well as batching to ensure no Salesforce API limits are hit. 


When to Use it
Use a Jomablue connector when you have CRM and internal data models already defined. In addition, if data needs to frequently move between systems and be transformed during this journey to comply with business rules or rate limits imposed by external systems.

Use this when connecting Jomablue to Salesforce, Dynamics365, Marketo, Marketing Cloud etc. 


Things to Consider

  • The most flexible offering for connecting two systems programatically
  • Typically built in 3-6 weeks after requirement gathering
  • Jomablue can offer realtime push of data, this can often be cost prohibitive with the structure of some CRM's API pricing structure. Therefore minute by minute batching is an alternative within a Jomablue Connector.
  • The connector can be considered as ETL between Jomablue and other systems

Did this answer your question?