MAU Addendum
MAU Addendum to Terms of Service
1. MAU Program Participation
This MAU Program Addendum ("Addendum") supplements and forms part of the Terms of Service between Peaberry Software, Inc. d/b/a Customer.io ("Customer.io," "we," "us," or "our") and you, the customer ("Customer," "you," or "your"). By entering into the applicable Service Order, you acknowledge and agree that you are participating in Customer.io's confidential Monthly Active User pricing pilot program ("MAU Program"). You further agree to work in good faith with Customer.io to resolve any issues or discrepancies that may arise during the MAU Program, including but not limited to billing calculations, usage tracking, or technical implementation matters.
By participating in the MAU Program, you acknowledge that you have read, understood, and agree to be bound by this Addendum in addition to our Terms of Service. If there is any conflict between this Addendum and the Terms of Service, the terms of this Addendum shall prevail with respect to the MAU Program.
2. MAU Definition
For purposes of this Service Order, a Monthly Active User ("MAU") is someone who:
- Has a unique Customer.io (http://Customer.io) ID, and
- Took at least one of these actions within Customer's billing cycle:
- Triggered a tracked event, such as a page view, a mobile screen view, or a custom event like
purchaseorsigned in - Opened or clicked a message (email, push, SMS, in-app, or another channel)
- Viewed, clicked, or converted on in-app content, or completed a campaign goal
- Sent a message or reply to Customer
- Opted in
- Entered, dwelled in, or left a geofence
- Triggered a tracked event, such as a page view, a mobile screen view, or a custom event like
Each MAU counts once per billing cycle, however many actions they take. An action counts whether it arrives through an SDK, the API, or an integration. Imports are the only exception and are listed below.
The following do NOT count toward MAU:
- Creating a profile, or updating its attributes or devices
- Data brought in by CSV upload, Google Sheets, or SQL data sync
- Messages sent, delivered, bounced, or failed
- Automated opens and clicks, such as Apple Mail Privacy Protection or link scanners
- Unsubscribes, opt-outs, STOP replies, and spam complaints
- Dismissing in-app content
- Anonymous visitors, until they're identified
- Objects and relationships
- System activity, such as profile merges and deletes, segment membership changes, and replayed or backfilled events
3. Billing and Overages
MAUs are calculated based on your billing cycle, not calendar months. All overages are calculated and billed monthly regardless of Customer's subscription payment term or billing frequency. Overage charges cannot be paid in advance or bundled with annual subscription payments and will be automatically charged to the payment card on Customer's account.
For more details regarding how MAU billing works please see the MAU Billing Documentation