Figma Slides Tracking in 2026: Native Share, Pitchdeck, and HummingDeck Compared

Updated June 2026.

Figma Slides is the native presentation tool inside Figma. The file lives in your Figma workspace alongside the design system, and distribution uses Figma's standard share-link model: one URL per file, access controlled by the file's permission setting.

That model has known limits once the deck leaves your Figma org. The share link is a single URL that everyone gets, with no per-recipient version, no record of who opened the deck, and no view of which slides got attention. Figma added a "viewer history" feature in February 2025, but it only logs signed-in Figma users with access to the file, which excludes most external recipients (investors, prospects, clients).

Two real ways exist to recover per-slide engagement on an external send. The Hypermatic Pitchdeck plugin keeps you inside Figma and generates its own tracked share link with anonymous per-slide analytics. HummingDeck takes the PDF export and sends it through a sharing layer with per-recipient tracking. The rest of this post compares the two against the same source deck.

What Figma Slides is, in one paragraph

Quick context if you've heard the name but haven't used it. Figma Slides is Figma's own presentation tool. It went into beta on June 26, 2024 and out of beta on March 19, 2025. It runs the deck inside Figma's normal canvas, so your components and design tokens are right there. Presenter mode, speaker notes, and live polling are bolted on top. If your designers live in Figma, Slides is the obvious place to build the deck.

What the Figma Slides share link does, and what it doesn't

Here's how Figma's share link actually works. It's one URL for the whole file, and access is governed by the file's permission setting, not by who got the link. Fine when you're collaborating on a design, which is literally what the model was built for. Send the same deck to ten prospects and you get a black box.

Specifically:

• Ten prospects, one link, no way to tell them apart.
• No revoking access for one recipient without revoking for everyone.
• No record of who opened the file, when, from where, or for how long.
• Public sharing requires loosening file permissions to "anyone with the link." Easy to forget to scope back later; the file then stays open indefinitely.

Figma's design-file sharing model and a B2B external-send workflow are doing fundamentally different jobs.

Figma's viewer history doesn't help with prospects

In February 2025, Figma did add a thing called viewer history on paid plans. It logs which Figma users opened the file and on what day.

If you're reading this and thinking "that solves my problem," it almost certainly doesn't. Viewer history only records logged-in Figma users who already have access to the file. The VP at the prospect company who opens your deck without a Figma account doesn't show up. Neither does the investor reading on a phone without logging in. Neither does anyone clicking through your "anyone with the link" share. That covers most of the people you actually wanted to track.

Figma's own community has been asking for real viewer analytics since 2024. The Add analytics to Figma Slides request thread says it plainly: "It would be amazing to see what slides have been viewed or interacted with. Or even to see if a link has been opened." Figma hasn't shipped it.

Per-slide engagement for an external recipient requires a tracking layer outside Figma. There are two of those worth looking at.

Option 1: Hypermatic Pitchdeck (in-Figma plugin)

Inside Figma, the closest thing to a real fix is Pitchdeck, a plugin from Hypermatic. You run it on the frame or deck you're working on, it generates a custom share link, and you get a dashboard showing per-slide views and time spent. Password protection is in there. So is export to PowerPoint, Google Slides, PDF, and Keynote.

The big advantage for a Figma-native team is the lack of an export step. You're in Figma, you make a link, the analytics live in Figma. Whole workflow in one window.

The viewer page lives on a Hypermatic-hosted URL. If you care about your share link sitting on your own custom domain, or you want every sent deck (PDFs, proposals, AI artifacts) gathered in one library, Pitchdeck isn't where you'll land.

The bigger limitation is that the analytics are anonymous. Pitchdeck supports password protection but not per-recipient identity. You see "someone spent 4 minutes on slide 7," not "Jane at Acme Corp spent 4 minutes on slide 7." For a draft you're showing to a small group of teammates, that distinction doesn't really matter. For thirty investor partners or a buying committee at a prospect, it's the whole game.

For a team shipping exclusively from Figma to a small, trusted audience, Pitchdeck is a clean answer.

Option 2: HummingDeck (export PDF, send tracked link)

