Simula delivers contextually relevant in chat ads tailored for AI games and companions. It's lightweight, easy to integrate, and MRC-compliant out of the box.

⚡ Quick Start

Integrate in two steps:

1. Wrap your app with SimulaProvider
2. Insert <InChatAdSlot /> where you want ads

function App() {
  return (
    <SimulaProvider apiKey="SIMULA_xxx">
      <YourChatApp />
    </SimulaProvider>
  );
}

function ChatMessage() {
  return (
    <div>
      {/* Chat UI */}
      <InChatAdSlot
        character_desc="A stick of butter who can talk..."
        format="all"
        theme={{ theme: "light", accent: "blue" }}
      />
    </div>
  );
}

🧩 Components

SimulaProvider

Initializes the SDK and manages session state.

// Wrap your entire app
<SimulaProvider apiKey="SIMULA_xxx">
  <App />
</SimulaProvider>

// Or wrap logged-in content (recommended for authenticated apps)
function App() {
  const { user } = useAuth();

  if (!user) return <LoginPage />;

  return (
    <SimulaProvider apiKey="SIMULA_xxx" primaryUserID={user.id}>
      <AuthenticatedApp />
    </SimulaProvider>
  );
}

💡 Provider Best Practices

SimulaProvider doesn't need to wrap your entire app. But for best results:

• Wrap logged-in content – Place it around authenticated sections where we can track a user across a single session
• Provide primaryUserID – Use your user's ID to enable cross-device tracking and cookie-independent identification. This approach delivers:
  • Higher CPMs – Better user attribution leads to more valuable ad placements
  • Frequency capping – Prevents oversending ads to the same user
  • Better ad experience – Optimized targeting based on consistent user history
  • Accurate analytics – Reliable performance metrics across devices and sessions

For anonymous users, you can still use SimulaProvider without primaryUserID, but tracking will rely on cookies.

InChatAdSlot

Displays an ad based on conversation context. Ad slots can either render as a below-chat component or be mounted into an existing dropdown node, depending on the host component hierarchy.

Behavior: