Billing in Freshpaint is determined based on the number of MTUs (monthly tracked users). In other words, the number of users that Freshpaint has data on. More specifically, the number of MTUs is equal to the number of non-identified users plus the number of identified users.
If a non-identified user visits your site on their phone and on their computer that will count as two MTUs since they have a unique id on both their phone and on their computer:
If you later assign a single identity to the user on both devices, Freshpaint will now recognize the two devices as a single user. This will bring your MTU count down to 1:
1 MTU = 0 non-identified users + 1 identified user (that uses two devices).
If you're using the Freshpaint HTTP API or sending data to Freshpaint using a cloud Source, the number of API calls you make may be billed separate. We place limits on the number of API calls that are sent for billing purposes.
One API call is an event payload sent to Freshpaint's client-side API, server side API, or sent to Freshpaint via a cloud Source like Mailchimp.
How are API calls billed differently than MTUs?
API calls are mapped to MTUs for billing purposes. The conversion we use is 250 API Calls = 1 MTU.
If you're using an email Source with Freshpaint, each individual Email Sent, Email Opened, and Email Clicked event counts as 1 API Call. In one month, if your cloud email Source generates:
2.5 million Email Sent events
1.5 million Email Opened events
1 million Email Clicked events
That would be calculated as an additional 20,000 MTUs to your plan for billing purposes.