What to Send and What to Keep

I was sitting in a cramped cafe last Tuesday, staring at a client’s email that basically asked me to prove my worth through a 40-page slide deck of “engagement metrics.” It’s the same old dance: someone asks for your data, and suddenly you feel like you need to hire a designer to make your spreadsheets look expensive just to stay credible. Most people will tell you to build a complex reporting suite or hide behind vague percentages, but honestly, that’s just a way to mask a lack of real results. If you’re wondering how to handle a request for your statistics without losing your mind or your dignity, you need to stop treating your data like a polished marketing presentation and start treating it like a functional tool.

I’m not here to teach you how to fluff your numbers or create “vanity metrics” that look good in a pitch but mean nothing for the bottom line. Instead, I’m going to show you how to provide the raw, honest numbers that actually prove your work performs, even when the signal is weak and the context is messy. We’re going to skip the growth-hacking jargon and focus on a straightforward system for delivering data that builds trust rather than just filling up a folder.

Responding to Data Inquiries Without Losing Control

When someone asks for your numbers, your first instinct is often to either send everything you have to prove your worth or to get defensive and say nothing at all. Both are mistakes. I’ve seen people send over full-resolution screenshots of their backend dashboards just to impress a potential client, only to realize later they’ve accidentally leaked proprietary campaign structures or client names. You need to stop treating your analytics like a raw dump and start treating them like a curated report. The goal is sharing analytics securely by providing the insights they need without handing over the keys to your entire digital house.

The best way to maintain authority is to establish a standard procedure for managing sensitive information requests before they even land in your inbox. Instead of a frantic scramble, I always suggest having a pre-formatted “Impact Summary” ready to go. This isn’t a massive spreadsheet; it’s a clean, high-level overview of the metrics that actually matter—like conversion rates or engagement growth—stripped of any identifying details. If you provide a structured, professional response, you aren’t just answering a question; you’re demonstrating that you actually know how to protect your own professional boundaries.

The High Cost of Sloppy Data Disclosure Best Practices

When you treat data requests like a casual favor, you’re setting a dangerous precedent. I’ve seen people send over raw spreadsheets because they wanted to look helpful or “transparent,” only to realize later they’ve handed over more than just performance metrics. If you aren’t careful about managing sensitive information requests, you risk leaking more than just your reach; you might accidentally expose client details or proprietary strategy. Sloppy disclosure isn’t just a professional oopsie—it’s a liability that can end a contract faster than a broken link.

The real danger lies in the lack of a filter. If you don’t have a standard process for anonymizing statistical data, you’re essentially leaving your front door unlocked. I once worked with a brand that shared a full breakdown of their customer engagement numbers with a potential partner, forgetting that those numbers could be traced back to specific campaign windows and budget spends. They didn’t just share stats; they shared their entire playbook. You have to treat your data like your code: if it isn’t cleaned and stripped of everything unnecessary, you’re just asking for a security headache.

Five ways to share your numbers without handing over the keys to the kingdom

• Stop sending raw spreadsheets. If someone asks for your reach or engagement, send a clean, curated summary. Giving a potential partner a messy CSV file just invites them to misinterpret your data or find a tiny dip in a single week and use it against you.
• Context is your best defense. A 2% click-through rate looks terrible in a vacuum, but if the industry average is 0.5%, you’re actually winning. Never send a number without the benchmark that proves it’s actually a good one.
• Use a “view-only” approach. I’ve seen too many people email PDF attachments that get passed around like wildfire. If you can, use a live dashboard or a locked link. It allows you to see who is looking and, more importantly, ensures you aren’t the one stuck answering follow-up questions about a typo in a static document.
• Vet the “why” before the “what.” If a brand or agency asks for your stats, ask them what specific metric they are trying to solve for. If they say “engagement,” they might actually mean “conversion.” Don’t waste an hour pulling data for a metric they don’t even care about.
• Set a deadline for the data’s relevance. Data has a shelf life. When you send your stats, include a note that says, “These figures are current as of [Date].” It prevents someone from coming back in six months and trying to hold you to last year’s performance.

The bottom line on data requests

Stop treating data requests like a formal interrogation; have a standard, pre-vetted set of metrics ready so you aren’t scrambling or over-sharing every time an inquiry hits your inbox.

Context is your best defense against bad interpretations—never send a raw percentage without the baseline number that actually proves whether that growth is significant or just noise.

Protect your proprietary workflows by sharing the results, not the recipe; show them the reach and the conversion rate, but you don’t owe them the granular backend details that make your process work.

Getting your data house in order

At the end of the day, managing requests for your stats isn’t about being secretive; it’s about being prepared. If you wait until a potential partner or client asks for your engagement rates or conversion numbers to start digging through your analytics, you’ve already lost. You need to have a streamlined process—whether that’s a clean, hosted dashboard or a simple, unadorned PDF—that allows you to share the truth without handing over the keys to your entire kingdom. Remember, the goal is to provide enough evidence to prove your value while maintaining a standardized way of reporting that keeps you from looking disorganized or, worse, defensive.

I know it feels like a chore, and honestly, most of the time it is. But treating your data with the same respect you treat your creative work is what separates the hobbyists from the professionals. When you stop treating your statistics like a scary secret and start treating them like a functional tool for business, everything changes. You move from being someone who just “posts content” to someone who delivers measurable results. So, go through your folders, clean up those spreadsheets, and make sure that when the next request hits your inbox, you aren’t scrambling—you’re simply hitting send.

Frequently Asked Questions

What do I do if a potential client asks for my data but refuses to sign an NDA first?

If they won’t sign an NDA, don’t send the raw data. Period. I’ve seen too many people hand over granular campaign results only to have that information used against them in a later negotiation. Instead, offer a “sanitized” version. Give them the percentages and the growth trends, but strip out the client names and specific budget figures. If they can’t trust you with a piece of paper, they definitely shouldn’t be trusted with your intellectual property.

How much detail is actually necessary—should I send a full breakdown or just the high-level wins?

Send the high-level wins first. If you dump a massive spreadsheet on someone immediately, you’re inviting them to nitpick your methodology instead of celebrating your results. Start with the “so what”—the conversion rates and growth numbers that actually matter. If they push for more, then you can provide the breakdown. It keeps you in the driver’s seat and ensures they’re looking at your impact, not just your raw data.

Is it okay to withhold certain metrics if they don't look as good as my other stats?

Look, I get the temptation to hide the “ugly” numbers, but selective reporting is a fast track to losing trust. If a brand realizes you’re cherry-picking, they’ll wonder what else you’re hiding. Instead of burying a low engagement rate, frame it with context. If reach was down but conversion was up, lead with the conversion. Data isn’t just about the highs; it’s about proving you know how to interpret the lows.

How can I present my numbers so they look professional without looking like I'm trying too hard to hide something?

Don’t send a massive, unformatted spreadsheet; that looks like you’re trying to bury the truth in a mountain of noise. Instead, use a clean, simple summary. Lead with your most important KPIs—the ones that actually prove your value—and provide the context behind them. If a number looks low, explain why. Transparency isn’t about showing every single decimal point; it’s about showing that you actually understand what those numbers mean for the business.