Koddi supports offsite conversion tracking for platforms such as The Trade Desk (TTD), Pinterest, Meta and more by allowing clients to append a privacy-safe identifier to their existing Koddi conversion events. Koddi then onboards and forwards those enriched conversion events to the client’s platform-specific advertising account(s) used for offsite activations.

👍
If you have an existing onsite integration with Koddi, we can handle the heavy lifting!
All you need to do is add the addition field(s) below and Koddi will handle sending conversion events to offsite partners. This enables a single integration path (client → Koddi) instead of requiring you to build and maintain multiple direct integrations to individual platform APIs.

High-level Data Flow

Client sends conversion event to Koddi via the existing conversion event API.

Client includes normalized + hashed identifiers in the attributes object (e.g., hashed_email, hashed_phone).

Koddi validates the payload (required fields + hashing format). Koddi routes the event to the client’s configured offsite ad account(s) on supported platforms.

Offsite platform uses the hashed identifier to match users and attribute conversions for tracking/measurement.

Client Integration Requirements

Clients append identifiers to the attributes portion of the conversion event payload. All user identifiers must be:

Normalized
Hashed using SHA-256
Base64-encoded (standard RFC 4648 Base64, padding allowed)

Email normalization

Trim leading/trailing whitespace
Convert to lowercase

Phone normalization

Convert to E.164 format where possible (recommended)
Remove spaces and punctuation
Ensure country code is included (recommended)

Payload Contract

At minimum, clients must continue to send their standard conversion event fields (examples below). Exact required fields depend on the client’s existing Koddi conversion integration.

New/updated fields:

attributes.hashed_email (string, Base64(SHA-256(normalized_email)))
attributes.hashed_phone (string, Base64(SHA-256(normalized_phone))) (optional, if supported/available)

Example Payload:

{
"client_name": "Example Client",
  "culture": "en-US",
  "currency": "USD",
  "user_guid": "35438579345",
  "transaction_id": "0c0d2002-7f51-11ef-a003-bf4609a550e7",
  "unixtime": 1727717516,
  "bidders": [
    {
      "bidder": "1401144",
      "count": 1,
      "base_price": 13.08,
      "total_price": 17.42
    }
  ],
  "attributes": {
    "hashed_email": "ku4mBX7Z3qJTXWyLFB1INzkyR2WZGW4ANSJUiW21iI7="
  }
}

Privacy & Security Considerations

Clients must not send raw PII (plaintext email/phone) in the conversion payload.
Hashing must be performed client-side before transmission to Koddi.
Hashing is not encryption; it is used for privacy-safe matching consistent with offsite platform conversion APIs.