View all articles

Which Claude Code connector should I use?

DX offers three Claude Code connectors. The right connector depends on how your users call the Claude API.

Decision guide

How users access Claude Connector to use
Directly via claude.ai — Claude for Enterprise plan Claude Code (Enterprise)
Directly via Anthropic Console — pay-as-you-go plan Claude Code (Anthropic Console)
Via a 3rd-party provider: AWS Bedrock, Google Vertex AI, or similar Claude Code (OTel)
Mixed — some users direct (Enterprise or Console), some via Bedrock/Vertex Both the matching API-based connector and Claude Code (OTel)

The key question is whether users are going through a 3rd-party API provider. When they are, Anthropic’s own Analytics API has no visibility into those requests — OTel push telemetry from the Claude Code SDK is the only way to capture that data.

The Claude Code (Anthropic Console) connector is for organizations on the pay-as-you-go plan through the Anthropic Console. For most new customers, the Claude Code (Enterprise) connector is the correct API-based choice.

Running both an API-based connector and OTel at the same time

If your organization has a mixed user population — some users accessing Claude directly and others routing through AWS Bedrock, Google Vertex AI, or a similar provider — set up both connectors:

Data precedence: OTel wins

When a user has activity recorded by both connectors, OTel data takes precedence in DX reports. Enterprise data is retained in storage but OTel data is what is shown for that user.

This precedence rule means you do not need to manually reconcile data when a user’s access method changes (e.g., migrates from Enterprise to Bedrock). Once OTel data appears for that user, reports automatically switch to showing the OTel data.

For details on how DX identifies and merges user records across these connectors, see How does DX link Claude Code users?.

If you have questions about your connector setup or about historical data, contact your DX representative or support@getdx.com.