Skip to main content

Send a Targeted Email from the CDP Funnel

This guide sends one personalized email to a single contact from the Mailtarget CDP funnel view. Use it when an operator needs to reach a specific customer with a targeted message: a recovery email after a churn signal, a manual follow-up after a sales conversation, a personal note to a Promoter-stage customer.

This is an operator workflow, not an application integration. For programmatic per-contact sends, use the Transmission API.

When to use this flow​

Pick this flow when:

  • The send is to one specific contact, not a segment.
  • The decision to send is human, not algorithmic.
  • The message is personal and not template-driven.

For everything else (transactional notifications, automated campaigns, segment-based sends), use the Transmission API or campaigns built in the dashboard.

The flow​

In the dashboard:

  1. Open the CDP funnel view.
  2. Search for the contact by email or by name.
  3. Click the Action icon on the contact row.
  4. The contact detail panel opens with the contact's funnel status, history, campaign report, notes, and activity log.
  5. Click Send Email.
  6. The plain email composer opens.
  7. Compose the email: subject, body, and any signature you want.
  8. Send.

The send goes through the same authentication, sending domain, and deliverability stack as any other Mailtarget send. The recipient receives one message addressed to them only.

What the recipient sees​

The send fires from the configured sender of your account (sender name and sender email set in account settings or per-message). The message is plain (no HTML template). Use this for short, personal messages. For richly formatted email, use a campaign or template-based send instead.

What the dashboard records​

After sending, the message appears in the contact's activity log. Subsequent webhook events (delivery, open, click, bounce, complaint) are visible in the activity timeline alongside the send.

If you need the events delivered to your application, the standard webhook configuration covers this send the same way it covers any other.

What this flow does not do​

  • No template engine. The composer is plain. If you want substitution data and templates, use the Transmission API.
  • No bulk send. This flow is per-contact. To send to a group, use a campaign with a segment.
  • No automation trigger. A targeted send from the funnel view does not start an automation flow. If you need follow-up, schedule it manually or use a campaign with automation.

Programmatic alternative​

If your application needs to send a targeted email keyed by user ID, the cleaner path is the Transmission API:

curl https://transmission.mailtarget.co/v1/layang/transmissions \
  -X POST \
  -H "Authorization: Bearer $MAILTARGET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "subject":  "Following up on your account",
    "from":     { "email": "csm@your-verified-domain.com", "name": "Your CSM" },
    "to":       [ { "email": "user@example.com", "name": "Customer Name" } ],
    "bodyHtml": "<p>Hi Customer Name, ...</p>",
    "metadata": {
      "user_id":   "u_abc",
      "trigger":   "csm_followup",
      "operator":  "csm@yourcompany.com"
    }
  }'

Set metadata so the webhook events arrive with operator and intent context. This is what most teams adopt once they outgrow the dashboard UI flow.

Next​