SendGrid Integration: Transactional Emails and Campaigns

Imagine an online store with 10,000 orders per month losing up to 15% of confirmations due to landing in spam. Each lost order means lost revenue and a dissatisfied customer. We faced this situation on a project and implemented SendGrid. Integration took 2 days, deliverability rose to 99.5%, and email infrastructure costs dropped by 30% by eliminating the need for an in-house SMTP server. SendGrid handles millions of emails per day, ensuring 99.9% uptime and built-in analytics. Get a consultation for your project — we will help with integration.

How SendGrid Solves Deliverability Issues

Deliverability directly depends on sender reputation. SendGrid automates reputation management: dedicated IP pools, automatic spam complaint handling, suppression lists. According to SendGrid documentation, proper SPF, DKIM, and DMARC setup reduces the likelihood of landing in spam by 90%. We configure Event Webhook to track delivery, bounces, and clicks in real time. This allows us to react promptly to issues. SendGrid integrates 2x faster than Amazon SES thanks to ready-made SDKs and dynamic templates.

Why Use Dynamic Templates?

Dynamic templates with Handlebars provide flexibility: you change email content without modifying code. For example, for order confirmation we pass an array of items, and the template renders the table itself. This speeds up development and simplifies maintenance. According to SendGrid documentation, dynamic templates support nested blocks and conditional logic. Static templates require code changes for every design update — dynamic templates solve this, reducing time for changes by 2–3 times.

Comparison of SendGrid with Other ESPs

SendGrid wins on integration simplicity and dynamic templates — this cuts development time by 30% compared to Amazon SES.

How the Integration Works

1. Analysis — audit of current sending scheme, DNS check (SPF, DKIM, DMARC).
2. Design — selection of template types, category setup for statistics.
3. Implementation — install the @sendgrid/mail package, write sending code, configure templates.
4. Testing — send test emails, check deliverability via Email Test.
5. Deployment — launch into production, monitor via Webhook and Dashboard.

What Is Included in the Work

• Audit of current sending scheme and recommendations for improvement.
• Domain setup for sending (SPF/DKIM/DMARC).
• Code integration: single sends, batch sends, dynamic templates.
• Event Webhook configuration for event tracking.
• API documentation and team training.
• Deliverability testing across different email clients.

API Integration Examples

Installation and Sample Code

npm install @sendgrid/mail

import sgMail from '@sendgrid/mail';

sgMail.setApiKey(process.env.SENDGRID_API_KEY!);

await sgMail.send({
  to: '[email protected]',
  from: { email: '[email protected]', name: 'Acme' },
  subject: 'Order Confirmation #12345',
  html: '<p>Your order has been received!</p>',
  categories: ['transactional', 'order-confirmation'],
  trackingSettings: {
    clickTracking: { enable: true },
    openTracking: { enable: true },
  },
});

Dynamic Templates

await sgMail.send({
  to: user.email,
  from: '[email protected]',
  templateId: 'd-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
  dynamicTemplateData: {
    subject: `Order #${order.id} confirmed`,
    customer_name: user.name,
    order_id: order.id,
    items: order.items.map(item => ({
      name: item.name,
      quantity: item.quantity,
      price: formatCurrency(item.price),
    })),
    total: formatCurrency(order.total),
    order_url: `https://app.example.com/orders/${order.id}`,
  },
});

Batch Sends via Marketing Campaigns API

import axios from 'axios';

const { data: campaign } = await axios.post(
  'https://api.sendgrid.com/v3/marketing/singlesends',
  {
    name: 'April Newsletter',
    email_config: {
      subject: 'Latest news from Acme',
      html_content: newsletterHtml,
      sender_id: 123,
      suppression_group_id: 456,
    },
    send_to: {
      list_ids: ['list-uuid-1', 'list-uuid-2'],
    },
  },
  { headers: { Authorization: `Bearer ${process.env.SENDGRID_API_KEY}` } }
);

