How We Built More Than 100 Customer Success-Integrations for our Product

If there is one thing that sets Akita apart from its competitors in Customer Success software, it is our ability to ingest data from virtually any data source a customer may have. This includes:

• Visitor behavior captured by our Javascript SDK or Segment.com;
• Customer data sent to Akita using our RESTful API;
• 3rd-party integrations using publicly available APIs;
• Cloud databases and data warehouses; and
• Even retrieving data from a customers own API.

1. Visitor behavior captured by our Javascript SDK or Segment.com;
2. Customer data sent to Akita using our RESTful API;
3. 3rd-party integrations using publicly available APIs;
4. Cloud databases and data warehouses; and
5. Even retrieving data from a customers own API.

But writing integrations are hard! How do you do it? h2

The Scheduler runs continuously and finds those Integration Objects that require syncing. This takes into account their defined sync frequency (how many times per day) and the time that has elapsed since the last sync. Any Integration Objects that require syncing are then sent to the Retriever.

Not all Interaction Types are created equal. Some must be synced more frequently than others and some integration partners have higher API limits. We can sync data more or less frequently on a per-Provider / per-Interaction Type basis depending on the limits of the Provider and the needs of each customer.

But writing integrations are hard! How do you do it? h2

But writing integrations is hard! How do you do it? h3

The Scheduler runs continuously and finds those Integration Objects that require syncing. This takes into account their defined sync frequency (how many times per day) and the time that has elapsed since the last sync. Any Integration Objects that require syncing

The Scheduler runs continuously and finds those Integration Objects that require syncing. This takes into account their defined sync frequency (how many times per day) and the time that has elapsed since the last sync. Any Integration Objects that require syncing are then sent to the Retriever.

Not all Interaction Types are created equal. Some must be synced more frequently than others and some integration partners have higher API limits. We can sync data more or less frequently on a per-Provider / per-Interaction Type basis depending on the limits of the Provider and the needs of each customer.