Introduction

Historically, Vuture integrations have been built and controlled by the Vuture engineering team, and the Vuture product initiates all connections with our client CRMs by either requesting data from the CRM or pushing data back to the CRM.

With the Open API we are looking to reverse the flow of data, by allowing the CRM (or middleware) to push data into Vuture and then pull reporting information from our APIs or Data Warehouse (DWH). This will remove the dependency on Vuture’s engineers to build and support integrations, therefore allowing a faster time-to-market of CRM integrations.

Why We Built This

• Many customers have multiple contact stores, not necessarily in CRM, which are not available for email marketing: for example, internal HR platforms

• The Open API will allow an automated sync of contact information and engagement data from all business units

• Any platform without a Vuture integration will have the capability to provide email marketing data to Vuture and pull back business intelligence

• The legal CRM space now has more products than ever before, and we want to provide first-party integrations for every potential partner in a timely manner.

This article is a temporary placeholder on our Knowledge Base.  In future versions of this document we will be looking to answer the following questions:

• Who manages the contact information?

• Who determines the list structure

• Who handles subscription preferences and consent?

• What decides whether or not contacts are stored in CRM, Vuture, or both?

• What decides whether engagement data is stored in Vuture and/or CRM?

• Where do new contact records appear? How are they created?

• How often does the data synchronise? Is this a total sync or partial?

  • Event RSVPs could be more frequent than Consent, for example

• Do clients need a Data Warehouse subscription?

EXISTING SYSTEMS

Vuture already has several solutions for dealing with CRM data within our existing “pull–push” integrations that we can extract into a new series of services, wrapped in an API endpoint.

• List management

  • Creation of global list

  • View of contacts held within a list

• Bulk load contact information into a new list structure

• Bulk load contact information into an existing list

  • Add new contacts

  • Edit existing contacts

  • Remove contacts

• Bulk load contact additional field information

  • Typically RSVP data

• Report on email engagement

  • Email sent

  • Email opened

  • Links clicked

  • Forms submitted

  • Subscription changes

• Data Warehouse

Please contact your Customer Success Manager for more information.