Pingram Roundup - 2026 Week 38

Email broadcasts are live. Create, schedule, and send campaign-style email from the dashboard or POST /broadcasts. Target identified users with property filters, or pass a list of addresses. Personalize subject and HTML with Liquid mergetags, include {{ pingram.unsubscribe }}, and track delivered, opened, clicked, bounced, and unsubscribed. Full walkthrough in the announcement and broadcast docs.

Identify users with custom attributes

user.identify now accepts a properties map for attributes like first name or plan. Later identify calls merge new keys; omitted keys stay as they are. Use those attributes in broadcast audience filters and in templates as {{ user.properties.firstname }}.

await pingram.user.identify('user-123', {
  email: 'alex@example.com',
  properties: {
    firstname: 'Alex',
    plan: 'pro'
  }
});

See managing users.

MFA on any paid plan

Multi-factor authentication is included on every paid plan, not only Enterprise. Enable an authenticator app from Profile → Security. Free accounts unlock MFA by upgrading.

Team members can manage Auto upgrade

Anyone who can change the account plan can enable or disable Auto upgrade under Settings → Plan. PATCH /account no longer requires the owner role to set autoUpgrade.

Clearer MCP tool names and safety hints

Each Pingram MCP tool now shows a human-readable title in the connector listing (for example, “Send Email” instead of email_send), and advertises whether it is read-only or destructive so clients can group them correctly.

Broadcast code samples include your API key

Broadcast Code samples embed your account API key in the Node.js, Python, and cURL snippets. Raw email audience examples come first; filtered-audience samples include a short user.identify snippet.

Full ship list: changelog.