The other route, and the one most teams sending Figma decks externally end up on, is to export the deck and ship it through a separate sharing layer. HummingDeck is ours. Quick disclosure so you can calibrate what follows. The product is a doc-sharing platform that takes PDFs, PowerPoints, and HTML artifacts, and gives you per-page engagement on whatever you upload, tied to the specific person you sent it to.

Step 1: Export the deck as PDF

In Figma Slides, File → Export → PDF. The whole deck comes out as one PDF, one slide per page.

PDF is a lossy format compared to what Figma Slides can do in live presenter mode. Animations, video embeds, polls, and hotspots all get flattened or dropped. The next section breaks that down route by route. For most sales decks, pitch decks, and client proposals, what's lost is mostly presenter-mode features, not viewer-mode features.

Step 2: Upload the PDF to HummingDeck

Drop the PDF into your HummingDeck library. The upload picks up the page breaks from the PDF, so each slide becomes a tracked page in the share link.

Step 3: Send a tracked link, not the PDF

You get a share link. Send that, not the file. The link can have:

• A per-recipient URL, so you can tell which prospect did what.
• A verified-email gate, so the viewer identifies themselves before they see anything.
• An expiry date or a revoke button, so the link goes dead when the deal closes or the round wraps.
• A custom domain, so the link reads as yours, not as a third party's.

Step 4: Watch what happens

Per recipient, you get:

• Whether they opened the link.
• Which slide they looked at, and for how long.
• Whether they came back later. Return visits are the single most predictive signal for whether the deal moves forward.
• Whether they forwarded the link to a colleague. A second device fingerprint on the same link tells you a champion is selling for you internally.
• Whether the open was human or bot. Microsoft Safe Links, Proofpoint, and similar email scanners click the link before your prospect ever sees it. Those clicks get filtered out so they don't inflate the data. The mechanics live in Why Your Deck Analytics Are Wrong.

What survives each path

Nothing interactive does. Slide transitions, object animations, embedded video playback, live polls, and hotspots all need a renderer that can run scripts and animations. PDF can't. Whether the PDF comes out of Figma's native export or Pitchdeck's exporter, the result is the same flat document.

Pitchdeck's web tracked link is the one exception, with an asterisk. The interactivity in Pitchdeck's web viewer isn't Figma Slides' animations being carried over. It's a parallel layer the designer authors inside the Pitchdeck plugin (its own timeline editor, its own embed system, its own click-link model). Static visuals come from Figma; the interactive playback is rebuilt in Pitchdeck. If your team is committed to that workflow, it works. If you assumed Pitchdeck reads your Figma animations automatically, it doesn't.

Pitchdeck vs HummingDeck side-by-side

Both products solve the "Figma Slides has no analytics for external recipients" problem. They solve it for different audiences.

Read the table left to right and the split is fairly clean. Pitchdeck wins the Figma-native workflow. Zero export step is a real convenience for a designer shipping a review to teammates. HummingDeck wins the external-recipient send: per-recipient identity, bot filtering, forwarding inference, return-visit alerts, multi-doc bundling, custom domain. The kind of signals you actually need when you don't know the person on the other end of the link and you can't ask them what they thought.

What HummingDeck does beyond the deck itself

A deck is one artifact. The workflow it sits inside (closing a deal, raising a round, getting an approval) is bigger. A few capabilities that live outside a slide plugin's scope:

Access control and proposal approvals. Verified-email gate (allowlist your specific recipients), calendar-based link expiry, manual revoke after the link's been opened, and accept / decline / request-changes buttons inside the viewer when the deck doubles as the proposal. State of the proposal lives in your dashboard alongside the engagement data. See Proposal Tracking for the proposal-specific surface.

Multi-doc bundles. Deal Rooms for sales (deck + pricing + case study + Loom in one branded URL with per-recipient gating). Data Rooms for fundraising (the deck plus financial model, cap table, diligence PDFs, optional NDA enforcement, partner-specific tracking). A slide plugin can't cover this category.

Mobile sender admin. HummingDeck is a web app, so checking who engaged works from any device. Pitchdeck's analytics live inside the Figma desktop plugin.

Why the HummingDeck signal is more sales-honest

