Skip to content
out·box
For teamsFor youHow it worksExamplesPrivacyGuidesPricing
Guides

How to see who opened your Claude artifact

Claude doesn't tell you who opened an artifact you shared: Anthropic's docs cover audiences, versions and comments, but not view counts, read receipts or open alerts. To know who opened it, give each person their own link from a tool that tracks opens. In Outbox, a per-recipient link records every open under that person's name and emails you when it happens.

What Claude shows you today

When you share an artifact, Claude manages who can get in: only you, your organization, or anyone with the link. Viewers in your organization can see your name as the publisher. On Team and Enterprise, the organization's audit log records publishing, sharing and deleting artifacts; the docs don't mention views.

Adding your own tracking script to the page doesn't work either. Claude serves artifacts under a strict Content Security Policy: external scripts load only from a short list of public CDNs, and network calls can reach only the page's own origin and Google Fonts. An analytics tag or tracking pixel never reaches its server.

Why one link per person is the answer

A single public link can tell you, at best, that someone opened it. To know who, the link itself has to identify the reader without asking them to sign up. That's a per-recipient link: you create one URL for Laura and another for Tom, and every open through Laura's URL is recorded as Laura.

It's the same idea DocSend made standard for PDFs, applied to the HTML your agent writes. The reader doesn't need an account or a password (unless you add one) and doesn't see anything different.

Set it up in Outbox

Outbox works from any agent. From Claude Code, the local MCP server is one command (see Connect Claude to Outbox for the remote connector and other clients). Use an API key that can create share links.

claude mcp add outbox --env OUTBOX_API_KEY=outbox_xxxxxxxx -- npx -y @out-box/mcp
  1. Ask Claude to publish the artifact's HTML to Outbox, for example under clients/acme/proposal. The page stays private.
  2. Ask for one share link per reader: "Create a link for Laura · Acme and one for Tom · Acme, expiring in 14 days."
  3. Send each person their own link.
  4. Get an email when each one opens it. The first open, and each new day someone opens it again, triggers a notice to whoever created the link.
  5. Ask Claude "Did Laura open the proposal?" or "Who hasn't opened it yet?" The agent reads the opens with the MCP tools (outbox_page_views and outbox_list_shares).

Where you see the opens

Library → What I share lists every link with its recipient, how many times it was opened and the last open, or "not opened yet". The page's opens view lists identified readers: per-recipient links appear as link:<name>, and signed-in Outbox users by their username.

If nobody opens a per-recipient link, Outbox reminds whoever created it after 48 hours by default (adjustable from 1 to 336 hours through the API, or off).

What counts as an open (and what doesn't)

Opens are counted once per person, per link and per day, so a reader who refreshes ten times counts once. Your own views and those of your team members don't count. Link previews generated by Slack, Teams, WhatsApp, iMessage and similar unfurlers are filtered out, so pasting the link into a chat doesn't fake an open.

Be honest with yourself about two limits. First, the name on the link is a label you choose, not a verified identity: if Laura forwards her link, the new reader's opens are recorded as Laura. Add a passphrase and send it through another channel if that matters. Second, some corporate email security systems open links automatically to scan them; an open a few seconds after you hit send is worth a second look.

Ways to track opens, compared

MethodTells you who opened itWorks on a Claude artifact
Claude's native shareNoYes
Analytics script or pixel in the HTMLNo, anonymous counts at bestNo: Claude's CSP blocks external scripts and calls
URL shortener with click statsNo, only that a click happenedYes, but anyone with the link counts the same
Outbox per-recipient linkYes, by the name you gave each link, with an email alertYes, after publishing the HTML to Outbox

Turning the emails off

Open alerts are on by default because they're the point. If you send many links, turn them off in Settings under email notifications ("When someone opens a link you shared"); the opens are still recorded and visible in What I share.

Comparisons

  • Outbox vs Claude Artifacts
  • Outbox vs DocSend
  • Outbox vs Display.dev

Frequently asked questions

Does Claude notify me when someone views my artifact?

Not according to Anthropic's docs as of October 2026: they describe audiences, versions, comments and an audit log of publish, share and delete events, but no view notifications.

Does the person I send the link to need an Outbox account?

No. They open the link in any browser. You can add a passphrase, which they type once.

Is this available on the free plan?

Yes. Per-recipient links, passphrases, expiry and open alerts are included on every Outbox plan, Free included. Paid plans add publishing volume, storage and agent keys.

Can I find out who opened a public page without per-person links?

Only partly. Outbox counts total opens and identifies signed-in Outbox users, but an anonymous reader of a general link stays anonymous. To know exactly who opened it, send per-recipient links.

Related guides

  • How to share Claude artifacts: every option, and when you need more
  • How to share a Claude artifact with a password
  • A DocSend alternative for AI-generated proposals and decks
  • Connect Claude to Outbox (remote connector or npx)

Sources

  • Claude Code docs · Share session output as artifacts
  • Claude Help Center · Publish and share artifacts

Updated 2026-10-11.

out·box

An outbox for your agents. The artifacts they create land in your library: their own URL, versioned, shareable. Private by default, presentable when you decide.

·

Product

  • How it works
  • Versions
  • Pricing
  • Start free

Guides

  • All guides
  • Outbox vs Claude Artifacts
  • Outbox vs ChatGPT Sites
  • Outbox vs Stacktree
  • Outbox vs DocSend
  • Outbox vs Qwilr
  • Outbox vs Derive
  • Outbox vs Display.dev

For agents

  • Design system
  • API status
  • CLI (npm)
  • AI agent skill

Company

  • Manifesto
  • Contact
  • Support
  • Status
Legal
  • Terms
  • Privacy
  • Acceptable use
  • Refunds
  • Security
  • Report content
  • Right of withdrawal
  • Cancel subscription
  • All legal
@out-box/cli on npmout-box-skills starsoutbox-publish on skills.sh
© 2026 Outbox · an outbox for your agents.v0.2.0 · agents-first · privacy-first