Overview
Moby 2 becomes more useful when it understands how your business operates, what your brand represents, and which rules should shape its recommendations.
Moby can use your connected Triple Whale data to understand what is happening in your business. You can provide additional context to help Moby understand what matters, how your team evaluates performance, and how you want the work presented.
You can review and manage much of this information directly from the Moby 2 chat screen.
This article explains how to:
Review the files and assets available to Moby
Check your connected tools and business accounts
Review business-specific reference material
Review your Brand Vault
Understand the available memory types
Confirm your Slack connection
Choose a model and thinking level
Set how Moby should handle actions
You do not need to document your entire business before using Moby. Start with the information that would materially change its answer or recommendation.
Key terms
Term | Definition |
Business context | Reference material that helps Moby understand your business, including goals, operating rules, customer information, inventory plans, campaign guidance, and other business documents. |
Connected data | Business data available through Triple Whale and its connected integrations, such as orders, advertising, attribution, customer, product, and performance data. |
File Manager | The area where you can review uploaded files, Moby-generated assets, published ads, product imagery, and tracked competitors. |
Brand Vault | Moby’s analysis and guidance about your brand identity, messaging, products, and visual direction. Review and refine the Brand Vault before relying on it for customer-facing work. |
Memory | Durable information or preferences that Moby can apply to relevant future work. Memory can be organized by user, business, Slack channel, or workspace. |
Connector | A supported connection that makes information or actions from another platform available to Moby. |
Model provider | The AI provider used for a Moby conversation, such as OpenAI, Anthropic, Google, or xAI. Available options may change. |
Action preference | The setting that determines how Moby handles supported actions, including whether it should ask for approval every time. |
Why context matters
Connected data may show Moby that your New Customer ROAS declined. Business context helps Moby understand whether the decline requires action.
For example, your team may know that:
A major promotion ended this week.
A high-margin product is temporarily out of stock.
Meta is primarily used for prospecting.
Your New Customer CPA ceiling is $60.
Your team prioritizes Net Profit over top-line revenue.
A campaign is part of a controlled test and should not be changed.
Without that information, Moby may provide a technically reasonable recommendation that does not fit your strategy.
The right context helps Moby evaluate performance through your team’s operating rules instead of relying only on general ecommerce patterns.
Before you begin
Gather the information and assets that would change how your team interprets performance or makes a decision.
You may want to prepare:
Your current business goals
Your most important metrics
Custom metric definitions
Attribution preferences
Target markets and customers
Budget, margin, or acquisition-cost requirements
Product and inventory constraints
Current promotions and launches
Approved brand assets
Reporting preferences
Action and approval requirements
When practicing unfamiliar workflows, use a demo or test environment if one is available. When configuring your actual business, do not include credentials, API keys, private customer information, or files that should not be available to other authorized users.
Step 1: Open Moby 2 chat
Open Triple Whale and select Moby 2.
The chat screen includes:
The Ask Anything... input
A plus icon for additional tools and context
The current action preference, such as Ask every time
The selected model and thinking mode
Suggested prompt categories
The plus menu is the main entry point for reviewing files, customizing Moby, and checking Slack.
Step 2: Review your files and assets
Select the plus icon in the Moby chat bar, then select File Manager.
File Manager can include the following areas:
Uploaded Files
Uploaded Files contains documents, images, folders, and other materials available for Moby workflows.
These files may support work such as:
Performance analysis
Creative development
Product reporting
Customer research
Promotion planning
Recurring business reviews
When you want Moby to use a file, explain what the file contains and how it should influence the work.
For example:
Use the attached marketing calendar to identify active promotions and product launches when you analyze revenue changes. Treat the calendar as supporting context. Validate any relationship against the performance data before presenting it as a cause.
This gives Moby both the source and the rule for interpreting it.
Moby Generations
Moby Generations contains assets created through Moby.
Review generated assets before reusing or publishing them. Check:
Product accuracy
Logo accuracy
Brand colors
Typography
Image quality
Messaging
Mobile readability
Keeping generated assets organized can make them easier to find and reuse in later conversations.
Published Ads
Published Ads can provide existing creative and available performance information for advertising work.
This can help Moby review:
Current advertising creative
Creative performance
Potential fatigue
Reusable themes or formats
Opportunities for new variations
Available metrics and advertising sources depend on your connected accounts and data access.
Product Imagery
Product Imagery contains images associated with products from your connected commerce business.
For example, if your Shopify store is connected to Triple Whale, Moby can make the imagery associated with those products available for supported creative, advertising, and landing-page workflows.
This helps Moby work with the products your business actually sells instead of inventing or reconstructing their appearance.
Review the available product imagery before using it and confirm that:
The correct commerce store is connected.
The intended product is selected.
The images are current.
Product variants are represented accurately.
The imagery is approved for the intended use.
Product Imagery is separate from Uploaded Files. Use Uploaded Files for additional documents or assets you provide directly. Use Product Imagery to review product images brought in from your connected store.
Availability depends on your connected commerce platform and the product information available through that connection.
Competitors
The Competitors area in File Manager lets you search for and track competitor brands, then review their available advertising creative.
To add a competitor:
Select the plus icon in the Moby chat bar.
Open File Manager.
Select Competitors.
Open Brand Tracker.
Select Track Brand.
Search using the brand name or base website domain, such as brand.com.
Select the correct result and add it to Brand Tracker.
Competitor data is powered by Foreplay and uses publicly available advertising-library information. Brand Tracker can only add brands found in Foreplay’s index.
If a search returns no result, try the brand’s full name or an alternate domain. If the brand still does not appear, it may not currently be indexed by Foreplay and cannot yet be added to Brand Tracker.
Finding no matching brand is different from tracking a brand that has no available ads. A tracked brand may still have limited or no creative coverage based on the public advertising data Foreplay can collect.
Competitor Analysis does not provide private performance metrics such as competitor spend, revenue, CPA, or ROAS.
Step 3: Open Customize Moby
Select the plus icon again, then select Customize Moby.
This opens the Make Moby Work Your Way area.
The available sections shown in the current interface include:
Connectors
Business context
Brand Vault
Memory
Skills
These areas help you review the information and capabilities Moby may use.
Step 4: Review your Connectors
Open Connectors.
The current interface organizes connectors into areas such as:
Business
User
Integrations
Available connectors may include business platforms, advertising accounts, Google Workspace tools, and other supported services.
Examples shown in the current interface include:
Shopify
Meta
Google Ads
Snapchat
AppLovin
Google Drive
Google Docs
Google Sheets
Google Slides
Gmail
Google Calendar
Typeform
The connections available to your business may differ.
Before relying on a connector, confirm:
The intended business is connected.
The correct account is selected.
The required information is available.
The connection has the necessary permissions.
The data is current enough for the decision.
The workflow requires analysis only or write access.
A connected platform does not always mean Moby can make changes to it. Read-only access may support analysis but not actions.
If a required source is unavailable, ask Moby to identify the limitation rather than replacing it with an unsupported assumption.
Step 5: Review Business context
Select Business context.
Business context can contain reference files that explain how your organization operates.
Examples may include:
Inventory forecasts
Customer persona cards
Common customer objections
Product information
Brand or market research
Campaign plans
Promotion calendars
Reporting templates
Business rules
Operating procedures
Select a file to preview its contents. Review the file to confirm that the information is accurate and current before relying on it as context for Moby.
Think about what you would explain to a new analyst before asking them to evaluate your business.
Useful context can include the following information.
Business goals
Examples:
Grow new-customer revenue while maintaining positive Net Profit.
Increase repeat purchase rate without increasing discount depth.
Improve New Customer ROAS before increasing acquisition spend.
Protect contribution margin during the summer promotion period.
Metric definitions
Document any definitions that are specific to your team.
Examples:
Use New Customer ROAS to evaluate acquisition performance.
Use a 60-day LTV window for customer-quality analysis.
Treat MER as a business guardrail, not a channel-level attribution metric.
Use the custom Net Profit metric configured in Triple Whale for profitability reporting.
Decision rules and constraints
Examples:
Do not recommend increasing spend when Net Margin is below 15%.
Do not evaluate an ad set until it has spent at least $500.
Exclude branded search campaigns from acquisition-efficiency analysis.
Treat the current product launch as a controlled test through July 31.
Do not recommend products expected to be out of stock within seven days.
Reporting preferences
Examples:
Lead weekly reports with the decision and primary cause.
Limit executive summaries to five bullets.
Separate Triple Whale, Pixel-attributed, and platform-reported metrics.
Flag conflicting sources instead of silently choosing one.
Focus on information that should influence multiple conversations or workflows. Temporary campaign details can remain in the relevant conversation or Automation instructions.
Keep your business context current. Update or replace information when your targets, strategy, promotions, or constraints change.
Step 6: Review or build your Brand Vault
Select Brand Vault.
Brand Vault gives Moby guidance about your identity, messaging, products, and visual direction so generated content can better reflect your business.
An existing Brand Vault may include sections such as:
System
Color
Typography
Logo
Campaigns
Products
The Brand Vault may describe your:
Core brand idea
Visual behavior
Messaging behavior
Product world
Color system
Typography
Logo variants
Core marketing hooks
Offer language
Campaign families
Voice patterns
Product presentation
The next step depends on whether your business already has a Brand Vault.
If you do not have a Brand Vault
Select Build Brand Vault with Moby.
This opens a new Moby conversation and sends the following prompt:
Build the Brand Vault for my shop using your Brand Vault skill.
Moby analyzes your connected store and available brand information to create the initial Brand Vault.
When it is complete, review how it represents your positioning, messaging, colors, typography, products, logos, and visual direction.
If you already have a Brand Vault
Review the current Brand Vault, then select Edit in Moby.
Use this prompt:
Moby, I want to update our Brand Vault. Using your Brand Vault skill, review what we currently have. Then ask me the questions you need, one at a time, to refine and fill in any gaps before you update it.
Moby will review the existing guidance before asking for additional information. Answer each question using the most current details about your brand.
You can also request a specific conversational update.
For example:
Update our Brand Vault to use RGB 12, 112, 242 as our primary CTA color. Preserve the rest of the Brand Vault.
After Moby completes the update, return to Brand Vault and confirm that the change appears correctly and that unrelated brand guidance was preserved.
Update your Brand Vault when:
Your positioning or audience changes
You introduce new messaging
Your tone of voice changes
You update your colors or typography
You add new logo variants
Your product presentation changes
New products require additional guidance
Moby-generated work repeatedly misses a brand requirement
Brand Vault gives Moby stronger brand context, but customer-facing work should still receive a final review before publication.
Step 7: Review Memory
The Memory page also includes an option to import memory from supported AI providers. Select Start import to begin the available import flow. Review imported information before relying on it, and remove anything that should not become durable Moby context.
Select Memory.
The current interface shows memory organized into the following areas:
User
Business
Slack
Workspace
The Memory page also includes an option to import memory from supported AI providers. Select Start import to begin the available import flow. Review imported information before relying on it, and remove anything that should not become durable Moby context.
Then continue with User memory.
User memory
User memory can support durable preferences associated with your individual Moby experience.
Examples may include:
Your preferred report structure
Your level of detail
Your writing preferences
The metrics you regularly use
Business memory
Business memory contains durable information that should help Moby work consistently across the business.
Use it for shared facts, definitions, rules, and preferences that remain relevant beyond one conversation or workflow.
When reviewing or updating Business memory, provide what you want added, changed, or removed. Useful categories include:
Business model and current priorities
Products, vendors, and fulfillment locations
Reporting definitions and KPI targets
Inventory and purchasing rules
Brand and customer context
Approval boundaries
Recurring workflows
Examples include:
“Our primary business model is direct-to-consumer, with wholesale as a secondary channel.”
“Use New Customer ROAS to evaluate acquisition efficiency.”
“Our New Customer CPA target is $60.”
“Do not recommend products expected to have fewer than 14 days of inventory.”
“Budget changes above 10% require review.”
“Our weekly growth report runs every Monday and should compare the previous completed week with the week before it.”
When information changes, state exactly what Moby should update or remove.
For example:
Update our New Customer CPA target from $60 to $55. Preserve the rest of our acquisition rules.
Or:
Remove the memory that identifies the summer product launch as our current priority. That launch has ended.
Business memory should contain information that is useful across the business. Keep temporary campaign details, short-term promotions, and instructions for one specific task in the relevant conversation or Automation instead.
Slack memory
Slack memory can provide context associated with a specific connected Slack channel.
This can help Moby understand relevant channel discussions and working context when supported.
Do not assume that Moby can access every Slack channel. Access depends on the connected workspace, channel availability, and permissions.
Workspace memory
Workspace memory can hold durable context for work associated with a specific Moby workspace.
This may include:
The workspace’s purpose
Goals and success metrics
Reporting definitions
Analysis rules
Recurring output requirements
Decisions that should guide future work in that workspace
Workspace memory is separate from Business memory. Use Business memory for information that should apply across the business, and Workspace memory for information that should apply only to a focused area of work.
Workspace memory access and management may depend on the workspace and conversation you are using.
Add memory through chat
You can ask Moby to save durable information directly from a conversation.
For example:
Save as a memory that our fiscal year ends July 31 every year.
Ask explicitly when you want information saved. Keep temporary promotions, one-time instructions, unconfirmed assumptions, credentials, and private customer information out of durable memory.
Step 8: Review and use Skills
Select Skills.
Skills give Moby repeatable instructions for specific types of work. They can define how Moby should approach a task, which requirements it should follow, and how the result should be structured.
The current interface separates skills into two groups:
Triple Whale Skills
Triple Whale Skills are default skills available for supported Moby workflows.
Examples shown in the current interface include skills for:
Data analysis
Google media buying
Image prompt engineering
Agent-to-Automation migration
Moby can call the relevant Triple Whale Skill when the requested work matches its purpose.
Business skills
Business skills are custom skills created for repeatable workflows associated with your business.
Examples may include:
A 30-day performance report
A monthly creative report
A Meta advertising audit
A recurring internal analysis
Business skills are useful when you want Moby to follow the same process, rules, and output structure each time.
Create a Business skill in chat
You can ask Moby to turn a defined workflow into a Business skill.
Your request should explain:
The job the skill should perform
The required inputs
The sources it should use
The analysis or decision rules
The required output structure
What it should never do
The name of the skill
For example:
Create a Business skill for our monthly creative report. Review the previous completed month, analyze Meta creative performance, identify the top performers and fatigue risks, and organize the result into an executive summary, performance table, creative findings, and prioritized next actions. Do not make account changes. Call this skill monthly-creative-report.
Review the finished skill and confirm that its instructions match the workflow you intended.
Run a Business skill
To use a Business skill from Moby chat, enter / in the chat bar.
Select the skill under Business Skills, provide any required information, and run it.
Using a slash command lets you start a repeatable workflow without rewriting the full instructions each time.
Update a Business skill when:
The required metrics change
The source or attribution settings change
The report structure changes
New decision rules are introduced
A previous instruction is no longer accurate
The workflow should include or exclude different accounts, campaigns, or products
Step 9: Check your Slack connection
Close Customize Moby and return to the main chat screen.
Select the plus icon, then select Slack.
If Slack is already connected, the interface will show the existing connection and available routing information.
Moby in Slack can help your team:
Ask performance questions from Slack
Bring Triple Whale data into team discussions
Continue a conversation in a thread
Share Moby’s answers where decisions are being made
Before relying on Moby in Slack, confirm:
The correct Slack workspace is connected.
The intended Triple Whale business is associated with the workspace or channel.
Moby is available in the intended channel.
The question is asked in the correct channel or thread.
The response uses the intended business.
This is especially important if your team or agency manages multiple businesses.
Use Slack threads when a follow-up depends on an earlier response. Return to the Triple Whale app when you need to explore dashboards, review detailed visual reports, manage context, or inspect a workflow that is not available from Slack.
For full setup instructions, see:
Step 10: Choose the model and thinking settings
Return to the main Moby chat screen.
Select the model and thinking control shown inside the chat bar. The visible label reflects the current selection, such as OpenAI - Thinking.
The current interface includes settings for:
Reasoning
Creative
Provider
Thinking Effort
Model
Available providers shown in the current interface include:
OpenAI
Anthropic
Google
xAI
Available providers, models, and thinking levels may change.
Choose the configuration that fits the work.
A quick operational question may not require the same thinking level as:
A detailed root-cause analysis
A multi-source report
A large research project
A creative-generation workflow
A complex business recommendation
If the task is exploratory, begin with the smallest useful request before expanding into a long-running or generation-heavy workflow.
Step 11: Set how Moby should handle actions
The chat bar also shows your current action preference.
The current interface includes:
Ask every time
Let Moby decide
Use Ask every time when you want Moby to present supported actions for review before proceeding.
This is the safer starting point when:
You are setting up a new workflow.
The request affects advertising spend.
The action could pause or activate a campaign.
Moby is publishing or updating customer-facing content in a connected platform.
The action changes a product, discount, audience, or connected account.
Your team has not yet validated the workflow.
Before approving an action, review:
The connected platform and account
The affected campaign, ad, product, audience, or asset
The current state
The proposed state
The data period
The reason for the change
The expected impact
How the action can be reversed, when reversal is supported
Actions affect live connected accounts after they execute.
Step 12: Ask Moby to summarize your setup
After reviewing the available context, ask Moby to help identify any missing information.
Use a prompt like this:
I want to set up Moby for our weekly growth review.
Ask me no more than six questions, one at a time, to understand:
The business, accounts, and markets in scope
The goals and metrics we use
The data sources and attribution settings we trust
Our budget, profitability, inventory, and promotion constraints
The decisions this review should support
The audience and format for the final report
At the end, summarize the proposed setup. Separate confirmed facts, assumptions, and missing information. Do not save anything, create an Automation, or take an action until I confirm the summary.
Review the proposed setup before you ask Moby to reuse or remember it.
Step 13: Verify the setup
Check the proposed setup for the following areas.
Accuracy
Are the business goals correct?
Are custom metric definitions preserved?
Are budget and profitability requirements current?
Are product and inventory constraints accurate?
Scope
Is Moby using the correct business?
Are the correct advertising accounts included?
Are the intended markets and channels selected?
Is multi-business or multi-region scope clearly defined?
Sources
Which source owns each important metric?
Is the required connection available?
Are attribution settings stated?
Are unavailable or conflicting sources identified?
Freshness
Has the promotion calendar changed?
Are inventory constraints still current?
Have budgets or targets changed?
Are the connected sources syncing successfully?
Permissions
Is Moby analyzing information only?
Is it preparing recommendations?
Is it proposing an action for review?
Is it allowed to execute a supported action?
Do not treat access to one business or account as proof that Moby is using the intended one. Confirm the target before relying on consequential analysis or actions.
Expected result
After reviewing and updating the context available to Moby, it should be better prepared to:
Interpret metrics through your business goals
Apply your approved definitions and constraints
Use relevant reference files
Follow your brand guidance
Apply durable preferences where relevant
Use available connected data
Follow your preferred reporting structure
Identify missing or conflicting information
Produce more relevant recommendations
Support validated workflows and Automations
Context does not guarantee that every response will be correct. Review important metrics, recommendations, generated assets, and proposed actions before using them.
Best practices
Start with context that would change a decision.
Keep stable information separate from temporary instructions.
Ask Moby explicitly when you want information remembered.
Update business context when strategy or conditions change.
Use approved brand and product assets.
Name the business and account in multi-business environments.
Confirm the source and attribution settings for performance analysis.
Explain how uploaded files should influence the work.
Use Ask every time for new or consequential action workflows.
Review customer-facing creative before publishing it.
Remove or correct outdated context.
Confirm the target before approving any action.
Related questions
How do I teach Moby about my business?
What information should I add to Business context?
What files can Moby use?
What should I ask Moby to remember?
What is the difference between Business context and Memory?
How does Moby use Brand Vault?
How do I confirm which business Moby is analyzing?
Which model should I use in Moby?
What does Ask every time mean?
Can different teammates share Moby context?
How do I update Moby when my business goals change?