await axios.post(
  `https://api.sendgrid.com/v3/marketing/singlesends/${campaign.id}/schedule`,
  { send_at: 'now' },
  { headers: { Authorization: `Bearer ${process.env.SENDGRID_API_KEY}` } }
);

Webhooks (Event Webhook)

app.post('/api/webhooks/sendgrid', async (req, res) => {
  const events = req.body as Array<{
    event: string;
    email: string;
    timestamp: number;
    sg_message_id: string;
  }>;

  for (const event of events) {
    switch (event.event) {
      case 'delivered':
        await updateEmailStatus(event.sg_message_id, 'delivered');
        break;
      case 'bounce':
        await handleBounce(event.email);
        break;
      case 'unsubscribe':
        await handleUnsubscribe(event.email);
        break;
      case 'spamreport':
        await handleSpamReport(event.email);
        break;
    }
  }
  res.status(200).end();
});

Suppression List Management

SendGrid allows managing suppression lists via API. Example: add an email to the global suppression list:

await axios.post(
  'https://api.sendgrid.com/v3/asm/suppressions/global',
  { recipient_emails: [email] },
  { headers: { Authorization: `Bearer ${process.env.SENDGRID_API_KEY}` } }
);

Common Mistakes When Working with SendGrid

• SPF/DKIM/DMARC not configured — emails go to spam (up to 90% of emails).
• Ignoring suppression list — repeated sends to bounced addresses degrade reputation.
• Emails larger than 10 MB — may be rejected.
• Lack of webhook processing — you miss bounces and complaints.
• Incorrect category setup — analytics become useless.

Timelines and Cost

Integration timelines: from 2 to 5 days depending on complexity. The cost is calculated individually after an audit. Get a consultation for your project — we will select the optimal configuration. Order turnkey integration — we guarantee 99.9% uptime and full support after launch.

Thanks to extensive experience integrating email services, we guarantee stable operation and complete documentation upon project completion.

Email Campaign Integration: Why Does It Often Break?

We’ve observed that a trigger email sent 10 minutes after registration converts 4–5 times better than the same email sent after 24 hours. This isn’t a marketing myth—it’s mechanics: while the user is still warm, while they remember the context. But most integrations with email services are built like this: form submits → synchronous HTTP request to API → if the API is slow, the user waits 3 seconds → the email either goes out or doesn’t, nobody knows. In one project, we saw a 30% drop in conversion simply because the email service responded with 504 and Laravel’s queue driver wasn’t configured. Lost emails often hit customers silently – no log, no alert, just a missing order confirmation.

If you’re facing lost emails or spam folder issues, order an audit of your current integration – we’ll find bottlenecks within 2 days.

Providers and Their APIs

Unisender — a Russian provider popular in the SMB segment. REST API, simple. Adding a contact: importContacts, sending a transactional email: sendEmail. Important: for transactional emails (order confirmations, password resets), Unisender Go is a separate service with a different API and separate pricing. Mixing bulk and transactional mailings in one stream is bad for domain reputation. Unisender Go handles up to 1000 requests per second.

SendPulse — provides email, SMS, web push, Viber, and Telegram bots through a unified API. Convenient for projects requiring an omnichannel approach. Automation 360 is a visual chain builder; you can trigger automation via API events. The PHP SDK (sendpulse/rest-api-php-sdk) is maintained but updated irregularly – better to use Guzzle directly.

Mailchimp — a choice for international audiences and marketing teams accustomed to the Mailchimp ecosystem. Transactional email via Mandrill (a subsidiary service). Marketing API v3 for list, tag, and campaign management. Webhooks for opens, clicks, unsubscribes, bounces.

SMS. For Russia: SMSCenter, MTS Exolve, Devino Telecom, SMS Aero. Their APIs are similar: a send method with phone, message, sender parameters (sender name must be registered separately with the operator). One nuance: the sender name must be registered through the aggregator with a contract – otherwise SMS won’t be sent on MTS/MegaFon/Beeline networks.

