Guide
Marketing Email Usage and Billing
Included sends, acceptance-based counting, 1,000-send billing blocks, and monthly resets.
Your monthly allowance
Each service option includes 1,000 marketing emails per Eastern calendar month, then $0.50 per started block of 1,000 additional emails. Transactional emails, including receipts, account security messages, purchase notices, and license or activation messages, are included separately and do not consume the marketing allowance.
Monthly included quantities reset at midnight on the first day of the calendar month in America/New_York, following EST or EDT. Unused quantities do not roll over. Campaigns and marketing automations share the marketing-email allowance. Historical paid statements retain the accounting calendar recorded on them.
SoundSync
Monthly billing
What counts as a marketing send
Marketing usage counts recipient sends accepted by the email provider. Drafts, scheduling, campaign test sends, recipients skipped for consent or suppression, and provider-rejected sends do not count in the campaign billing path. A message that bounces after provider acceptance still counts as a send.
Automations record marketing usage after a successful provider send. Accounting reconciliation can recover a missed accepted-send record; repeated accounting for the same campaign recipient or queue item should not create duplicate charges.
How overage blocks work
Overages are billed in started blocks of 1,000 marketing emails at $0.50 per block. After the 1,000 included sends, sending 1 to 1,000 more costs $0.50; sending 1,001 to 2,000 more costs $1.00. Campaigns, automations, and split statement periods share the same monthly count, so continuing within an already billed block does not add another block charge.
At 1,500 total monthly marketing sends, the usage-only overage is $0.50. At 2,000 it is still $0.50; at 2,001 it is $1.00. A statement spanning two months calculates each month separately, with a fresh allowance in the new month. Other SoundSync charges and the monthly minimum are reconciled separately.
Tests and retries
Campaign and workflow test sends use the configured test-send path and do not consume the ordinary campaign/automation usage allowance. Growth-flow tests are restricted to the signed-in developer account and require a ready sending provider. Inspect recipient/queue identity and provider outcome before retrying; a timeout does not prove the provider never accepted a message.
Transactional messages
Receipts, account security, purchase, and licensing messages are not promotional campaigns and do not consume the marketing allowance.
A campaign cost estimate is not an invoice
Usage reporting applies the current policy to live accepted sends in Eastern calendar months. Campaigns and automations share one 1,000-email allowance. Additional blocks are attributed in send order, so a later campaign does not receive another free allowance and does not pay again for an already counted block.
The API labels this costBasis:current_policy_estimate. It does not rewrite a paid historical statement, include a private waiver or establish that an invoice was collected. Use billing statements and payment records to reconcile actual charges.
Read the allowance across both payout periods
The payout breakdown shows free usage consumed through the selected period end and paid units inside that period. Earlier usage in the same Eastern month still consumes the same allowance; a new payout window does not supply another 1,000 emails or 10,000 redemptions. Multi-month ranges combine the separate monthly allowances.
Estimated payout-provider fees appear with the expenses before total deductions and the final payout amount. Open the row details for country, provider, currency and applicable FX information. This presentation does not change the allowance, sales-fee minimum or payment eligibility.
Set an optional marketing budget
Marketing has no monthly spending limit by default. The account owner can enter a USD monthly budget in Marketing Settings, use $0 to stay within the included sends, or clear the budget to return to unlimited. Usage still costs money at the published rate; unlimited is not free sending.
Campaigns and Growth Flows share the budget. Accepted and reserved sends count toward committed spend; the warning starts at 80% of a chosen budget. Lowering a budget does not undo messages already accepted by the provider. A campaign preview is an estimate, and scheduled previews use the scheduled billing month.
Billing readiness and an uncertain send are different holds
Paid marketing needs a verified billing payment method. An unpaid live SoundSync bill or temporarily unavailable billing verification can pause new marketing, including otherwise included sends. Resolve the displayed billing requirement before resuming.
An accepted send settles once. A definite pre-acceptance failure releases its reservation; an uncertain outcome stays held for review and must not be resent automatically. These marketing controls do not themselves revoke existing licenses, downloads or necessary transactional messages.
SoundSync
Current usage-only email charges
| Accepted sends in the month | Marketing overage |
|---|---|
| 1,000 | $0.00 |
| 1,001 | $0.50 |
| 2,000 | $0.50 |
| 2,001 | $1.00 |
| 10,000 | $4.50 |
| 50,000 | $24.50 |
SoundSync
Delivery reports, usage and retries
Do not reprice a block that already opened
The allowance is shared across campaigns, automation and statement windows. Each additional block retains the rate at which it opened unless an applied, explicitly authorized unpaid-period adoption covers it. Other periods can still contain older and current rates. Current-policy marketing reports are estimates; finalized billing uses the applicable recorded policy and adoption. Transactional messages are separate from this allowance.
A billing pause does not restart the sequence
A queued Growth Flow email can show Sending paused while billing or a chosen spending limit needs attention. The planned Scheduled for date stays separate from Automatic retry. A past planned date is not proof that an email was sent, and updating billing does not enroll the customer again or restart the flow delay.
The recipient API returns scheduledFor, sendHoldCode, failureReason and nextRetryAt. The retry deadline is normally set 15 minutes after a deferred funding attempt; it is the earliest retry eligibility, not a promised delivery time. Once funding and spend checks succeed, the worker can retry eligible work automatically. The flow must remain active, and current audience, ownership, suppression and provider checks still apply.
Do not duplicate the flow or use Retry unconfirmed to release a normal funding hold. delivery_unknown means the provider outcome is uncertain and follows its separate review and duplicate-risk rules. An accepted send is counted once; a queued billing hold is not an accepted send.
