Reddit Conversions API: the 2026 setup manual

Reddit is still underpriced for a specific class of advertisers: B2B tech teams selling into technical buyers, gaming publishers with community-led demand, crypto and fintech brands that need credible discussion instead of polished ad inventory, and DTC companies built around niche hobbies. The platform is not always the easiest place to scale broad prospecting, but it can surface buyers who are already reading threads, comparing tools, and asking blunt questions before they ever search for a brand.

That behavior makes measurement fragile. A Reddit click can land on a long technical article, send the user into docs, return through a direct visit, and convert after a sales form, checkout, or app install handoff. Browser-only tracking loses pieces of that path through ad blockers, Safari restrictions, consent banners, payment redirects, and cross-device research. Reddit Conversions API gives your server a direct way to send the final conversion with the first-party context you were allowed to keep.

Build the integration in narrow layers: prove authorization, add browser context, normalize identifiers, send backend truth, then harden logging and retries. Each layer should be independently visible in your logs and Reddit diagnostics.

POST https://ads-api.reddit.com/api/v2.0/conversions/events/{ad_account_id}
Authorization: Bearer conversion_access_token
Content-Type: application/json

{
  "pixel_id": "t2_abc123",
  "event_at": "2026-04-23T10:15:30.000Z",
  "event_type": {
    "tracking_type": "PageVisit"
  },
  "event_metadata": {
    "conversion_id": "pv_session_10492_1"
  },
  "user": {
    "ip_address": "203.0.113.42",
    "user_agent": "Mozilla/5.0..."
  }
}

{
  "pixel_id": "t2_abc123",
  "event_at": "2026-04-23T10:18:22.000Z",
  "event_type": {
    "tracking_type": "AddToCart"
  },
  "event_metadata": {
    "value": 89.95,
    "currency": "USD",
    "item_count": 1,
    "conversion_id": "cart_10492_add_1"
  },
  "user": {
    "email": "sha256_lowercase_email",
    "ip_address": "203.0.113.42",
    "user_agent": "Mozilla/5.0...",
    "screen_dimensions": {
      "width": 1440,
      "height": 900
    }
  }
}

import crypto from "node:crypto";

function sha256(value: string) {
  return crypto
    .createHash("sha256")
    .update(value.trim().toLowerCase())
    .digest("hex");
}

const user = {
  email: sha256("buyer@example.com"),
  external_id: sha256("cust_10492"),
  ip_address: "203.0.113.42",
  user_agent: "Mozilla/5.0..."
};

{
  "pixel_id": "t2_abc123",
  "event_at": "2026-04-23T10:24:16.000Z",
  "event_type": {
    "tracking_type": "Purchase"
  },
  "event_metadata": {
    "value": 129.95,
    "currency": "USD",
    "item_count": 2,
    "conversion_id": "ord_10492_purchase"
  },
  "user": {
    "email": "sha256_lowercase_email",
    "external_id": "sha256_customer_id",
    "ip_address": "203.0.113.42",
    "user_agent": "Mozilla/5.0...",
    "screen_dimensions": {
      "width": 1440,
      "height": 900
    }
  }
}

{
  "event": "reddit_capi_dispatch",
  "ad_account_id": "a2_abc123",
  "pixel_id": "t2_abc123",
  "tracking_type": "Purchase",
  "conversion_id": "ord_10492_purchase",
  "status": 200,
  "retry_count": 0,
  "identifiers_present": ["email", "ip_address", "user_agent", "rdt_uuid"]
}

Reddit will not need every field on every event, but production payloads should be predictable. The table below is the practical contract for web and app events. Keep the same meanings across Reddit Pixel, CAPI, analytics, and backend logs so a rejected or duplicated conversion can be traced without guesswork.

Reddit's click and browser identifiers are the bridge between an ad interaction and a later server event. The Reddit Pixel can write first-party cookie values such as rdt_uuid and _reddit_uuid2 on your domain. When present, those values help Reddit connect CAPI events to the browser session that saw or clicked an ad. They are especially useful when the conversion happens after checkout moves to another domain or when the purchase is finalized by a backend webhook.

Capture these cookies early and attach them to the session or cart. Send the original values as context in your server event or internal dispatch envelope, depending on the exact connector you use. Do not fabricate them, do not hash them, and do not treat them as a replacement for eligible first-party identifiers like hashed email. They are strongest when paired with IP address, user agent, screen dimensions, and a stable conversion_id.

function readCookie(name: string) {
  return document.cookie
    .split("; ")
    .find((part) => part.startsWith(name + "="))
    ?.split("=")[1] || null;
}

await fetch("/api/cart/reddit-context", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    rdt_uuid: readCookie("rdt_uuid"),
    reddit_uuid2: readCookie("_reddit_uuid2"),
    user_agent: navigator.userAgent,
    screen_dimensions: {
      width: window.screen.width,
      height: window.screen.height
    }
  })
});

Deduplication prevents Reddit Pixel and CAPI from turning one action into two conversions. Generate one conversion_id per meaningful action, pass it to the browser event, and reuse the same value in the server payload. A readable convention is entity_action_result: cart_10492_add, lead_77821_submit, or ord_10492_purchase. The ID should be unique per action, stable across retries, and visible in diagnostics.

const conversionId = "ord_10492_purchase";

rdt("track", "Purchase", {
  conversionId,
  value: 129.95,
  currency: "USD",
  itemCount: 2
});

await fetch("/api/tracklayer/reddit-capi", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    event_at: new Date().toISOString(),
    event_type: {
      tracking_type: "Purchase"
    },
    event_metadata: {
      value: 129.95,
      currency: "USD",
      item_count: 2,
      conversion_id: conversionId
    },
    user: {
      email: sha256(normalizeEmail(customer.email)),
      ip_address: requestClientIp,
      user_agent: navigator.userAgent
    }
  })
});

Reddit's EU consent handling is more limited than Google Consent Mode, so do not assume the platform can model around a denied signal in the same way. Your tracking layer should decide whether Reddit receives the event, which identifiers are removed, and whether browser Pixel and server CAPI are treated symmetrically. If advertising storage or ad measurement is denied, suppressing the destination is often cleaner than sending a nearly anonymous purchase that your legal and media teams interpret differently.

A durable pattern is to capture consent at the event edge, store it with the order or lead event, and evaluate Reddit routing just before dispatch. Internal analytics can still retain operational purchase truth, while Reddit receives only events and identifiers that match the user's region, CMP decision, and your policy.