If you’re putting serious effort into go-to-market (GTM) content—think product tours, interactive demos, onboarding walkthroughs—you probably want to know if anyone’s actually engaging with it. Not just pageviews, but real signals: Are people clicking? Where do they drop off? What’s working, and what’s just noise?
That’s where Arcade analytics comes in. This guide walks you through how to use Arcade’s built-in analytics to track customer engagement, figure out what matters, and skip the vanity metrics.
Whether you’re in product marketing, customer success, or just the “random person who owns the demo,” this is for you. No fluff—just practical steps and the stuff you can safely ignore.
Why Arcade Analytics Actually Matters (and What It Won’t Do)
Before you dive into dashboards, let’s get something straight: Analytics aren’t magic. They won’t tell you how to make your content amazing, and they definitely won’t solve bigger product problems. But they do help you answer real questions like:
- Are people actually using your interactive content?
- Where do they get stuck, or drop out?
- Which assets drive clicks, signups, or whatever else you care about?
Arcade’s analytics are especially useful for interactive content—think hands-on demos, not static PDFs. If you’re just looking for “how many people visited my landing page,” you’re better off with Google Analytics.
What Arcade Analytics does well: - Tracks viewer engagement and completion rates for Arcade demos - Shows drop-off points and click patterns inside your content - Gives you session-level data (as in, what a person actually did—not just that they showed up) - Integrates with other tools for deeper tracking (with some caveats, more on that later)
What it won’t do: - Replace product analytics or end-to-end customer journey mapping - Tell you why someone dropped off (just that they did) - Give you perfect attribution—especially if you embed your Arcade everywhere
Okay, let’s get into the how.
Step 1: Set Up Arcade Analytics (Don’t Overthink This Part)
If you’re already using Arcade to build demos or guides, good news: basic analytics are built in. There’s nothing fancy to set up.
Here’s what you need to do: 1. Publish your Arcade. 2. Share it—either via a direct link or by embedding it on your site, help docs, or wherever you want.
Arcade automatically starts tracking: - Views - Unique viewers - Completion rates (how many people finished your demo) - Click-throughs on CTAs (if you’ve added them) - Drop-off points (where most folks leave)
Pro tip: If you want to track specific users (not just anonymous traffic), you’ll need to use Arcade’s integrations or custom embed options. More on that below.
Step 2: Embed Your Arcade Where It Matters
Analytics are only as good as the context. Don’t just throw your Arcade anywhere—think about where it’ll actually get seen.
Places that usually work: - Product landing pages (for new launches) - In-app help centers or onboarding flows - Customer support docs - Blog posts announcing new features - Sales decks or outreach emails (Arcade links work well here)
What not to do: Don’t bury your Arcade three clicks deep in your docs and expect magic. If nobody sees it, your analytics will look terrible—and it’s not the analytics’ fault.
Pro tip: Each embed location gets tracked separately in Arcade. Use this to compare performance by channel, but don’t get obsessed with minor differences (your homepage will always get more traffic than a niche help article).
Step 3: Understand the Metrics That Actually Matter
Arcade gives you a stack of numbers, but not all of them are useful. Here’s what you should focus on:
- Views vs. Unique Viewers: Views count every session, uniques give you the real number of people. Uniques matter more.
- Completion Rate: The percentage of people who finish your demo. This is gold—if it’s low, something’s up (maybe your demo is too long, or folks get bored).
- Drop-Off Points: Where people leave. This is where you should start tweaking content.
- CTA Clicks: If you add call-to-action buttons (like “Start Free Trial”), Arcade tracks who clicks. This is the closest you’ll get to tying demos to outcomes.
- Average Engagement Time: Not always available, but useful for seeing if people are just skipping through or actually paying attention.
What to ignore: - “Total Impressions” (unless you’re running ads and care about sheer volume) - “Shares” or social metrics (unless virality is your north star, which… usually isn’t the case for product walkthroughs)
Pro tip: High view counts with low completion usually mean your hook is good, but your content loses people. Shorten it or make it more interactive.
Step 4: Use Integrations for Deeper Insights (Optional, But Powerful)
If you want to connect Arcade analytics to your other tools—like your CRM, product analytics, or email platform—there are some options. Here’s the honest rundown:
- HubSpot / Marketo / Salesforce: You can use Arcade’s integrations to push demo engagement data into your CRM. This is great for sales follow-up (“Hey, I saw you tried our feature demo!”). It’s not perfect—tracking depends on cookies and may not always match up with your contacts.
- Google Analytics: You can add Google Analytics tracking to your Arcade embeds. This gives you traffic source info, but not the same session detail as Arcade’s built-in dashboard.
- Custom User Tracking: If you embed an Arcade behind a login, you can sometimes pass user IDs or attributes for richer data. This usually requires dev help.
Caveats: - Don’t go overboard wiring up every integration if you’re just starting out. The basics usually give you enough insight. - Data in different systems won’t always line up perfectly. Don’t obsess; look for trends, not perfect numbers.
Step 5: Review Analytics, Make Changes, Repeat
Now comes the real work: looking at your analytics, making small tweaks, and seeing what changes. Don’t expect instant miracles—but you will see trends.
How to actually use the data: - If most people drop off halfway through, cut your demo in half or move your most important message up front. - If your CTA isn’t getting clicks, try a different prompt or placement. - If one channel (say, your help docs) drives more completions than another (like your homepage), focus your energy there.
What not to do: - Chase every tiny fluctuation. Numbers bounce around, especially with small sample sizes. - Assume every drop-off is a disaster. Some people are just browsing; that’s fine. - Try to “game” the metrics by making your Arcade super short or jam-packed with CTAs. People can tell when they’re being manipulated.
Pro tip: Schedule a quick analytics review once a month. Set a reminder, look at the big trends, make one or two changes, and move on.
What Actually Works: Real-World Lessons
Here’s what I’ve seen work (and not work) with Arcade analytics:
- Shorter is better. Attention spans are short, even for interactive demos. Aim for 60–90 seconds max.
- One clear CTA beats three options. Don’t make users guess what to do next.
- Iterate, don’t overhaul. Small changes (like reordering steps or trimming fluff) usually move the needle more than total rewrites.
- Don’t obsess over perfect attribution. You’ll never tie every demo view to a closed deal. Look for patterns.
And finally, don’t get paralyzed by analysis. If your content is helpful and people are finishing it, you’re on the right track.
Keep It Simple and Iterate
Arcade analytics aren’t magic, but they do give you a real window into how people engage with your GTM content. Focus on the signals that matter—completion rates, drop-offs, CTA clicks—and don’t lose sleep over the rest. Start simple, keep your demos short, look at the numbers once a month, and tweak as you go.
The best GTM teams aren’t the ones with the fanciest dashboards—they’re the ones who learn and ship faster. So keep moving. The insights will follow.