Integration

Dittofeed Tracking integration

Dittofeed Tracking is the write-key API of Dittofeed, the open-source customer engagement platform (Segment-compatible). Send user data into a Dittofeed workspace: identify users with traits, track events, record page and screen views, assign users to groups, or send several of these in one batch. What it records feeds segments and can start journeys that message users. Managing segments, journeys, templates and broadcasts needs an Admin API key and is the separate Dittofeed integration; the alias route (undocumented), the inbound email, SMS and Segment webhook routes and the end-user subscription management route (authenticated by a per-user link hash, not the write key) are not exposed. Authentication is the workspace's write key (Settings, Write Key), sent in the Authorization header as Basic <key>; the connection also holds the Dittofeed URL: https://app.dittofeed.com for Dittofeed Cloud, or your self-hosted instance's public URL.

Connect Dittofeed Tracking How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Dittofeed Tracking.Built from the 6 Dittofeed Tracking tools below, on the connection you add once.

What you can do with Dittofeed Tracking

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Event, 1 operation

track_eventTrack eventPOSTRecords an event a user performed (event name plus free-form properties) in Dittofeed. Can enter the user into segments and journeys that send messages. Answers with no body.

Group membership, 1 operation

set_group_membershipSet group membershipPOSTAssigns a user to a group, or removes them from it with assigned=false, optionally setting the group's traits, in Dittofeed. Can change segments and journeys. The reference documents no response body.

Message batch, 1 operation

send_batchSend batchPOSTSends several identify, track, page, screen and group messages to Dittofeed in one call. Can enter users into segments and journeys that send messages. Answers with no body.

Page view, 1 operation

record_page_viewRecord page viewPOSTRecords that a user viewed a page of your website (page name plus free-form properties such as url) in Dittofeed. Can enter the user into segments and journeys. Answers with no body.

Screen view, 1 operation

record_screen_viewRecord screen viewPOSTRecords that a user viewed a screen of your mobile app (screen name plus free-form properties) in Dittofeed. Can enter the user into segments and journeys. Answers with no body.

User, 1 operation

identify_userIdentify userPOSTRecords a user's traits (email, name or any JSON) in Dittofeed, keyed by userId or anonymousId. Can enter the user into segments and journeys that send messages. Answers with no body.

Use Dittofeed Tracking from Claude Code, Cursor or Codex

Connect Dittofeed Tracking in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Dittofeed Tracking operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Dittofeed Tracking

Create your workspace
Sign up free. Nothing to install.
Connect Dittofeed Tracking once
Add your Dittofeed Tracking connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.