"Did somebody open this" is the same level of signal as an email open rate, and it's been broken for the same reasons for a while now. A click happened. That doesn't tell you whether a human did it, whether they read past slide one, whether they came back the next day with their cofounder, or whether they forwarded the link to the rest of the buying committee.

What you actually want is much more specific. "Paula spent forty seconds on the problem statement on Wednesday morning, came back Thursday with someone from a different IP, and the second person spent two minutes on the pricing slide." That's a story you can act on. It's also literally what the deck was supposed to do, which is to open a conversation with a specific person. So it's a little strange we ever settled for so much less.

Figma's native viewer history won't tell you that story at all. Pitchdeck will tell you a redacted version of it (somebody spent forty seconds on slide three, somebody came back, somebody spent two minutes on slide eight). HummingDeck attaches every event to a named recipient, which is what makes the story usable.

The other piece worth flagging is bot filtering, mentioned briefly back in Step 4. Without it, a chunk of what your dashboard calls "engagement" is corporate email scanners and link prefetchers loading the URL before a human sees it. The full why is in Cold Email Open Rates Are Dead and the mechanics in Why Your Deck Analytics Are Wrong.

Which to pick when

Designer-led team, Figma-only stack, audience mostly internal? Pitchdeck. The zero-export workflow is a real benefit and the anonymous tracking is enough when you already know who the people are.

Founder raising a round? HummingDeck. The thing you care about isn't whether the deck got opened, it's which specific partner at which specific fund read past the team slide, who came back to the deck before the partner meeting, and which associate they forwarded it to. Those signals only exist when the link knows who the person is. And the fundraising send is almost never just the deck. The financial model, the cap table, the diligence PDFs all belong in the same conversation. HummingDeck wraps them in a Data Room.

AE or sales lead sending the deck as part of a proposal? Same answer. You want per-recipient tracking because deals move on what specific people do, not on aggregate views, and you want accept / decline / request-changes built into the viewer when the deck doubles as the proposal. Deal Rooms cover the deck-plus-pricing-plus-case-study send.

Stack with multiple tools (Figma for some decks, Claude Design for others, Keynote, PowerPoint, the occasional v0 prototype)? You need one tracking layer over all of them, or you'll be reading four different dashboards. That's the use case HummingDeck was built around.

Nothing stops you from running both. Plenty of teams use Pitchdeck for internal Figma reviews and HummingDeck for anything that crosses the company boundary.

Beyond Figma: the same flow for other deck tools

The export-upload-tracked-link path works for any deck format that exports out of its native tool:

• Keynote → export to PDF → tracked link.
• Google Slides → publish to PDF → tracked link.
• Canva → export → tracked link.
• PowerPoint → upload .pptx directly, no PDF step needed.
• Claude Design and other AI deck builders → export as HTML or PDF → tracked link. See How to Share a Claude Design Artifact for the HTML path.

Every one of these tools has the same gap as Figma Slides on the native share link: anyone-with-link, no per-recipient tracking, no engagement data. If your stack has more than one of them, a cross-format tracking layer matters more than any single in-tool plugin.

Bottom line

Figma Slides solved a real problem: building the deck without leaving the design system. The send is still unsolved territory inside Figma itself. Viewer history is a step, but it only covers people who are already in your Figma org, which is roughly the opposite of the audience you usually need it for.

If your team is Figma-native and your audience is small and trusted, the Hypermatic Pitchdeck plugin is the cleanest answer. If you're sending externally to investors, prospects, or customers and need per-recipient identity, bot-filtered signal, accept/decline workflow on proposals, multi-doc Deal Rooms or Data Rooms for the broader send, mobile sender admin, and one tracking layer regardless of what format the deck ships in, that's what HummingDeck is for.

---

Related:

• How to Share a Claude Design Artifact (HTML Deck) and Track Per-Slide Engagement: the sibling guide for AI-generated HTML decks.
• 7 Best AI Presentation Makers for Pitch Decks and Sales (2026 Comparison): the broader landscape comparison covering Gamma, Pitch, Beautiful.ai, and others.
• Why Your Deck Analytics Are Wrong: the bot-filtering mechanics behind the "sales-honest signal" argument above.
• Cold Email Open Rates Are Dead: why "did somebody open this" stopped being a useful signal.
• HummingDeck for Sales | Deal Rooms | Pricing