Our pricing is primarily centered around the total number of uniquely indexed records you have sitting in your Formstack Sync integration. To help you figure out where you might fit within the plans listed on our pricing page, below is an overview of this this is calculated.
What Records Are Calculated
Each Mapping Type you have in Formstack Sync will determine the type of records we will index into your Formstack Sync integration. So if you have a Contact Mapping and Company Mapping then we'll index these record types and combined they will count towards your unique record count.
* Activity Mapping Note: If you have an Activity Mapping, we will exclude these records from your count since this is a separate Add-On object that you must purchase in order to utilize the mapping in your integration.
How Unique Records Are Calculated
Once we have all of the records indexed based on your mappings, we'll go through and dedupe so that we create a unique version of each record within the Formstack Sync index. For example, if you have a contact in your marketing system with an email address of email@example.com and a lead in your CRM system with the same email, in Formstack Sync this is considered one unique record. Learn more about how we deudpe all objects here.
Does Formstack Sync Charge For Records We Won't Be Syncing Between Systems?
Ultimately yes, there will likely be records that are calculated in your record count that may never sync from one system to another. But these records still must be indexed since as a bi-directional integration we have to know everything about the records you are syncing so that we don't lead to the creation of duplicate records.
It's also important to note that the majority of transactions we are processing are to update records and not necessarily to sync new records. So while you may only be syncing a portion of your records at any one point in time, a given record might sync through Formstack Sync multiple times in a day simply due to the updates taking place the fields you have setup in your mappings. The larger the size database the more transactions the integration is going to be managing on a day to day basis whether all of your records are syncing or not.