ParseBounce/API DocsDashboard

Tracking ID

Group your emails by campaign, batch, or any custom identifier to track deliverability metrics per campaign.

What is a Tracking ID?

A Tracking ID is a custom identifier you attach to your emails when sending. ParseBounce extracts this ID from webhook events and allows you to:

  • Group messages by campaign, newsletter issue, or transactional batch
  • View delivery statistics per tracking ID
  • Filter the Messages page by tracking ID
  • Compare performance across different campaigns

How to Add Tracking ID

The method varies by email provider. Maximum length is 128 characters.

SESAmazon SES

Option 1: Add a custom header

X-ParseBounce-Id: campaign-2026-01-newsletter

Option 2: Use SES Tags (in SendEmail API)

{
  "Tags": [
    { "Name": "parsebounce_id", "Value": "campaign-2026-01" }
  ]
}

SendGridSendGrid

Use custom_args in the API request:

{
  "personalizations": [{
    "to": [{ "email": "user@example.com" }],
    "custom_args": {
      "parsebounce_id": "welcome-series-v2"
    }
  }],
  "from": { "email": "noreply@yourapp.com" },
  "subject": "Welcome!",
  "content": [{ "type": "text/plain", "value": "Hello" }]
}

MailgunMailgun

Use the X-Mailgun-Variables header:

X-Mailgun-Variables: {"parsebounce_id": "promo-black-friday"}

Or via API:

curl -X POST https://api.mailgun.net/v3/YOUR_DOMAIN/messages \
  -F from='sender@yourapp.com' \
  -F to='user@example.com' \
  -F subject='Hello' \
  -F text='Hello World' \
  -F v:parsebounce_id='promo-black-friday'

SparkPostSparkPost

Use metadata in the transmission:

{
  "recipients": [{ "address": "user@example.com" }],
  "content": { "from": "sender@yourapp.com", "subject": "Hello" },
  "metadata": {
    "parsebounce_id": "order-confirmation-batch"
  }
}

PostmarkPostmark

Use Metadata in the API request:

{
  "From": "sender@yourapp.com",
  "To": "user@example.com",
  "Subject": "Hello",
  "TextBody": "Hello World",
  "Metadata": {
    "parsebounce_id": "password-reset-flow"
  }
}

MandrillMandrill (Mailchimp Transactional)

Use metadata in the message:

{
  "message": {
    "from_email": "sender@yourapp.com",
    "to": [{ "email": "user@example.com" }],
    "subject": "Hello",
    "text": "Hello World",
    "metadata": {
      "parsebounce_id": "weekly-digest-2026-w03"
    }
  }
}

Viewing Campaign Statistics

Once you start sending emails with tracking IDs, you can view per-campaign statistics:

  1. Go to Messages page in your dashboard
  2. Use the Tracking ID dropdown to filter by campaign
  3. View delivery, bounce, and complaint counts for that specific campaign

Tip: Use the search in the dropdown to quickly find a specific campaign when you have many tracking IDs.

Best Practices

Use descriptive IDs

Include date, campaign type, or version in your tracking ID for easy identification later.

newsletter-2026-01-15welcome-series-v2order-confirm-batch-1705

Keep IDs consistent

Use the same tracking ID for all emails in a campaign to aggregate statistics correctly.

Avoid PII in tracking IDs

Don't include personal information like email addresses or user IDs in tracking IDs. Use campaign-level identifiers instead.

user-john@email.com-resetpassword-reset-2026-01

API Access

Tracking IDs are included in API responses. When fetching messages, you can filter by tracking ID:

GET /projects/{projectId}/messages?trackingId=newsletter-2026-01

# Response includes trackingId for each message:
{
  "items": [
    {
      "messageId": "abc123",
      "recipient": "user@example.com",
      "status": "delivered",
      "trackingId": "newsletter-2026-01",
      ...
    }
  ]
}