Akita integrates with over 80 leading software-as-a-service applications—leaders in CRM, support, finance and more. By integrating applications your business already uses, you can create more powerful segments, health scores and automations in Akita and enrich your 360-degree customer view.
Getting Started
We recommend you first choose a Primary data source. This data source contains the the most up-to-date list of your customers and users. Typically this would be your application's own database. You can sync data from your application's database to Akita several ways:
Akita REST API. You can use the Akita REST Api to create Accounts and Contacts in Akita when they are created in your application. You can send updates as they happen or create a process that runs nightly to keep your data in Akita fresh.
Akita Javascript SDK. The Akita Javascript SDK will automatically create new Accounts and Contacts in Akita as your users browse your application. This works great for many applications but has a few drawbacks: it only sends update when visitors are active in your application—potentially omitting inactive accounts from Akita. Additionally, data you send via the Javascript SDK can be viewed by (clever) users so you may want to omit sensitive data.
The very best solution is to use both! Utilize the Akita REST API to add users to Akita when they sign up in your system, send updates via the REST API in a nightly process and use the Javascript SDK to track users behavior in your application.
Adding 3rd-Party Data Sources
When you add 3rd-party data sources (ex. Hubspot CRM, Stripe, etc), the data will be used to either:
Create new records in Akita; or
Enrich existing records in Akita.
You determine the behavior of the integration by specifying a set of rules to follow when new records are encountered from your 3rd-party data source.
Associating Account and Contact Records between Akita and 3rd-Party Partners
When you choose to sync "Account" and "Contact" data from your integrations, you will be required to configure the mapping between the incoming data and existing data in Akita.
You will be provided with several options for processing new records encountered during a sync:
Option 1. Create a New Record
With this option, Akita will create a new Account or Contact for each record synced from the partner application. You should choose this option if you have "single source of truth" (SSOT) containing your Customer data.
Option 2. Append to an Existing Record
If you would like to use your 3rd-party integration to enrich existing data in Akita, select this option. For instance, you may use the Akita REST API to populate Akita with Accounts and Contacts (using the 'create a new record' option) and then enrich that data with data from your CRM.
You will be prompted for instructions on how to associate the incoming data CRM data to existing records in Akita.
Option 3: Create a new record if a match is not found
Option 3 is a hybrid of the first two. You might select this if your application allows direct sign ups through your application AND a sales-assisted signup flow. In this instance, you may use the REST API to populate Akita with new signups (using the 'create a new record' option) but also create new records when your sales team creates a record in your CRM. Akita will attempt to merge the new record with an existing record but create a new record if no match is found.
Option 4: Let Akita Decide (Contacts Only)
When mapping Accounts and Contacts in Akita, you may select a 4th option "Let Akita Decide". In this scenario, Akita will use our intelligent matching logic to associate incoming data with an existing record or create a new one automatically if a good match isn't found.