What is IGSendMail

What IGSendMail does#

IGSendMail is an email marketing platform. You store your contacts in it, send campaigns to those contacts, and set up sequences that send on their own. This page explains the model the rest of the documentation assumes, so the later pages make sense the first time you read them.

The core model#

Three objects do most of the work.

Lists hold your contacts. A contact is an email address plus whatever else you know about the person: first name, company, plan, signup date. Those extra columns are called Fields, and you define them yourself. Inside a list you can save a Segment, which is a saved filter such as "signed up in the last 30 days" or "opened at least one campaign". A segment is not a copy of the contacts, it is a view of them, so it updates as the list changes.

Campaigns are the emails you send once. You pick a list or a segment, build the content, then send it now or schedule it. A campaign is a single send to a group of people at a point in time.

Automations are the emails that send without you. You define a trigger, such as someone joining a list, and the messages that follow it, with waits and conditions between them. A welcome sequence and a lapsed-customer nudge are both automations. The difference from a campaign is timing: an automation runs per contact, whenever that contact hits the trigger.

Almost everything else in the product supports one of those three. Templates give campaigns a starting point. Forms feed lists. Sending domains and the blacklist affect whether the mail arrives.

How you are billed#

You pay for emails sent, not for contacts stored.

Each plan comes with a monthly email allowance. If you have 20,000 contacts and you email all of them twice in a month, that is 40,000 emails against your allowance. If you email a 500-person segment instead, that is 500. Storing the other 19,500 contacts costs nothing.

On every paid plan, contacts are unlimited. There is no penalty for keeping a large archive of people you rarely mail, and no reason to delete old subscribers to stay under a cap. The Free plan is the exception: it holds up to 2,500 contacts.

Two practical consequences:

• Sending to a tight segment is cheaper than sending to everyone, and it usually performs better as well.
• Growing your list does not raise your bill on its own. Mailing that larger list more often does.

Allowances reset at the start of each billing cycle and unused allowance does not roll forward. If you need more than your plan covers in a particular month, you can buy an add-on credit pack, and pack credits do carry over. The numbers are in Plans and limits.

What every plan includes#

Feature access is not the thing that changes between plans. The allowances are. Every plan, including Free, gives you:

• Email verification. Check an address before you mail it and get back a status of deliverable, undeliverable or risky. Running an imported file through verification is the single fastest way to protect a new sending reputation.
• Automations. Welcome series, drip sequences and multi-step workflows are available from the start.
• Forms and popups. Hosted and embeddable signup forms that write straight into a list.
• The API. A REST API at https://mail.igsendmail.com/api/v1 for creating contacts, triggering sends and reading results from your own application.
• Sending domain authentication. SPF, DKIM and DMARC records for your own domain, which is what stops your mail being filtered as unaligned.

So the question when choosing a plan is how much you send, not which features you want. Higher plans raise the monthly ceilings on email, verification and AI generations.

Who it suits#

IGSendMail fits you if you own a list and want to mail it yourself: a newsletter, a store, a SaaS product sending lifecycle email, an agency running sends for several clients. It expects you to have permission to email the people you import, and it gives you the domain-level controls that serious senders need.

It is a weaker fit if you want a single transactional relay with no interface, or if your list is entirely purchased or scraped. Cold, unconsented lists produce complaints, and complaints damage the sending domain you worked to authenticate.

What you do next#

The rest of Getting started is written to be read in order. You create an account and set your sender identity, take a tour so the navigation stops being unfamiliar, import contacts into a list, then send one real campaign to a small audience.

Budget about an hour for all of it, plus DNS propagation time if you authenticate a domain on the way through. You do not have to authenticate before your first send, but you should do it before your first send that matters.