Plan your implementation

Get data in and out of Regal in as little as 5 min

You can implement Regal in a few different ways to ensure it fits with the rest of your tech stack seamlessly. Most of the options require no engineering effort on your end.

A complete Regal "integration" includes:

  • DATA-IN: Sending Regal your contacts and event data
  • DATA-OUT: Receiving Regal event and reporting data back

DATA-IN: Sending Data to Regal

  • Already collect data with a CDP, CRM or ESP? All of those are great sources of customer profile and event data to send to Regal, and none require you to do engineering work.
  • Need to start tracking the right data? You can start by adding Regal's site tag to your Google Tag manager or call the Regal API directly.

Already collect data with a CDP, CRM or ESP?

Customer Data Platform (CDP)

If you already use a CDP, like Segment, you can get up and running with Regal in seconds. Supported CDPs include.

CRM

If you already send events and customer profile data to a CRM like Salesforce or Hubspot, you can easily send that data to Regal. Note, however, that if those CRMs are only updated e.g., once per hour or day, then the data that gets into Regal will also only be as fresh as the data in your CRM.

ESP

If you've already invested a lot in getting rich customer profile and event data into your ESP, many ESPs like Iterable and Braze allow you to setup workflows and webhook data out to a 3rd party like Regal. These can be a quick and easy source for getting your customer profile and event data into Regal.

Need to start tracking the right data?

If the customer and event data you would like to send to Regal does not already exist in your CDP, CRM or ESP, you can use one or both of the below approaches to integrate with Regal.

  • Site tag: Integrate Regal directly into your website by inserting the Regal tag in your Google tag manager or any other tag manager you work with. This is the easiest integration path to get started and requires no engineering on your end.

📘

Opt-In Forms

An additional benefit of the Regal tag is that it can be used to trigger and render compliant opt-in forms on your site so that you don’t have to build those yourself.
Email [email protected] for the Regal Tag and Installation Guide.
Segment destination: If you have a Segment account, you can add the Regal Destination to send us both front-end (website and app) events and server-side events.

  • Direct API Integration: If you prefer, you can send user events by having your engineering team call the Regal API directly. This is typically the best solution for home-grown CRMs. While this method requires engineering effort, most companies have successfully implemented the Regal API in less than a week as there is only a single endpoint to integrate with.

DATA-IN: Summary

Integration Method

Requires Engineering on Your End?

Time to Implement

Regal Site Tag

No

< 5min

Segment

No

< 5min

mParticle

No

< 5 min

Salesforce

No

< 1 hour

Hubspot

No

< 1 hour

SimonData

No

< 1 day

Klaviyo

No

< 1 hour

Braze

No

< 1 day

Iterable

No

< 1 day

Customer.io

No

< 1 day

Zapier

No

< 1 day

Kustomer

Yes

< 1 day

Regal API

Yes

< 1 week

DATA-OUT: Receiving Data Back from Regal

Regal supports two ways for you to receive data back from the platform. They are not mutually exclusive (you can receive both real-time event data and canned reports):

1. Real-time event data. Regal publishes event data back in real-time to several destinations:

  • Segment
  • Kustomer
  • Salesforce
  • Hubspot
  • Reporting Webhooks (to an endpoint of your choosing)

2. Amazon S3 If you do not support one of the above ways to receive real-time event data, you can instead receive data directly to an Amazon S3 bucket.

Platform

Events

Kustomer

agent.activity.updated
call.completed
call.recording.available
contact.attribute.edited
contact.created
contact.experiment.assigned
contact.subscribed
contact.unsubscribed
sms.conversation.completed
sms.queued
sms.sent
sms.undelivered
sms.received
task.canceled
task.created
task.reservation.accepted
task.reservation.created

Hubspot

call.completed
call.recording.available
contact.created
sms.conversation.completed
sms.sent
sms.received

Reporting Webhooks

agent.activity.updated
call.completed
call.recording.available
contact.attribute.edited
contact.created
contact.experiment.assigned
contact.subscribed
contact.unsubscribed
sms.conversation.completed
sms.queued
sms.sent
sms.undelivered
sms.received
task.canceled
task.created
task.reservation.accepted
task.reservation.created

Salesforce

call.completed
call.recording.available
contact.attribute.edited
contact.created
contact.experiment.assigned
sms.conversation.completed
sms.sent
sms.received

Segment

agent.activity.updated
call.completed
call.recording.available
contact.attribute.edited
contact.experiment.assigned
contact.subscribed
contact.unsubscribed
sms.conversation.completed
sms.queued
sms.sent
sms.undelivered
sms.received
task.canceled
task.created
task.reservation.accepted
task.reservation.created


Did this page help you?