This document describes how to integrate an Email Service Provider (ESP) with Koddi so email placements can be planned, booked, and reported alongside all your other ad inventory. This is a generic guide that applies to most ESPs that support custom content blocks and server-side content rendering at send time.

You will implement a reusable “Koddi Ad Slot” content block in your ESP’s email builder. At send time, the block calls Koddi to retrieve the correct creative, renders HTML into the email, and instruments tracking so Koddi can report delivery and engagement consistently across channels.

At a high level:

• A campaign is booked in Koddi and includes one or more Email placements.
• The email producer places a Koddi Ad Slot block into an email template.
• On send, the ESP requests ad content from Koddi.
• The ESP injects the returned HTML into the email.
• Opens and clicks are tracked, and delivery metrics are reconciled back into Koddi reporting.

3 Step Process

ESP Tool Set up

Koddi generally integrates with the ESP via a configurable content component inside the email builder.

In practice:

• A Koddi “ad component” is installed in the ESP
• Email creators drag and drop that component into the email template.
• At send time, the component makes an API call to Koddi.
• Koddi returns the approved creative.
• The email is assembled and sent.

This enables dynamic ad insertion without disrupting the email workflow.

Booking Campaigns

Media plans and campaigns are generally booked in Koddi (either by the advertiser or a managed service/ad ops team).

If the plan includes sponsored emails, Koddi forecasts expected delivery based on audience and send assumptions. Email becomes another measurable, forecastable surface within the broader media plan. General best practice is to ensure the audience defined in Koddi matches the audience selected in the ESP.

Koddi becomes the system of record for booked volume and reporting structure.

From there, the email team would then build the email, including the Koddi ad component.

Send Time Ad Delivery Patterns

Koddi supports two patterns. Most partners start with Pattern A.

**Pattern A: Static Creative Per Placement (recommended to start) **

• One creative is selected for the placement ahead of time.
• The ESP requests a single HTML payload per send job (or per template render) based on the audience set up in the ESP.
• “Impressions” are derived from send counts or from image render calls.
• "Clicks" are tracked through a Koddi redirect using hashed emails.
• This is the simplest operationally and avoids per-recipient decisioning.

**Pattern B: Per-Recipient Decisioning (advanced) **

• The ESP requests content per recipient at send time.
• Koddi selects the best eligible creative based on recipient attributes and campaign rules.
• “Impressions” are derived from send counts or from image render calls.
• "Clicks" are tracked through a Koddi redirect using hashed emails.
• This requires stricter latency controls and careful handling of recipient attributes.

Reporting

Koddi unifies reporting across channels, including email.

Standard metrics for email will include:

• Impressions based on send volume or image rendering calls
• Click and click-through rate
• Spend, pacing, attribution, etc. for campaigns

Prerequisites

You will need the following - all are generally supported by modern ESP platforms.

• Ability to add a custom content block or dynamic content component in your ESP builder
• Ability to execute server-side code at send time or template render time (varies by ESP)
• Outbound HTTPS access from the ESP to Koddi endpoints
• A method to export or query send and open metrics by email job, campaign, and segment