Claude's sharing UI does not expose a per-viewer read receipt. For tracked views, publish the content to a Sentway-hosted URL using the Sentway connector, require verified email to identify viewers by email, and ask the same AI for visitor activity. Tracking starts only on the Sentway page: it does not monitor the original claude.ai artifact URL, and historical views cannot be imported.
Sharing permissions are not view analytics
An 'anyone with the link' setting answers who may access your artifact, not who opened it. Likewise, selecting specific people controls access; it is not a list of confirmed readers. Claude can publish and share artifacts, so you do not need another host just to send someone a working link.
Native sharing options evolve, and capabilities and terminology can differ between legacy artifacts, newer artifacts and account or workspace settings. Check the current sharing panel rather than assume an older tutorial applies. Anthropic explains the available sharing options here: https://support.claude.com/en/articles/9547008-share-artifacts
Option 1: keep the simple Claude share link
Use Claude's share link for trying an artifact or reviewing an idea when tracking would not change your next step. It avoids extra setup. If you need an answer, ask the recipient to reply with feedback.
Option 2: use manual or third-party link analytics
A tracked redirect or link shortener records clicks before forwarding visitors to Claude. It may report totals, timestamps or approximate device information. Those are observations about the tracking link, not analytics inside the artifact: a click does not establish that the destination loaded or was read.
A separate link for each recipient can suggest which invitation was used, but forwarded links and automated security scanners make that an unreliable identity check. Manual replies give you explicit confirmation instead. Check a third-party service's privacy terms and tell recipients what you collect; neither approach imports Claude's historical views.
Option 3: publish a Sentway page with visitor activity
Sentway hosts a version of the content at a new URL and records activity on that page. Aggregate analytics answer questions such as whether the site received visits. Detailed visitor timelines let your connected AI inspect recorded page activity for individual visitor records, subject to the plan requirements below.
An anonymous visitor record is not a named person. Verified email access associates access with an address whose inbox was verified. It is stronger than accepting whatever address someone types, but proves control of an inbox, not legal identity. Use an allowlist if only particular recipients should get access.
1. Create a free Sentway account. Decide later whether you need detailed visitor activity.
2. Add Sentway from the Claude Connector Directory. Sign in with your Sentway account and approve the connection. Use the setup documentation below if you need the manual route.
3. In your proposal or report conversation, ask Claude to publish a version as a Sentway page. This creates a separate hosted version, not analytics on the existing Claude link.
4. Ask Claude to configure email access with email verification enabled. If the report is confidential, also specify the allowed recipient addresses. Explain the activity collection to recipients before sharing.
5. Send the new Sentway URL, replacing the old link in your message. Recipients verify their email before entering. Anyone who continues using the original Claude URL is outside this tracking flow.
6. After opens occur, ask Claude to list visitors and inspect their activity. Detailed per-visitor readback requires the plan shown below. Ask it to distinguish verified-email visits, anonymous records and recipients with no recorded activity, rather than invent a list of readers.
Page visits, scroll-depth milestones and visible-tab time are useful signals, not a certified read receipt. A page can remain visible while someone does something else. A scroll can pass a section without the visitor understanding it, and blockers or connection failures can leave gaps in the record.
Section-by-section time is not an automatic report. Ask Claude to add appropriate tracking to the page when building it if section-level evidence matters, and have it report only signals actually recorded. Without that setup, ask for page activity and scroll depth, not precise time spent reading each paragraph.
Example: following up on a client proposal
Publish your proposal behind verified email and send the new link to the client. Later, ask Claude whether that email has recorded a visit and what page activity exists. Use the answer to time a helpful follow-up, not to say 'you read the pricing section' without evidence. If acceptance matters, include an explicit response form.
Example: a report for named colleagues
Allowlist your colleagues' email addresses and share the Sentway report. Ask Claude which verified addresses have visited and which have no recorded visits. That helps organise reminders without guessing from anonymous traffic. For an actual review sign-off, ask colleagues to submit a confirmation or comment; an open alone is not approval.
Benefits and limits before you share
The benefit is a hosted page, an explicit access step and activity you can ask about in the same Claude conversation. The trade-offs are a new URL, email verification friction and a paid plan for detailed timelines. If you only need casual sharing, keep the Claude link.
This is not invisible tracking. Be transparent about what you collect and obtain consent where required. Email verification does not guarantee a particular person read the page, and a shared inbox can represent several people. No view, scroll or time signal proves understanding; request explicit acknowledgement when the distinction matters.
A prompt you can paste
Pro: Visitor timelines
Publish a version of this [proposal/report] through Sentway, require verified email access for the recipients, and give me the live URL. After I share it, help me check visitor activity and tell me which sections they spent time on.
Produces: A Sentway-hosted version with verified-email access and a new URL to share, followed by a readback of recorded visitor activity.
Per-visitor activity requires Pro. Section-level time is not automatic: ask Claude to add suitable tracking before publication and report only evidence collected. Without it, use page activity and scroll depth instead.
Needs Pro. On the free plan this prompt returns a permission error for Visitor timelines.
Can I track views of my existing Claude artifact URL?
Not through Sentway. Publish a version to a Sentway-hosted URL and share that new link. Only visits to the Sentway page are tracked; views of the original Claude link and historical views cannot be imported.
Can I see the names of people who viewed it?
Not from anonymous activity alone. Verified email access identifies the verified address associated with a visit, not necessarily a person's name or legal identity. A name needs to be explicitly supplied, for example in a form, and a visit still does not prove reading.
Can I do this on the free plan?
You can create a free account, publish a page and inspect aggregate site analytics. Detailed visitor lists and per-visitor activity require Pro. An aggregate view count is not a list of identified readers.
Do visitors need Claude or Sentway accounts?
No. Recipients open the Sentway URL in their browser. With verified-email access they must verify an allowed email address, but they do not need to create Claude or Sentway accounts to view the page.