# Three Tips for Better Prompts in Amplitude Global Agent

AI has gotten really good, but success still depends on the quality of your prompts. Explore three best practices for prompting in Amplitude Global Agent.

Source: https://amplitude.com/en-us/blog/three-prompting-tips-AI

---

[Jacob Newman](/blog/author/jacob-newman)

[Principal Product Manager, Amplitude](/blog/author/jacob-newman)

[](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Famplitude.com%2Fblog%2F%2Fblog%2Fthree-prompting-tips-AI)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Famplitude.com%2Fblog%2F%2Fblog%2Fthree-prompting-tips-AI)[](https://twitter.com/intent/tweet?url=https%3A%2F%2Famplitude.com%2Fblog%2F%2Fblog%2Fthree-prompting-tips-AI\&text=Three%20Tips%20for%20Better%20Prompts%20in%20Amplitude%20Global%20Agent)[](mailto:?subject=Checkout%20this%20Amplitude%20Article\&body=Check%20this%20out%3A%20https%3A%2F%2Famplitude.com%2Fblog%2F%2Fblog%2Fthree-prompting-tips-AI)

Everything about AI is evolving so rapidly: what it can do, how users interact with it, and the skill set required (or not required) to use it. AI prompt engineering is no exception.

Two years ago, we thought AI prompting would be ***the ***defining new skill for data analysts and engineers. Companies were opening job requisitions for AI prompters left and right, and LinkedIn postings with [“prompt engineering” surged by 400%+](https://www.vktr.com/digital-marketing/prompt-engineering-and-its-vital-role-in-ai-driven-marketing/). Two years ago, that made sense for AI’s maturity. Most models were either too literal, doing exactly what you asked–nothing more, nothing less—or too liberal, overinterpreting your prompts. As a result, we really thought AI prompting was going to be its own industry.

However, today’s LLMs are so. much. better. AI has gotten really good at understanding your intent, reading between the lines, and doing what you want it to. Nonetheless, it still can’t read your mind and doesn’t (yet) have all the [business context ](https://amplitude.com/blog/context-engineering-matters)or institutional knowledge of a seasoned human analyst. While the new AI is certainly more user friendly, your success with it still depends heavily on the quality of your prompts.

Let’s explore three best practices for prompting in [Amplitude Global Agent](https://amplitude.com/ai-agents?siteLocation=nav). For now, they’ll set you up for the most success with your agentic analyses.

## 1. Remove jargon and acronyms from your prompts

Every company coins its own internal language from acronyms, kitchy code names, and jargon. New employees regularly jot down words in the margins to ask someone about them after the meeting. *“Um, what are QBC Plus Delta, PRD V3 Final, and Project Phoenix, again?”*

It takes AI time to get up to speed on your organizational lingo, too, learning the language as data analysts define it. That’s why, even though we’ve trained [Amplitude AI Agents to think like an analyst](https://amplitude.com/blog/ai-thinks-like-analyst), we recommend initially treating Global Agents more like an intern than someone who’s worked at your company for years.

For example, I might refer to “self-serve” customers when talking to a seasoned Amplitude colleague, and they’ll know that I’m referring to customers on our Starter Plan. But if I ask AI to show me 30-day retention for self-serve customers, it wouldn’t intuitively know which segment of customers I’m referring to. Without that context, it would likely return an incorrect or incomplete answer.

AI knows your taxonomy and your definitions. Your data admins can define your internal lingo for AI to reference, but as a user, it’s always better to err on the side of caution until it builds a deeper understanding of your business. The good news is that the Global Agent can remember context from your conversations, learn from feedback, and apply it to future queries so you don’t have to re-explain context every time. Nonetheless, for the best results, treat your AI as graciously as possible to start. Assume it doesn’t know your secret language and use defined, “official” language in your prompts.

**TLDR: **Think of AI as a useful member of the team that can access all your internal data, but still needs some help understanding context about your business before it can interpret anything.

## 2. Insert yourself as the human in the loop

Most of us want AI’s help answering big, difficult questions. We can answer the easy ones ourselves, glancing at a simple dashboard, but more nuanced questions take more time, digging, filtering, slicing, and dicing. Answering complex questions involves long workflows with numerous steps and stages. Although AI can get you the answer (much faster than you could on your own!), each one of those steps introduces room for error if AI misunderstands your request at any point along the way.

Consider the steps involved in answering something like “Why did our conversion dip in September?”

- AI first has to understand what you mean by conversion and calculate it
- AI has to build or find a visualization that models this conversion and ensure it includes the right timeframe to find the dip
- AI has to do extra analysis to figure out which segments actually dropped in September—was it driven by region, channel, customer size, etc.?
- AI has to compare that segment’s September data to other months and run a series of evaluations to identify the cause of the dip

It’s easy to think that AI can orchestrate these steps in perfect order, but if it makes a mistake during any of these steps, you won’t get the right answer. For example, maybe you define conversion as a completed purchase within seven days of signup, while AI treats any purchase as a conversion regardless of timing. A small error so early in the analysis will compound into larger downstream errors, since the steps all build on each other.

The best way to mitigate this is to break down the steps required to answer your question and engage with the agent after each one. This enables you to insert yourself into the process and ensure the process never gets too far away from the intended goal.

So, instead of asking “Why did our conversion dip in September?” you could:

- Ask Global Agent, “Model conversion for me for the last 6 months” (knowing that September is in that time period)
- Review the visualization to ensure it’s true, and you can identify the dip
- Ask, “Is that dip due to regional or channel differences?”
- Ask, “What are some hypotheses about why conversion dipped among users in that region/channel?”

You could also try framing the conversation differently in your first prompt: “Tell me why our conversion dipped in September. Stop at every stage of your analysis to ask for my verification before proceeding to the next step.”

This approach enables you to work iteratively and collaboratively with AI agents to ensure that you have a perfect answer at the end. Verifying the facts at each step before performing extra synthesis avoids frustration and gives you more confidence in the answer. Over time, you’ll learn which questions AI can and can’t tackle without as much supervision.

**TLDR: **Don’t ask AI for a big answer right out of the gate and expect a miracle answer. Ask it to take several small steps in a row and build human checks into your analysis process. Remember, the bigger the leap you ask for, the more room for error there is.

## 3. Specify your audience and segmentation to get accurate answers

Good data inquiries require three elements: the right data, the right time frame, and the right user segmentation. These three components are second nature to veteran users of Amplitude dashboards and charts. AI agent users generally do a good job of including the right data and time, but it’s easy to forget the segmentation.

In the absence of further instruction, Global Agent will typically default to “all users.” However, most product managers and marketers aren’t typically looking for that broad of an audience. They’re typically looking for a subset by region, industry, product line, etc., and they might inadvertently bring existing mindsets or assumptions to the table that could result in misinterpreting AI’s answers.

Imagine you're a marketing manager for the Americas. You always look at Americas data, and all your charts and dashboards are filtered to that region. You ask AI, “What’s our average order size?” and it tells you 13. AI’s answer applies to *all* orders, but your brain is still in the Americas. Your usual assumptions have gotten in the way of your communication with the agent. So you walk away thinking that the Americas’ average order size is 13, when it’s actually 24.

The easiest way to avoid this is to always specify segmentation in your question, which is easy to do. Instead of asking “How were user signups trending last month?” just ask “How were user signups trending in EMEA last month?”

**TLDR**: Every AI prompt should specify the data set, time frame, and segment you care about. Nailing those three removes a lot of room for error or misinterpretation.

## Ask good questions, get great answers

With AI, you get what you give. Give it jargon-free, complete prompts, and you’ll get accurate answers to bet your business on. Writing prompts isn’t rocket science, especially when you’re working with Global Agent.

Be conscious of jargon, check AI’s answers along the way, and specify your segment. Do these three things and you’ll be on your way to unlocking deeper insights and moving the business outcomes that matter.

For more AI analytics best practices, check out these [blog articles.](https://amplitude.com/blog/tag/artificial-intelligence)

[Get started](https://app.amplitude.com/signup?siteLocation=blog) with Amplitude AI today.

##### Ready to use AI to transform your product?

Amplitude Agents help you understand your users more easily than ever.

[Get started now](/signup?source=blog-ai\&topic=ai\&siteLocation=blog-inline-cta)

About the author

Jacob Newman

Principal Product Manager, Amplitude

[More from ](/blog/author/jacob-newman)

<!-- -->

[Jacob](/blog/author/jacob-newman)

Jacob is a product manager at Amplitude, focused on the core analytics product. He began his career at startups in the ed-tech and recruiting space, where he learned to build products informed by data. Outside of work, you’ll find him listening to podcasts or getting lost in a sci-fi or fantasy novel.

Topics

[AI](/blog/tag/artificial-intelligence)

[Agents](/blog/tag/agents)

#### Recommended Reading

[Read ](/blog/ai-took-data-analyst-job-better)

[Customers](/blog/ai-took-data-analyst-job-better)

###### [How AI Took the Data Analyst’s Job, and Created a Better One](/blog/ai-took-data-analyst-job-better)

[May 22, 2026](/blog/ai-took-data-analyst-job-better)

[8 min read](/blog/ai-took-data-analyst-job-better)

[Read ](/blog/default-prompts-agent-retention)

[Insights](/blog/default-prompts-agent-retention)

###### [Default Prompts Are Tanking Your Agent’s Retention](/blog/default-prompts-agent-retention)

[May 21, 2026](/blog/default-prompts-agent-retention)

[6 min read](/blog/default-prompts-agent-retention)

[Read ](/blog/web-vitals-agents)

[Product](/blog/web-vitals-agents)

###### [Optimizing Core Web Vitals with Amplitude’s Global Agent](/blog/web-vitals-agents)

[May 20, 2026](/blog/web-vitals-agents)

[4 min read](/blog/web-vitals-agents)

[Read ](/blog/ask-ai-these-three-questions)

[Insights](/blog/ask-ai-these-three-questions)

###### [Don’t Ask Global Agent Anything, Ask These Three Things](/blog/ask-ai-these-three-questions)

[May 19, 2026](/blog/ask-ai-these-three-questions)

[9 min read](/blog/ask-ai-these-three-questions)