Loops features: what you get on each plan

The free plan carries up to 1,000 subscribed contacts, up to 4,000 sends in any rolling 30 days and a rate of 10 emails per second, with a Loops footer on every message. Paid plans remove the footer, lift the send cap entirely and raise the rate to 1,000 emails per second. Every line below was read on 14 September 2026 against two sources that agree: the Loops pricing page and the Loops documentation.

That makes the From plan column read strangely, and the strangeness is the finding. On most platforms in this corpus, the interesting question is which tier unlocks segmentation or split testing. On Loops the answer is always the free one, and the interesting question moves to how many people are on your list.

Feature matrix

How to read this table

Two lines carry all the weight. The first is branding removal, the only capability in the table that a plan change buys. The second is raw HTML, which no plan change buys: Loops states plainly that it does not support HTML content in API requests, on the grounds that emails do not belong in a codebase. If your transactional templates already live in your repository, that is a migration, not a setting.

The third thing to weigh is not a feature at all. Because billing follows contacts rather than messages, the arithmetic that decides whether Loops is cheap is your sends divided by your contacts. A product that mails the same people often does well here. A list that is mailed twice a year pays for people it rarely writes to.

Feature by feature

Loops analytics

Analytics on Loops are built around goals rather than a dashboard of open rates, and this is a deliberate position rather than a gap. A goal is an event you define, such as a signup completing or a plan upgrading, and campaigns and workflows are then measured on whether recipients reached it. The documentation goes as far as publishing a guide arguing that open rates are a vanity metric, which tells you what the product optimises for.

Everything is on the free plan. There is no analytics tier, no retention ladder and no reporting add-on, which is unusual in this corpus: SocketLabs keeps entry-plan logs for as little as 10 days and turboSMTP for 30. Per-contact history is available as an activity timeline, so an individual record can be inspected rather than only an aggregate.

Where it falls short of a specialist is depth of slicing. There is no cohort view, no revenue attribution beyond what you send in as event properties, and no funnel builder. Compared with a product analytics tool such as PostHog, which Loops integrates with rather than replaces, this is reporting attached to a sending tool, not an analytics product. The integration list is the tell: Loops expects your numbers to be assembled somewhere else.

Continue reading

• Loops review, including what the pricing slider does not publish
• Loops overview