Overview
Managing an ecommerce business means making constant changes across multiple platforms: pausing underperforming ads, scaling winners, updating budgets, building audiences, creating discount codes, and more. Without Actions, each change means logging in to a different platform, finding the right campaign or setting, and making the update manually.
With Moby Actions, you can manage many of those changes from Moby chat. Moby can prepare supported actions across Facebook Ads, Google Ads, AppLovin, Shopify, Audiences, Klaviyo, and social comments.
For example, you can ask Moby to:
Pause a Meta ad that is underperforming
Increase the budget on a campaign that is beating your Return on Ad Spend (ROAS) target
Create a discount code in Shopify
Build a customer segment and sync it to a connected platform
Create a Google Ads campaign in a paused state for review
Moby Actions follow your account’s action approval behavior. When approval is required, Moby shows the action, the reason, and the details before execution.
📝 Note: Actions require a connected account for the relevant platform, and the connected account needs permission to make changes. Read-only access is not enough.
Supported action areas
Area | Examples |
Facebook Ads | Create campaigns, ads, and lookalikes; change status, budgets, and bids |
Google Ads | Create paused campaigns and ad groups; manage bidding, keywords, and audiences |
AppLovin (AXON) | Pause or activate campaigns; change budgets |
Shopify | Create discount codes; edit product details |
Audiences (CDP) | Create segments; sync them to ad or email platforms |
Klaviyo | Create draft, immediate, or scheduled email campaigns |
Social comments | Hide, delete, or reply to comments on Meta ads |
For the complete list, see Moby Actions library: supported actions by platform.
Key terms
Term | Meaning |
Action | A single change Moby can make in a connected platform, such as changing a budget, pausing an ad, or creating a discount code. |
Ask every time | A visible control in Moby chat related to action review. |
Approval card | The review card Moby shows when an action needs your decision. It includes the action, reason, details, and response options. |
Actions log | The place to review action records, including their status, rationale, details, and created time. |
Action approval behavior | How your account handles supported actions, including whether an action can run automatically or must wait for review. |
How it works
Moby Actions follow a reviewable loop:
You ask Moby for a change.
Describe the change in plain language. Include the platform, campaign, ad set, ad, product, or audience when you know it.
Moby prepares the action.
Moby identifies the relevant account or entity, checks the available data, and drafts the action it plans to take.
Moby follows your account’s action approval behavior.
Some actions may run automatically. Other actions may require review before execution.
When approval is required, Moby shows an approval card.
The approval card is headed “Moby needs your approval to continue.” It includes the action name, a Reason section, and a View details button.
You decide what happens next.
When an approval card appears, you can choose Approve, Reject, or No, and tell Moby what to do differently. If approval is required, Moby only proceeds after you approve the action.
Moby reports the result.
Moby reports whether the action succeeded or failed. If the action cannot be completed, Moby shows the error.
The action is recorded.
The Actions log shows action records with fields such as Action, Status, Mode, Rationale, Details, and Created.
Approval and review
The Moby chat interface includes an Ask every time control. When an action requires approval, Moby pauses before execution and shows an approval card headed “Moby needs your approval to continue.”
When an approval card appears, you have three choices:
Choice | What happens |
Approve | Moby proceeds with the action. |
Reject | Moby does not run the action. |
No, and tell Moby what to do differently | Moby does not run the action, and you can give feedback so it can revise the proposal. |
⚠️ Warning: Actions run in your live connected accounts once executed. A budget change, status change, discount code, or customer-facing update is real after it runs.
To undo an executed action, ask Moby in chat to restore the previous setting. Moby can use action details to help reverse supported changes, including prior and new values when available. You can also make the change manually in the connected platform.
When to use Moby Actions
Use Moby Actions when you want to move from analysis to execution without leaving Triple Whale.
Good use cases include:
Pausing ads that crossed a spend threshold without enough revenue
Scaling campaigns that are beating your performance target
Creating a discount code for a promotion
Updating supported Shopify product content
Building an audience segment and syncing it to a connected platform
Creating a campaign in a paused state so your team can review it before launch
Actions are strongest when the decision is grounded in Triple Whale data. For example:
“Pause any Meta ad that spent more than $500 in the last 7 days with ROAS below 1.0.”
Or:
“Increase the budget by 20% for campaigns with spend above $1,000 and ROAS above 2.5 over the last 7 days.”
Trade-offs and considerations
Moby Actions help you move faster, but they still require clear direction and the right level of review.
Keep these points in mind:
Actions affect live accounts after they execute.
The connected platform may reject an action because of permissions, expired tokens, platform rules, or missing requirements.
Bulk requests can produce mixed results: some actions may succeed while others fail.
If a proposed action does not include enough context or evidence, reject it and tell Moby what to change.
If you want to review new campaigns, ad sets, or ads before spend begins, tell Moby to create them in a paused state.
Related questions
How do I ask Moby to take an action in chat?
Which platforms and actions does Moby support?
Will Moby make changes without my approval?
Can I undo an action after it runs?
What permissions does Moby need in my ad accounts?
Why did my action fail to execute?
Related articles
