User & Chat Identification

• user_id — enables user-based controls when supplied.
• chat_id — enables chat-based controls when supplied.

• Frequency capping — prevents the same user from seeing the same ad repeatedly. Needs a persistent user_id.
• Ad pacing — controls how often ads appear within a conversation. Uses chat_id.
• Better targeting — DSPs can optimize bids based on user-level signals. Needs a persistent user_id.
• Accurate analytics — your dashboard reflects real unique users and conversations.

​

chat_id

• One chat_id per conversation, not per user
• Store in sessionStorage (browser) or generate per conversation (server-side)
• Reset when the user starts a new chat session

​

Browser Example

function getChatId() {
  const STORAGE_KEY = 'thrad_chat_id';
  let chatId = sessionStorage.getItem(STORAGE_KEY);
  
  if (!chatId) {
    chatId = 'chat_' + crypto.randomUUID();
    sessionStorage.setItem(STORAGE_KEY, chatId);
  }
  
  return chatId;
}

​

Server-Side Example

import uuid

def get_chat_id():
    return f"chat_{uuid.uuid4()}"

​

user_id

• Store in localStorage, a cookie, or your own user store
• Reuse across sessions so DSPs can build better bidding signals
• Use anonymous UUIDs — never use PII (email, name, phone, etc.)

• Generate a new UUID per session or per request
• You still get ads, but frequency capping and cross-session targeting won’t apply

​

Browser Example — Persistent

function getUserId() {
  const STORAGE_KEY = 'thrad_user_id';
  let userId = localStorage.getItem(STORAGE_KEY);
  
  if (!userId) {
    userId = 'user_' + crypto.randomUUID();
    localStorage.setItem(STORAGE_KEY, userId);
  }
  
  return userId;
}

​

Browser Example — Ephemeral

function getUserId() {
  return 'user_' + crypto.randomUUID();
}