How does Coupler.io calculate the rows limit?

Our pricing is designed to let you pay for effective usage only. Coupler.io counts imported rows. 

Table of contents

  1. The basics of the rows limit calculation
  2. An example of the rows limit calculation

1. The basics of the rows limit calculation

Coupler.io calculates the rows limit as the total number of rows imported both manually and automatically. In the case of automatic data refresh, all imported rows will be calculated only if the data in your data source changes. In the case of manual data refresh, Coupler.io will calculate all imported rows every time you use it.

2. An example of the rows limit calculation

You created an importer to pull data from Pipedrive on an hourly basis using the replace import mode. To learn more about data importing modes, please use this guide.

In Pipedrive you have 1700 rows of data.

So, Coupler.io is going to do an import every hour (as scheduled) because it needs to make a request to Pipedrive to check whether your data changed since the last import.

Let's say, the chosen by you data set in Pipedrive changes twice (2 times) per day only. So, Coupler.io will calculate the rows imported during those two times, which means you will spend:

2 (imports when data changes every day) * 30 (days) * 1700 (all rows get updated) = 102 000 rows.
Book a free onboarding call! 
For any questions, feel free to email our team at  coupler@railsware.com