Skip to content

Actioning Moloco Ads

Actioning turns insights into changes you can push straight to Moloco — no copy‑pasting between Aliveo and the Moloco portal. When you ask Aliveo to optimize budgets, goal targets, pacing, or statuses across campaigns, ad groups, and creative groups, it produces an action table: a clear, side‑by‑side preview of current vs proposed values. You review the rows, adjust anything you like, select what you want, and click Apply — Aliveo then sends those changes to Moloco on your behalf and reports back which ones succeeded.

This guide covers:

  • How action tables work — reviewing and applying changes safely.
  • What you can action — budgets, goal rates and targets, flight end dates, and statuses across campaigns, ad groups, and creative groups.
  • Creating actions on the fly with /actioning in Analytics Chat.
  • Building repeatable Custom Actioning Workflows.
  • Example prompts, from simple one‑liners to multi‑step optimization workflows.

Who can action. Actioning is available only for accounts Aliveo manages for you (not read-only connections), and only to users who have permission:

  • Primary users can action by default.
  • Secondary users can action only once a primary user grants them permission for that account or platform — see Actioning Permissions.
  • Read-only users can never action.

If you don't have actioning permission for an account, Apply is shown but disabled, and hovering it explains why. Accounts that Aliveo doesn't manage don't offer actioning at all.

Management access on Moloco. Moloco connects with an API key, so Aliveo can't tell from the key itself whether it may make changes. When you save the key, tick Ads Management (next to the always-on Ads Read) to confirm the key has a write‑capable role in Moloco. Without it, the account is connected read-only. To turn management on later, save the key again with Ads Management ticked.

A note on names. Moloco groups the creatives that serve under a campaign into a creative group. It's the closest thing Moloco has to an "ad", and disabling one stops its creatives from serving — so where other platforms let you pause an ad, on Moloco you pause a creative group.


1. The Action Table

Whenever a chat answer or an agent step proposes changes to your account, Aliveo renders them as an action table. This is the single place where you review and apply changes — it looks and behaves the same whether the table came from a chat, a /actioning request, or a scheduled workflow.

Every action table carries the same instruction at the top:

Select rows, adjust the recommended values if needed, and click Apply.

Each row pairs a proposed value with its current value, and you can adjust any proposed value inline before applying. Select the rows you want, and the Apply button reflects how many you've chosen.

Action table — review and apply

Anatomy of the table

Element What it does
Row checkboxes Select exactly which recommendations you want to apply. A header checkbox selects/deselects all eligible rows.
Proposed value (editable) The recommended new value. You can edit it inline before applying — change a budget, round a target, switch a status, etc.
Current value Shown beneath the proposed value (e.g. Current: 2,000) so you always see what you're changing from.
Status badge Pending until applied, Applied once the change reaches Moloco (click it to open the change in the Action Log), or Failed if it didn't (hover to see the error).
Search / filter / sort Narrow large tables with the Filter rows… box, per‑column filters, and sortable headers.

Proposed cells adapt to the field type: amounts like budgets and targets use a number input, while statuses use a dropdown of allowed values.

Reviewing → applying

  1. Review each row — compare the proposed value against the current one.
  2. Adjust any proposed value inline if you'd like something different from what was recommended.
  3. Select the rows you want with their checkboxes (or use the header checkbox to take everything).
  4. Click Apply (N) — the number reflects how many rows you've selected. The button stays disabled until at least one row is selected.
  5. Aliveo validates the changes, pushes them to Moloco, and shows the result:
    • Actions applied — "Selected recommendations were sent for execution."
    • Some actions could not be applied — a few rows failed validation; review them and retry.
    • Failed to apply actions — try again, or Refresh the table to reload the latest recommendations.

Applied rows flip to an Applied badge and their checkboxes lock, so you can't double‑apply the same change.

Built‑in guardrails

Before anything reaches Moloco, Aliveo runs each row through safety checks so you don't get cryptic API errors:

  • No‑op protection — if a row's proposed value already matches what Moloco holds, nothing is sent and the row is marked Applied.
  • Drift protection — if the account changed since the recommendation was generated (the "current" value no longer matches Moloco), the row is held back rather than overwriting newer data.
  • Moloco rule enforcement — Aliveo pre‑checks Moloco's constraints (see Things to know) and rejects rows that would violate them, with a plain‑language reason on the row.
  • Accept‑then‑ignore detection — a goal target that doesn't match how a campaign is optimized is accepted by Moloco and then quietly ignored. Aliveo reads back what Moloco actually stored after every change and fails the row if the value didn't move, rather than telling you a change landed when it didn't.
  • Whole‑entity safety — Moloco updates replace the entire campaign or ad group, so Aliveo always sends the live entity with only your change merged in. Settings you didn't touch — targeting, creative wiring, frequency caps — are preserved exactly as they were.
  • Change log & restore — every applied change is recorded (what changed, from → to, who, and when) in the Action Log, where you can track its impact and restore most changes with one click.

2. What You Can Action