How to Build an Integration That Doesn’t Lose Emails?

Separate Transactional and Marketing Streams

Transactional emails (order confirmations, password resets, delivery status) go through a dedicated sender domain or subdomain tx.example.com. Marketing campaigns go through mail.example.com or news.example.com. If a marketing campaign receives many spam complaints, it should not affect the reputation of the transactional stream. According to SendGrid documentation, transactional messages should be sent through a dedicated IP pool to prevent cross-contamination.

Queue and Retry

Any call to the email API goes through a queue (Laravel Queue, Bull, Celery). If Unisender returns a 503, the job retries after 5 minutes, then 15, then 60. After 5 failed attempts, it goes to a dead letter queue with an alert. The user already received their 200 OK and knows nothing about the issue. This approach reduces bounce rate on projects to 0.5%.

Example Laravel job:

public function handle(): void
{
    try {
        $response = Http::post(config('services.unisender.email_url'), $this->params);
        if ($response->failed()) {
            $this->release(300); // retry after 5 min
        }
    } catch (\Throwable $e) {
        $this->release(300);
    }
}

Templates

We store templates in code (Blade, Twig, React Email), not in the provider’s interface. Reasons: versioning via Git, browser preview without sending, testability. For complex templates with dynamic content — react-email with export to HTML via @react-email/render.

Validation and Consent

Before adding a contact to a list — double opt-in (confirmation email). Store the confirmation timestamp in your own database. Upon unsubscription — synchronously unsubscribe both at the provider and in your database. Ignoring webhook unsubscriptions is a direct path to account suspension at the provider. All processes comply with Федеральный закон № 152-ФЗ «О персональных данных».

Deliverability Monitoring and DKIM Setup

Connect provider webhooks for events: bounce (hard and soft), spam_complaint, unsubscribe. Hard bounce — immediately mark the email as invalid in your database, stop sending. Soft bounce 3 times in a row — same. Metrics: open rate, click rate, bounce rate, unsubscribe rate — review at least once a week. Our certified engineers configure alerts in Grafana/Prometheus.

DKIM configuration steps:

1. Generate a key pair (e.g., openssl genrsa -out private.key 2048).
2. Publish the public key in DNS as a TXT record for the selector (e.g., mail._domainkey.tx.example.com).
3. Provide the selector to the provider (SendGrid, Mailgun, Unisender).
4. Verify with dig TXT mail._domainkey.tx.example.com.

SPF, DKIM, DMARC must be configured separately for each stream. We use subdomains with different DNS records.

Why Is It Important to Separate Streams?

If you send a marketing campaign from the same domain as transactional emails and receive spam complaints, you risk getting the domain blocked — and users will stop receiving even order confirmations. SPF, DKIM, DMARC (Sender Policy Framework, DomainKeys Identified Mail, Domain‑based Message Authentication, Reporting and Conformance) must be configured separately for each stream. In one project, a marketing blast with 12% spam complaints blocked the transactional domain for 48 hours — we had to re‑authenticate with Google and Yandex.

What Does the Integration Scope Include?

• Audit of current communication streams and domain reputation (SPF, DKIM, DMARC)
• Provider and schema selection: transactional vs marketing traffic
• Configuration of SPF, DKIM, DMARC DNS records
• Development of email templates (HTML + dynamic content)
• Backend integration via queues and API
• Webhook setup for deliverability and complaints
• Operations documentation and team training
• Deliverability guarantee and post‑launch support

We deliver production‑ready documentation, access to monitoring dashboards, and a handover session with your engineers. Our certified engineers provide a 30‑day post‑launch health check guarantee.

Timelines and Cost

Cost is calculated individually after audit. We provide turnkey service: from analysis to production monitoring. Contact us for a free engineer consultation — we’ll evaluate your project and give accurate timelines. Over 7 years of experience in email service integration, 50+ projects implemented. Order a free audit of your current integration and receive a report with recommendations and estimated savings.