Campaigns, ad groups, and creative groups can all be updated. On Moloco the campaign owns delivery — budget and bidding both live there — while ad groups and creative groups are switched on and off.

Campaigns

Action Values
Weekly budget For campaigns on a flexible weekly budget (in the account's currency). Fixed weekly schedules can't be edited — see Things to know
Daily budget For campaigns on a daily budget
Goal rate The budget‑centric pacing multiplier, between 0 and 2
Target CPI For campaigns optimizing to a target cost per install
Target CPC For campaigns optimizing to a target cost per click
Target CPM For fixed‑CPM campaigns
Target ROAS For ROAS‑optimizing campaigns, as a percentage (e.g. 312.5 = 312.5%)
End date Move a flight's end date out or bring it in
Status ENABLED / DISABLED

Which goal lever applies depends on how the campaign is optimized — see Goals below. Aliveo rejects a lever your campaign doesn't respond to.

Ad Groups

Action Values
Status ENABLED / DISABLED — pause or resume an ad group's delivery

Moloco ad groups carry no budget or bid of their own; those live on the parent campaign.

Creative Groups

Action Values
Status ENABLED / DISABLED — stop a group's creatives from serving, or bring them back

Creating entities

Creating campaigns, ad groups, and creative groups on Moloco isn't self‑serve yet — a new Moloco campaign needs a product, tracking link, goal configuration, country set, and creative wiring. Create them in the Moloco portal, then use Aliveo to optimize them. If you need campaign creation, talk to us.


3. /actioning in Analytics Chat

The fastest way to make a one‑off change is right inside a chat. Type / in the chat input to open the skills list, then pick actioning.

Selecting actioning tells Aliveo you want to change the account, not just analyze it. It then makes the actioning tools available so your request comes back as a ready‑to‑apply action table instead of a plain answer.

You don't always have to type /actioning — Aliveo also recognizes actioning intent from phrasing like "pause…", "reduce the weekly budget…", or "lower the target CPI…". Using the slash command simply makes your intent explicit.

Things you can ask with actioning:

  • "Pause the 2 Moloco campaigns with the highest spend and no installs."
  • "Reduce the weekly budget by 20% on campaigns spending over $500 a week."
  • "Raise the target ROAS by 10% on my best performing campaigns."
  • "Slow down pacing on the campaigns with the worst cost per install."

Aliveo finds the relevant entities, builds the action table, and hands it to you to review and apply.

The other skills, for reference: info (answer from context without running analysis), brainstorming (strategy and market exploration), web_search (pull in live external info), budget_allocation (recommend how to split budget — see Budget & Bid Allocation) and creative_features (label the videos in a Google Drive folder by creative feature). Only actioning produces apply‑ready action tables. See Starting a Chat for the full list.


4. Custom Actioning Workflows

For optimizations you want to run repeatedly — or assemble as a multi‑step routine — use a Custom Actioning Workflow agent instead of a one‑off chat. This is a blank‑slate agent template pre‑wired for actioning: you describe the analysis and the change, and the workflow produces an action table each time it runs.

You'll find it in the agent creation flow under Step 2: Template Selection (look in the Actioning Agents group).

Moloco Ads Custom Actioning Workflow

Blank‑slate actioning workflow for Moloco Ads at the campaign / ad group / creative group level (status, budgets, goal rate and targets, end time).

  • Use it for: weekly and daily budgets, goal rate and target adjustments, flight end dates, and pausing/enabling campaigns, ad groups, and creative groups.
  • Set up with: Ad Performance data.

How to build one

The template drops you into the workflow playground with the actioning tools already switched on, so you assemble the steps yourself:

  1. Shared Context — define anything common across steps (definitions, thresholds, the time window, e.g. "use the last 30 days").
  2. Analyze steps — do the data work: pull performance, compute metrics like cost per install or D7 ROAS, rank entities, and produce the proposed changes as an action table.
  3. Summary step — (optional, always last) logically summarize the combined output of the analyze steps.

Because this is an actioning workflow, the analyze step that proposes changes renders an action table in the workflow output — you still review and Apply exactly as you would in chat. (Custom Actioning Workflows are set up as one‑off agents so you stay in control of when changes are proposed.)

For the general agent‑building mechanics — accounts, data context, grouping, steps, preview, and scheduling — see Creating an Agent.


5. Examples — From Simple to Complex

Every example below is a single natural‑language request. Aliveo handles the analysis (finding the entities, computing the metric, ranking) and produces the action table — you review and apply.

Simple, single‑step actions

  • Budget — "Set the weekly budget to $2,000 on my top 2 campaigns by installs."
  • Status (campaign) — "Pause the 2 campaigns with the highest spend and fewest installs."
  • Status (ad group) — "Pause the ad groups with zero conversions and more than $200 spend in the last 30 days."
  • Status (creative group) — "Turn off the creative groups with no conversions this month."
  • Flight — "Extend the end date on my top campaign to the end of next month."

Metric‑driven optimizations

These combine an analysis with a change — Aliveo computes the metric, ranks, filters, then proposes the action:

  • CPI guardrail — "Reduce the weekly budget by 20% on campaigns with a cost per install above $5."
  • Wasted‑spend cleanup — "Find ad groups with over $250 spend and zero conversions in the last 30 days and pause them."
  • ROAS scaling — "Raise the weekly budget by 15% on campaigns with D7 ROAS above 30%."

Goal tuning

  • Pace back — "Slow down pacing on the campaigns overspending against their target."
  • Tighten targets — "Lower the target CPI by 10% on campaigns paying above target."
  • Push for return — "Raise the target ROAS by 10% on my best performing campaigns."

Multi‑step workflows you can assemble

In a Custom Actioning Workflow, you can chain several of the above into one routine:

  • Weekly efficiency pass — (1) Analyze: rank campaigns by cost per install, trim weekly budgets on the worst. (2) Analyze: rank by install volume at target CPI, raise budgets on the best. (3) Analyze: pause ad groups with sustained spend and no conversions. (4) Summarize what changed.
  • Return tune‑up — (1) Analyze: find campaigns under target ROAS and tighten their goal rate. (2) Analyze: find creative groups with weak conversion rates and disable them. (3) Summarize.

Each analyze step produces its own action table, so you can review and apply each set of changes independently.

Advanced, tailored workflows

Beyond the self‑serve patterns above, we build custom actioning workflows tuned to your account's strategy and scale. If any of these sound like what you need, talk to us and we'll set them up for you:

  • Sophisticated budget & goal management — goal‑seeking budget and target logic that reacts to CPI, CPA, and ROAS trends rather than simple top‑N rules.
  • Pacing — keep weekly spend on track to budget targets across the flight, with proposed adjustments when an account is over‑ or under‑pacing.
  • Creative rotation — retire fatiguing creative groups and promote fresh ones as their performance shifts.

These run as the same review‑and‑apply action tables, so even sophisticated logic stays fully under your control — nothing changes until you click Apply.


6. Things to Know — Moloco's Rules

Aliveo enforces Moloco's own constraints up front, so invalid rows are caught before they're sent. If you see a row rejected with a reason, it's usually one of these:

Statuses

  • Only ENABLED / DISABLED can be set. Everyday phrasing like "pause", "activate", or "turn off" is normalized to the right value automatically. Disabling never deletes anything — it's fully reversible.
  • A campaign's live delivery state is separate from whether it's enabled. Aliveo compares only the enabled/disabled setting, because Moloco's delivery state moves on its own and would otherwise look like a failed change.

Budgets

  • A campaign runs on one kind of budget — a daily budget, a flexible weekly budget, or a fixed weekly schedule (a separate budget for each day of the week) — and which one is fixed when the campaign is created. Aliveo only proposes the kind a given campaign actually uses; you can't switch an existing campaign from one to another.
  • Fixed weekly‑schedule budgets can't be edited from Aliveo. Change them in the Moloco portal; Aliveo can still change everything else on those campaigns.
  • Amounts are in the account's currency and must be greater than zero.

Goals

The campaign's goal decides which lever works. Setting a lever the goal doesn't use is accepted by Moloco and then ignored, so Aliveo rejects those rows up front and tells you why. Some levers also depend on the goal's mode (budget‑centric, target CPI‑centric, or target CPC‑centric):

Campaign goal Levers Aliveo can change
App installs Target CPI in target CPI‑centric mode; goal rate in budget‑centric mode
App ROAS (user acquisition) Target ROAS and target CPI; goal rate in budget‑centric mode
Clicks to app, clicks to web, and CPC re‑engagement Target CPC in target CPC‑centric mode; goal rate in budget‑centric mode
ROAS re‑engagement Target ROAS and goal rate
App retention Target CPI and goal rate, both in budget‑centric mode
Fixed CPM Target CPM
Fixed CPM with pacing Target CPM and goal rate
CPA goals (app user acquisition, app re‑engagement, repeated CPA, web), app reattribution, and web landing‑page goals Goal rate only, in budget‑centric mode

Campaigns on any other goal can't have their goal levers changed from Aliveo.

  • The goal rate must be between 0 and 2, where 1 is the campaign's baseline pace — below 1 slows spend, above 1 accelerates it.
  • Target ROAS is a percentage, not a multiple — 312.5 means 312.5%.

Ad groups and creative groups

  • Ad groups have no budget or bid of their own. Delivery is controlled at the campaign; the ad‑group lever is enable/disable.
  • Creative groups are enabled or disabled as a unit — Aliveo doesn't add, remove, or upload individual creatives.

Set once, at creation

  • A campaign's goal type, campaign type, device OS, and country set are fixed when the campaign is created and can't be changed afterwards. To optimize toward a different goal, create a new campaign in the Moloco portal.
  • A flight's start date is fixed; its end date can be moved.

These guardrails mean you can safely propose broad changes: any row that breaks a rule is marked Failed with the reason, and the rest go through.


That's actioning — analyze, review, and apply Moloco Ads changes without leaving Aliveo. Start with a quick /actioning request in chat, and graduate to a Custom Actioning Workflow once you find an optimization worth repeating.