Review a proposed campaign change in chat. Keep every account within the limits you choose.
Google Ads automation with iNudge starts with the permissions you choose for one account. Supported fixes can run within saved limits and report a checked result. New ads, activation, higher total spending, destination changes and anything outside those limits need an exact review in chat before they can run.
Ask iNudge to cut a budget or pause a campaign and it writes a proposal. The card carries the value now, the value proposed, and any warning our own code computed. A proposal older than 24 hours is refused and has to be asked for again.
Verification runs in the same request as the publish, field by field against what you approved. A disagreement is recorded as a failed verification and never as a success.
Write access is off on every new connection. You enable it one account at a time. Supported fixes need a separate account permission and saved limits; new ads, activation, higher total spending and destination changes need your approval.
- 01The platform, derived from the action type by the same rule the executor dispatches on
- 02What changes, current value beside proposed value
- 03Every number the claim leaned on, with its verified source, window and freshness
- 04Warnings our server computed, sitting directly above the button
- 05Approve, dismiss, and on a budget card an edit whose typed figure is re-checked
Section 01 · the three switches
Three switches stand between iNudge and your money.
Writes are off when you connect.
Every connection is stored with write access off. While it is off, the change tools are left out of the request we send to the model, so there is nothing for it to call. It cannot propose a change it was never handed, whatever you ask it.
You arm one account at a time.
The write switch belongs to one connection. Enabling it lets the agent propose changes. It does not grant a saved advertising permission or turn writes on for another account. Turning it off blocks new writes and keeps the read connected.
You choose what iNudge may handle.
Supported fixes can have a separate permission for one account within saved limits. You can withdraw it. New ads, activation, higher total spending, destination changes and anything outside the permission need an exact decision. Current account access, evidence and result checks still apply.
Which permission we ask each platform for, and why neither one has a read-only version, is on the integrations page.
Section 02 · one change, start to finish
One change, start to finish.
Six frames, in the order they happen to you. Nothing here is a rendering of a future version: every frame is a step that exists in the code today.
"Prospecting is over my cost ceiling. Cut its daily budget to 320 USD." Plain words, in the chat, with no form and no builder.
Live reads fire at the moment you ask, and the trace above the answer shows each one: the tool, its one-line summary, and whether it succeeded. Google performance · last_14d. A read that failed shows as failed rather than being dropped so the answer can look cleaner.
The write tool creates a row awaiting your approval and returns a card. It does not execute. A number the agent cannot trace back to a read from that same turn blocks the proposal before a card exists.
The diff, the evidence, the warnings, then approve or dismiss. $420.00 → $320.00 is the whole change, written out. Leave it and nothing happens.
On approve the endpoint re-checks your subscription and that connection's write switch, refuses anything older than 24 hours, claims the row atomically so a double click cannot fire twice, re-runs the propose-time guards against fresh platform state, then sends exactly one write.
The platform is read back in the same request and compared against what you approved. A match settles the row as verified. A mismatch settles it as a failed verification, with the discrepancy in plain words.
Between frame 03 and frame 04 the product does nothing at all. That gap is the feature.
Section 03 · what you see before you approve
What you see before you approve.
The card above is not a mock-up of the product. It is rendered by the same function that turns a stored proposal into the card in your workspace, so every part below is the part you will actually read.
| Part of the card | What it shows | Where it comes from |
|---|---|---|
| Platform label | Meta, Google Ads, TikTok Ads or Merchant Center. | Derived from the action type by the same rule the executor dispatches on, so the label cannot disagree with where the write goes. |
| Title | The change in one line. | The summary stored on the proposal row, composed in code when the proposal was created. |
| Why | One sentence of the agent's reasoning. | The model's claim, stored with the proposal. It is the model's, and the card presents it as the model's. |
| Diff rows | Current value beside proposed value, one row per thing that changes. | Read from the platform when the proposal was drafted and stored as the before state and the requested state. |
| Evidence | Each number the claim leaned on: the metric, the value in your account’s currency, the verified data source, the scope it applies to, the reporting window and the data freshness. | The proposal's evidence list. The parse fails closed, so anything malformed renders as no claim and no receipts, never as invented ones. |
| Before you approve | The tradeoffs, in amber, directly above the approve button, in the awaiting state only. | Computed by our server before the card exists and stored outside the model's own schema on purpose, so the model can neither write these warnings nor suppress them. |
| Buttons | Approve and dismiss, plus an edit on a budget card. | The live card is handed an approve handler, a dismiss handler, and on a budget card an edit handler, so the edit button renders there and nowhere else. |
| Executing checklist | Write to the platform, then verify by re-reading. A budget move shows four rows, one pair per leg. | Built per action type by the same mapper. |
| Change | Platform | What the card shows |
|---|---|---|
| Publish one existing manual or separately reviewed catalog-driven Collection Instant Experience draft without changing ad delivery. | Meta Ads | Exact Page, experience ID, draft revision, full content and destination. Missing Page content permissions block the operation. One send and exact readback; no automatic retry or undo. |
| Create one unpublished manual or catalog-driven Collection Instant Experience. | Meta Ads | Exact Page, name, background and every ordered copy, destination, Page-owned photo/ready-video ID, fit and spacing. Fresh exact media proof is captured and rechecked. The separate nested contract reviews photo carousels, first-position photo headers and last-position button footers, including every child’s copy, media, destination and order. Child-first receipts and root-only assembly; no recursive groups. Fresh Page authority, one send per step and durable IDs. Partial results stop without replay or automatic deletion. Publication and ad activation need separate approvals. A separate Collection draft contract reviews a Page-owned hero, the existing commerce product set reached through an exact selected-account source ad, its full filter and ordering, dynamic product tokens, and a one-button footer. It requires fresh catalog and Page proof before every single-send step. This approval creates unpublished content only. A separate Collection publication contract reviews full content, exact hero media and catalog scope with fresh proof; product availability, selection and prices remain dynamic. A separate first-Collection-ad approval reviews a fully published Page-owned hero/product-set/footer experience, exact commerce source/catalog/set/filter/order, compatible existing paused sales/catalog website parents and complete SHARE or VIDEO creative. Fresh evidence and provider validation protect one paused ad send and exact-ID recovery. Dynamic product selection, availability and prices are not fixed promises. A separate Collection parent contract reviews complete campaign/ad-set/first-ad setup before creating one paused sales/catalog campaign, then one separately approved website purchase ad set under its exact verified campaign. Full published content, Page hero, commerce source/catalog/set/filter/order and audience/budget proof are rechecked; each child has separate approval after parent-ID verification. No empty campaign is offered, no existing parent or Page content is changed, and no uncertain send is replayed. Template-video and activation remain separate. |
| Change an exact campaign name, scheduling, bidding or an existing lifetime budget. Provider validation, current-state binding, exact currency, policy checks and verification follow one request. | Meta Ads | Exact old and new names or delivery settings. A name-only change preserves entity ID and delivery; later name changes require a fresh approval. |
| Change an exact ad-set name, targeting, placements, audiences, bidding, attribution, optimization, scheduling or an existing lifetime budget. Closed settings preserve untouched targeting. Ownership, caps, locks and blackout windows apply. | Meta Ads | Exact old and new names or delivery settings and verified parent. A name-only change preserves entity ID and delivery; activation is a separate approval. |
| Create one paused Meta campaign. Explicit objective, special-ad-category declaration, exact budget mode and every included child are reviewed. Meta validates each object and verifies it paused. A complete-setup review can include the exact paused ad sets and ads in the same approval. Older object-only cards retain their original scope. Collection sales/catalog creation requires its separate full published-content/catalog contract and complete consistent ad-set/first-ad plan before this campaign approval. | Meta Ads | Exact reviewed settings, verified parents and assets, paused creation and separate activation approval. |
| Activate one exact iNudge-created complete Meta setup. | Meta Ads | Off by default; the operator must explicitly switch it on. Platform and account write access and a separate exact approval are required. Only the exact verified iNudge-created campaign, ad sets and ads from one complete paused setup are included. Activates children before the campaign. Configured ACTIVE does not guarantee delivery; effective status and provider issues are shown separately. Interrupted steps are observed before a new remaining-scope approval; no automatic retry or rollback. Arbitrary or bulk enable remains unavailable outside this exact setup contract. |
| Create one paused Meta ad set. Parent campaign, budget ownership, targeting, pixel/event and selected assets are rechecked before one send. Collection website purchase ad sets have a separate full published-content/catalog contract under the exact paused sales/catalog campaign; the ad still needs separate approval. | Meta Ads | Exact reviewed settings, verified parents and assets, paused creation and separate activation approval. |
| Create one paused standard image/video ad, fixed-order website carousel of 2–10 verified cards, first ad for a published manual Instant Experience or catalog-driven Collection, or reuse a verified account-owned Page-post creative in a website ad set. | Meta Ads | Exact reviewed settings, parents and assets; every carousel card and its order, full published experience content and single image/video cover without a source ad, or the existing creative, Page, post and destination IDs. Post reuse changes no content and guarantees no engagement. No automatic reordering or end card; catalog-driven Collection uses its own full published-content/catalog/paused-parent contract with exact Page hero and ad copy, dynamic products and prices, and no new parent authoring. Media transfer, Page publication and activation require separate approvals. |
| Duplicate one paused Meta object without descendants. Campaign and ad-set copies use the native copy endpoint without validate-only. Standard ad copies instead create one paused ad with the exact existing creative and reviewed tracking; validate-only runs first. Unsupported ad-level settings are blocked rather than dropped. No timeout write is retried. | Meta Ads | Exact reviewed settings, verified parents and assets, creative preservation for standard ad copies, paused creation and separate activation approval. |
| Transfer one private library MP4 up to 50 MiB without changing ads. | Meta Ads | Exact file, checksum and destination approval; one send, saved video ID and read-only processing checks for up to 24 hours. |
| Transfer one private library PNG or JPEG, up to 10 MiB, to the selected Meta ad account without changing ads. | Meta Ads | Exact filename, size, checksum and destination; separate approval, one send and verification by account image hash. |
| Campaign status | Meta Ads | One status row, ACTIVE to PAUSED or the reverse. |
| Campaign daily budget | Meta Ads | One daily budget row, both figures in your account's currency. |
| Budget move | Meta Ads | One row per leg, with the total held constant. The source falls by exactly what the destination rises by. |
| Ad-set status | Meta Ads | One status row, ACTIVE to PAUSED or the reverse, plus Meta’s effective delivery state after the write. |
| Ad status or name | Meta Ads | One status row, ACTIVE to PAUSED or the reverse, plus Meta’s effective delivery state; or one exact before/after ad name with unchanged configuration. |
| Ad-set daily budget | Meta Ads | One ABO daily-budget row, with current and requested figures in the ad account’s currency. |
| Ad creative replacement | Meta Ads | Exact standard copy/media edits, all 2–10 website carousel cards or a bounded authorized identity change with the old and new Page/Instagram IDs. Page changes are Facebook-only; Instagram changes retain the existing Page. Actor, story and parent stay bound; automatic reordering and end cards are off. Meta creates and attaches a replacement creative, may review it again, and does not preserve old post engagement or change ad status. |
| Campaign status | Google Ads | One status row, ENABLED to PAUSED or the reverse. |
| Permanent campaign removal | Google Ads | Released in Production for admitted workspaces. The card names the exact already-paused campaign, its budget identity and the permanent loss of its campaign ID, history and learning state. Google validates and receives one non-retried removal. |
| Pause a campaign batch | Google Ads | Released in Production for admitted workspaces. The card lists 2–10 exact enabled campaigns, requires a second confirmation and applies them as one atomic pause. Every campaign is re-read afterward. Bulk enable, budget, targeting and mixed changes are excluded, and there is no one-click bulk undo. |
| Label relationship | Google Ads | Released in Production for admitted workspaces. The exact campaign, ad group, ad or keyword and the label’s current relationship are shown before one label is created, attached or removed. |
| Asset relationship | Google Ads | Released in Production for admitted workspaces. The card shows the exact campaign or ad group, the existing asset’s type and content summary, the current link status and the requested attach, pause, enable or removal before you approve. |
| Performance Max asset-group settings | Google Ads | Released in Production for admitted workspaces. The card shows the exact current and requested name, enabled or paused status, HTTPS destinations and display paths for one existing asset group. Creative, audience, product, budget and bidding settings stay unchanged. |
| Performance Max signal | Google Ads | Released in Production for admitted workspaces. The card names the exact asset group and one search theme or existing audience being added or removed, and warns that signals guide Google rather than confining delivery. |
| Shopping product-group leaf | Google Ads | Released in Production for admitted workspaces. The card names the exact Performance Max asset group or Standard Shopping ad group, existing non-root leaf and inclusion change, or the exact before-and-after Manual CPC bid in the account currency. It warns that the whole tree must remain unchanged and that inclusion can change delivery. |
| Campaign name | Google Ads | One exact name row for one existing campaign. Status, budget, targeting and delivery remain unchanged. |
| Search Partners | Google Ads | Released in Production for admitted workspaces. One exact On/Off row for an existing Search campaign, with warnings about reach, spend and the limits of undo. |
| Campaign dates or tracking | Google Ads | Released in Production for admitted workspaces. Exact before-and-after date rows with the account time zone, or exact campaign tracking values. Clearing an end date says No end date; clearing tracking says Not set at campaign level, because inherited tracking can remain. |
| Campaign targeting and delivery controls | Google Ads | Released in Production for admitted workspaces. One exact operation shows the reviewed country, region, radius or language target, demographic exclusion, device modifier, complete account-time-zone schedule or placement exclusion, with delivery and undo warnings. |
| Standard bidding strategy, target CPA or target ROAS | Google Ads | Released in Production for admitted workspaces. The card shows the previous and proposed standard strategy or target, with target CPA in the account currency and target ROAS as both a percentage and multiplier. Strategy switches also bind the campaign’s complete conversion-goal evidence. |
| Portfolio target CPA or target ROAS | Google Ads | Released in Production for admitted workspaces. The card shows the exact strategy and target, every linked campaign and the combined daily-budget ceiling, counting shared budgets once. |
| Campaign daily budget | Google Ads | One daily budget row, both figures in your account's currency. |
| Shared daily or campaign total budget | Google Ads | Released in Production for admitted workspaces. One exact row shows the budget amount or name before and after, in the account currency where applicable, and names every linked campaign affected by a shared-budget change. |
| End one running experiment | Google Ads | Released in Production for admitted workspaces. The card names the exact experiment, its traffic split and affected campaigns, explains that treatment stops without being promoted, requires a second confirmation and states there is no one-click undo. |
| Dismiss one Google-native recommendation | Google Ads | Released in Production for admitted workspaces. The card names the exact recommendation ID and type, says the impact estimate came from Google, and states that dismissal is permanent while campaign delivery stays unchanged. |
| Campaign conversion goals | Google Ads | Released in Production for admitted workspaces. The card names the exact campaign, goal category and source, whether Google may bid toward it, and whether the campaign will use its own map or the account defaults. Every approval requires a second confirmation. |
| Create a secondary conversion action | Google Ads | Released in Production for admitted workspaces. The card shows the exact secondary website or call conversion action and its settings, requires a second confirmation, and returns Google’s installation code after a verified create. iNudge does not install or verify the tag, make the action primary, or change attribution and account defaults. |
| Create an account-level callout | Google Ads | Released in Production for admitted workspaces. The card shows the exact 1–25-character text and account-level scope, requires a second confirmation, and warns that Google may still review or limit the new asset. |
| Create a detached call asset | Google Ads | Released in Production for admitted workspaces. The card shows the exact phone number, reporting choice and complete account-time-zone business hours, requires a second confirmation, and explains that creation does not attach the immutable asset. A replacement leaves the old asset unchanged. |
| Create a detached Google-hosted lead form | Google Ads | Released in Production for admitted workspaces. The card shows every visible sentence, requested field, privacy policy, post-submit destination and policy attestation, requires a second confirmation, and explains that creation does not attach the form. Leads remain in Google-hosted download rather than iNudge. |
| Negative keywords | Google Ads | One row per term, each showing the term and the match type that will block it. |
| Remove campaign negative keywords | Google Ads | One row per exact existing term, including match type, before removal. |
| Manage positive keywords | Google Ads | One row per exact keyword in one ad group, showing match type and the current and requested status, or that a term will be added or removed. |
| Manage an existing ad group | Google Ads | One exact row for ad group status or name, with the current value beside the requested value. |
| Manage Search ad-group structure or an existing audience link | Google Ads | The exact paused creation, removal, Manual CPC bid change, or existing user-list inclusion, exclusion or Observation/Targeting mode. Released in Production for admitted workspaces; removals are permanent. |
| Change location-presence mode | Google Ads | The previous and requested location-presence mode for one Search campaign. Released in Production for admitted workspaces. Existing targets and exclusions remain unchanged. |
| Create a paused Search ad | Google Ads | Every headline, description, pin, destination and display path in an existing ad group. One supervised validation-and-create run passed in an isolated Preview. The family is released in Production for admitted workspaces, and creating the ad still requires exact approval. |
| One reviewed set of Search keyword bids | Google Ads | Every selected keyword name and exact bid in one account. Each row has its own checked result. Only proven-unsent failures can be tried again; successful and uncertain rows are excluded. |
| Change a keyword bid, destination or match type | Google Ads | The keyword identity and current Manual CPC bid, HTTPS destinations or match type beside the exact requested value. Released in Production for admitted workspaces. Match-type replacement changes the criterion id and cannot preserve learning state. |
| Existing ad status | Google Ads | One exact status row for one existing ad, with its ad-group and campaign context. This status operation leaves content unchanged. |
| Permanent paused-ad removal | Google Ads | One exact already-paused ad and its campaign and ad-group context, with a permanent-removal warning. Released in Production for admitted workspaces; the same ad id and learning state cannot be restored. |
| Paused responsive search ad text and destinations | Google Ads | Released in Production for admitted workspaces. Every headline, description, pin, HTTPS final URL and display path is shown. The exact ad and its parent state are bound to the card, and the ad remains paused after a verified update. |
| A new campaign, paused | Google Ads | No before and after rows, because nothing exists yet. The card shows the campaign itself: budget, countries and languages, every keyword with its match type, every headline and description with its character count against the platform limit, and each image you uploaded. |
| New TikTok campaign | TikTok Ads | No before and after rows, because nothing exists yet. The card shows the campaign itself: budget in the advertiser's own currency, objective, locations, the schedule in TikTok's own time format, which identity the ad runs under, the ad text against TikTok's character limit, and the video id it will use. It also says plainly that TikTok has not validated any of it, because TikTok publishes no way to check a campaign before creating it. |
| Transfer one exact private MP4 | TikTok Ads | The exact file, checksum, size and advertiser. One send, no automatic resend and read-only video-ID recovery. Creating or activating ads needs separate approval. |
| Existing TikTok campaign status | TikTok Ads | The exact campaign, current configured and effective status, requested status and current budget context. Enabling is checked against spending caps before the card can run. |
| Existing TikTok ad-group status | TikTok Ads | The exact ad group and parent campaign, current configured and effective status, requested status and configured budget. The card expires if that evidence changes. |
| Existing TikTok ad status | TikTok Ads | The exact ad and both parent ids, current configured and effective status and requested status. Enabling also rechecks the parent ad-group budget cap. |
| TikTok ad-group daily budget | TikTok Ads | The exact ad group, advertiser currency, current configured daily budget and requested amount. User edits are recorded, and magnitude, lock, blackout and spending-cap checks run again before execution. |
| Publish the product feed | Google Merchant Center | How many products would be added, updated and removed, and how many are already published unchanged. On a first publish the card also names the Merchant Center account and the data source iNudge would replace, because that publish takes over the feed serving your Shopping ads. |
The warnings are the part a model cannot touch. They are computed in our own code before the card is built and stored beside the model's reasoning rather than inside it, deliberately absent from the schema the model writes into. So a model that would rather you did not see a tradeoff has no field to put it in and no field to take it out of.
The card carries no estimated saving and no projected impact. We do not compute one, so it does not show one. A modeled figure on a money decision is the kind of number that gets quoted back at us and cannot be defended, and its absence is deliberate rather than an omission.
You can correct the number before approving. A budget card lets you type the figure you want. It runs the same magnitude, churn and cap checks the agent's figure runs, and it is recorded as a human-stated figure the model can never originate, so an edited number is re-checked rather than trusted blind.
Section 04 · what it can change
What it can change. What it cannot.
Sixty-one operations across four platforms. Meta now includes separately approved activation of one exact verified iNudge-created complete setup, exact ad-set/ad status, ABO ad-set daily budgets and bounded standard link/video creative replacement in addition to campaign controls and budget rebalancing. Google Ads campaign creation is released in Production for admitted workspaces. TikTok Ads can create a paused campaign and prepare exact existing campaign, ad-group and ad status changes or one ad-group daily-budget change when both write switches are on. Each of the thirty-two Google action families has its own gate and is released in Production for admitted workspaces. They include bounded campaign batches, permanent paused-campaign removal, experiment end, recommendation dismissal, Performance Max and Shopping controls, budgets, conversion goals, secondary conversion-action creation with code returned for installation, account-level callout creation, detached call-asset creation, detached Google-hosted lead-form creation, campaign settings, location and delivery targeting, standard and portfolio Smart Bidding targets, paused Search-ad content, ad-group structure and existing audience links, keyword settings, labels, existing asset relationships, new paused Search-ad creation and permanent paused-ad removal. Experiment creation, experiment scheduling, promotion and graduation and Google’s generic recommendation apply endpoint are not implemented. This is the whole implemented list, followed by what is missing.
| Platform | What iNudge can propose today | What it cannot do today |
|---|---|---|
| Meta Ads |
| Delete campaigns, ad sets or ads; upload video beyond the separate 50 MiB MP4 transfer or arbitrary remote media; create audiences, deep-copy trees or create dynamic/catalog creatives. Change carousel, collection, existing-post or unsupported creatives, an existing campaign objective or account settings. |
| Google Ads |
| Create or edit most asset content, manage location asset sets, or change Performance Max asset-group assets. Edit image, video or non-responsive-search creative, or edit the content of an enabled ad. Create audiences, upload Customer Match data or build arbitrary Shopping trees. Delete enabled campaigns or enabled ads. Edit or remove an existing conversion action, install or verify tracking code, change attribution, or turn budget sharing on or off. Move budget between campaigns as one conserved operation: there is no Google Ads rebalance tool, and the agent is instructed to say so rather than fake one with two separate writes. |
| Google Merchant Center |
| Change bids, budgets or campaigns. Change your Merchant Center account settings, shipping, tax or returns. Delete a data source. Touch an account you did not connect. Merchant Center accepts products one at a time, so a publish reports each item's outcome and can end partial; it never claims Google approved anything, because approval arrives later and the feed audit is what reports it. |
| Shopify | Nothing. Shopify is read-only today: no write permission is requested and no write path exists in the code. | It is absent from the list of providers the write switch accepts, so the switch refuses to arm for it. There is no proposal tool and the code that executes approved changes has no Shopify branch. |
| TikTok Ads |
| Change bids, targeting, schedules, identity, creative or destination on an existing object. Delete anything. Upload remote media. A selected private MP4 can be transferred through its own approval; campaign creation requires a ready advertiser video. Change audiences, pixels or the Events API. TikTok has no all-or-nothing create, so campaign, ad group and ad are three separate calls; every object is created paused, and a build that fails part-way names exactly which objects exist rather than reporting a bare error. |
| Google Analytics 4 | Nothing. The permission we request is read-only. | We read your property list and your traffic by source. No write permission, no mutating call. |
| Google Search Console | Nothing. The permission we request is read-only. | We read your site list and your search queries and pages. No write permission, no mutating call, and there is no write path. |
Not built: LinkedIn Ads, Microsoft Ads, Pinterest Ads, Snapchat Ads, Klaviyo, Amazon Ads. No connector, no login flow, no API client and no agent tool for any of them. We write not built rather than planned, because that word is a delivery promise and there is no date behind one.
Four connected platforms have at least one bounded write operation: Meta Ads, Google Ads, TikTok Ads and Merchant Center. Everything else we connect is read-only by construction rather than by policy. The bound is structural: one function in our code sends every Meta change, including the closed placement-value, audience and bid-cap operations, and the account-level spend cap set at connect. Background reporting also uses that sender to request a report, without changing advertiser settings. Google mutations compile from closed service-specific operation lists, including exact criterion removals, ad-group changes, existing-ad status changes and a separate permanent-removal operation restricted to already-paused ads. Atomic multi-operation paths carry paused campaign creation, the Google families released in Production for admitted workspaces and a separate 2–10 campaign pause batch. Separate non-retried Google endpoints can permanently dismiss one exact provider recommendation without applying it, end one exact running experiment without promoting treatment changes or selecting a winner, and create verified detached call or Google-hosted lead-form assets. All thirty-two Google action families are released in Production for admitted workspaces. Each change needs that account’s write switch and either approval of the exact change or a current permission for that supported fix. No outbound operation can delete an enabled campaign, an enabled ad, an account or a conversion action.
Where this stands today.
Meta is a reviewer-only path. Meta's read and write code is implemented, but Meta app review is still in progress. Access is limited to Meta reviewers and explicitly allowlisted test accounts, and no Meta capability is offered to other beta customers.
Google Ads is open to the controlled beta. Account reads and recommendations are available to beta customers. All thirty-two Google action families are released in Production for admitted workspaces. Each change needs that account’s write switch and either approval of the exact change or a current permission for that supported fix. Google Ads campaign status, campaign name and one private daily-budget path have supervised Production write-and-inverse evidence. The other released families do not yet have that same provider-evidence standard.
Every field we read from each platform, and the permission behind it, are on the integrations page.
Section 05 · the limits, in code
The limits live in code, not in a prompt.
Two kinds of rule. A block means no approval card is ever created, so there is nothing to press. A warning means the card is created and carries the tradeoff above the button.
| Rule | What happens | Where it applies |
|---|---|---|
| A budget increase larger than 300% | Warning A smaller step is recommended. Proceed with the requested amount after acknowledging this exact change on the approval card. Saved caps and platform checks still apply. | Meta campaign, Meta ad set, Google Ads campaign |
| A budget change larger than 20%, up or down | Warning Allowed, with the tradeoff printed on the card above the approve button. | Meta campaign, Meta ad set, Google Ads campaign |
| A Google Ads budget shared with other campaigns | Block Blocked when the proposal is drafted, and blocked again by the executor before it sends, because changing it would move money in campaigns you did not review. | Google Ads campaign budget |
| A Meta campaign whose budget lives on its ad sets, or that runs on a lifetime budget, or an amount of zero or less | Block Blocked. | Meta campaign budget |
| A campaign already in the state being asked for, or deleted, or archived | Block Blocked, with the campaign's real current state named. | Meta status changes |
| A Google Ads campaign that has been removed, or cannot be read from the account | Block Blocked when drafted, and re-checked against live state before the write is sent. | Google Ads changes |
| A budget move whose two sides sit in different ad accounts | Block Blocked, failing closed, because two accounts can bill in two currencies. It is blocked the same way when the account cannot be confirmed at all. | Meta budget move |
| A budget move that would take the source to zero or below | Block Blocked. Turning a campaign off has to be proposed as a pause and approved as one. | Meta budget move |
| A campaign covered by a lock rule you wrote | Block Blocked in code, and the refusal quotes your own words back at you. | Meta and Google Ads status changes |
| A number in the proposal that cannot be traced to a live read from that same turn | Block Blocked before a card exists, with strict matching, so a hundredfold unit error cannot pass as a rounding difference. | Every change |
| A proposal older than 24 hours | Block Refused at approve time. Nothing transitions and nothing is sent. Ask again and the account is read afresh. | Every change |
| Writes switched off after the proposal was drafted | Block Refused at approve time. The card stays pending with the reason on it. | Every change |
| A Google Ads change that could apply to more than one connected account | Block Blocked. iNudge asks which account you mean instead of guessing. | Google Ads changes |
| Negative keywords per proposal | Warning Bounded between 1 and 20, in the schema the model is offered and again at runtime. | Google Ads negative keywords |
| Pressing approve twice | Warning An atomic claim on the row means exactly one write goes out. The second press loses the race and is answered with the first one's result. | Every change |
These are not instructions in a prompt the model could talk itself out of. They run in our own code, before the model's output ever reaches a card, and the ones that guard money run again at the moment you press.
Section 06 · the second you press approve
What happens the second you press approve.
Seven steps, in one request. There is no queue, no worker and no callback: the write and the check that proves it are the same round trip.
- 01Your subscription and that connection's write switch are re-checked at the moment you press, not at the moment the proposal was written.
- 02Anything older than 24 hours is refused, and nothing transitions.
- 03The row is claimed atomically, moving from proposed to executing. A second press loses the race and replays the same answer.
- 04Inside the claim, the propose-time guards re-run against fresh platform state. If the account moved underneath, the row settles as failed with the reason and nothing is sent.
- 05Exactly one write goes to the platform.
- 06The platform is read back, in the same request.
- 07The re-read is compared against what you approved, field by field. A match settles as verified. A mismatch settles as a failed verification with the discrepancy stored in plain words, for example "Re-read shows 420 USD, not 320 USD."
A proposal is a claim about a moment. Past 24 hours the numbers on the card describe an account that has moved, so the honest answer is to ask again rather than to execute on a snapshot nobody re-checked.
Activating a Meta campaign counts as done when Meta saved it, and what Meta is still doing with it is shown as a state. Meta reports a campaign's own status and its effective status separately, and a campaign can be ACTIVE in name while gated by review, by budget or by an account issue. The check verifies the saved status and reads the effective one into words on the card ("Meta is still reviewing the ad"), then reads it again until it clears, so a review hold is never dressed as a failed change and never hidden as a live one.
If the guards cannot be re-run, nothing runs. An action type with no re-checkable guard is refused rather than allowed through on a pass that was a claim about nothing, and a read failure before the write settles the row as failed with the reason instead of executing blind.
Section 07 · the record it leaves
Every change leaves a record you can read.
One row in our database per proposal, approved or not, written as the change moves through its states. This is what the row holds.
| Field | What it holds |
|---|---|
| Summary and action type | What was proposed, in words, and which of the sixty-one operations it was. |
| Target and connection | The campaign, ad set or campaign target, and which connected account it belongs to. |
| Conversation and message | The exact turn of chat the proposal came out of. |
| Decision | The agent's claim, its confidence, its evidence list, and the warnings our server computed and showed you. |
| Before state | What the platform said before, at propose time. |
| Requested state | What you were asked to approve. |
| Executor result | What the platform returned. |
| Verified state | What the platform said when we read it back. |
| Verification result | Whether those two matched, and the discrepancy where they did not. |
| API error | The provider error or host safety reason, mapped into a title, a detail and a suggested fix. |
| Timestamps | Created, decided, executed. |
The states a change can be in
Only finished rows become receipts. A proposal still waiting on you is not a receipt, because nothing has happened. The ledger on your Today screen is built from rows that reached a decision, so it is a record of what was done rather than a list of what was suggested.
One thing we will not claim. The record stores that a change was approved, when, on which account, and which signed-in person pressed the button. Workspaces can include an Owner and Members, so that person-level record is what makes each approval accountable. A proposal that expires because a newer one replaced it records no approver, because nobody approved it.
How long we keep all of this, and how to have it deleted, is in the privacy policy.
Section 08 · when something goes wrong
When something goes wrong, it says so.
The second fear about letting anything touch a live account is not that it refuses. It is that it fails halfway and nobody tells you. Here is every way this can end badly and what you see in each case.
| What went wrong | What you see | What we do |
|---|---|---|
| The platform rejects the write | failed Failed, not confirmed live, with the provider's own reason translated into a sentence and a suggested fix. | Nothing changed. The row settles as failed. |
| The write applied and the re-read disagrees | verification failed A failed verification, with the discrepancy written out. | It is not marked done and it does not go green. The mismatch is stored on the row so a reload shows the real difference rather than a generic sentence. |
| A budget move fails after its first leg | rolled back Which legs applied, and that the account was put back. | Compensation runs on its own: applied legs are restored in reverse order and re-read to confirm they landed. The row settles as rolled back. |
| The compensation itself fails | rollback failed Could not fully undo, action needed, naming the exact entities and the value each should be back at. | We say the true thing rather than the comfortable one: a step failed, we could not fully undo it, and your account may be changed. Check these in Ads Manager. |
| Something throws after the write was sent | failed Failed, with the real error. | The write may or may not have applied, so we say exactly that and tell you to re-check the campaign before retrying. The row is never left stuck mid-flight. |
| The guards refuse before anything is sent | failed The account changed since this was proposed, with the blocker named. | Nothing was sent. The row settles as failed and says so, which is a different sentence from the one above on purpose. |
Undo shows the exact settings to restore. Supported earned-change receipts offer an exact undo for 24 hours. Your tap authorizes only the displayed previous settings after a fresh account check. Other eligible verified Google Ads and TikTok receipts prepare a separate approval. Unsupported or unverified actions need a new review. Undo cannot recover spend, impressions or learning effects. Compensation inside a failed Meta budget move remains separate. Uncertain platform writes are not automatically replayed.
A mismatch is never recorded as a success. The status a card shows is derived from the re-read, not from the platform's own reply, so a partial cannot be presented as a completion. That is why the verified footer says the change was confirmed live by re-read rather than saying the platform accepted it.
Section 09 · the questions worth asking
The questions worth asking.
Can iNudge change my campaigns without asking me?
No, and two separate gates stand in the way. A connection is read-only until you switch writes on for that specific account, and while it is off the change tools are never handed to the model. With writes on, supported fixes may run only within a separate permission and saved limits for that account. You can withdraw it. Changes outside that permission still wait for your exact approval.
What if I never approve anything?
Nothing changes. Proposals sit there and are refused after 24 hours. Read-only features can continue without enabling writes. Repeat audits, daily monitoring, alerts and AI features require an active trial, plan or eligible Shopify install.
What happens if a change fails halfway through?
Two cases. A single change either lands or does not, and the re-read tells you which. A budget move has two legs, so if the second fails the first is put back automatically and the row is marked rolled back. If a leg cannot be put back, we say so and name the exact campaigns to check in Ads Manager instead of pretending it resolved.
Can I undo a change?
Supported earned-change receipts offer an exact undo for 24 hours. You see the previous settings and tap once to restore them after a fresh account check. Other eligible verified receipts prepare a separate approval. Unsupported or unverified actions need a new review, and undo cannot recover money already spent.
What are the hard limits?
A budget increase larger than 300% requires acknowledgment of the exact change on the approval card. You can edit the amount or proceed after reviewing the recommendation. A change larger than 20% carries a spending explanation; that percentage alone does not prove a learning reset. Saved spending caps, campaign locks, permissions and platform checks still apply. Conflicting saved rules need an explicit settings change before a new approval.
Can it invent a number to justify a change?
Structurally, no. Every figure on a proposal has to trace back to a live read from that same turn, the check runs before the card is built, and the metric it can cite is a closed list of the metrics our read tools actually return. A proposal with an untraceable number is refused rather than softened.
Which platforms can it actually change?
Google Ads, TikTok Ads, GA4, Merchant Center, Search Console and Shopify are open to the controlled beta. Meta Ads is reviewer-only while app review completes. All thirty-two Google action families are released in Production for admitted workspaces. Each change needs that account’s write switch and either approval of the exact change or a current permission for that supported fix. TikTok Ads changes are available to admitted workspaces with both write switches on and exact approval. Meta has implemented change operations but is reviewer-only. Merchant Center publishing is supervised-only. Shopify, GA4 and Search Console have no customer write path.
What if I click approve twice?
The row is claimed atomically, so exactly one write goes out. The second press gets the same answer as the first, because the endpoint is idempotent rather than because the browser stopped you.
Do you record which of us approved it?
Yes. We record that a change was approved, when, on which account, and which signed-in person pressed the button. Workspaces can include an Owner and Members, so each approval is attributed to the person who made it. A proposal that expires because a newer one replaced it records no approver, because nobody approved it.
Do I need a paid plan to publish?
Google Ads connection and one initial audit need no card. Repeat audits, daily monitoring, alerts and AI features require an active trial, plan or eligible Shopify install. Merchant Center publishing is supervised-only. Approving a permitted change draws no credits, but the conversation that produced it does.
Controlled beta
Start read-only. Turn writes on only when you trust the evidence.
Sign up with one active Google Ads account. You review the first recommendation before any write capability is considered.
- writes off until you switch them on, per account
- one card, one decision, no bulk approve
- every figure on this page: one demo account
You connect read-only first. You choose which supported fixes iNudge may handle within saved account limits. New ads and higher total spending need your approval.
Receipts
- Write access is off on every new connection. While it is off, the agent's change tools are left out of the request sent to the model, so it is never handed them.
- Write access is granted per connected account and can be withdrawn without disconnecting the read. Arming one platform never arms another.
- Every product view and every figure on this page is the Gymszy sample account, labeled as demo data where it appears. Nothing here is presented as a customer result, because there are none to present yet.
- Warnings on a proposal are computed by our server and stored beside the model's reasoning rather than inside it, deliberately outside the schema the model writes into, so it can neither author them nor remove them.
- Google Ads, TikTok Ads, GA4, Merchant Center, Search Console and Shopify are open to the controlled beta. Meta Ads is reviewer-only while app review completes. All thirty-two Google action families are released in Production for admitted workspaces. Each change needs that account’s write switch and either approval of the exact change or a current permission for that supported fix. TikTok Ads changes are bounded and available to admitted workspaces with both write switches on and exact approval. Merchant Center publishing is supervised-only. Shopify, GA4 and Search Console have no customer write path.
- A budget increase larger than 300% requires acknowledgment of the exact change. A change larger than 20% in either direction is explained on the card. Saved limits and platform validation still apply.
- A proposal older than 24 hours is refused at approve time and has to be asked for again against a fresh read.
- Every approved change executes exactly once and is verified by reading the platform back in the same request and comparing it, field by field, against what you approved. A mismatch is recorded as a failed verification, never as a success.
- The record stores that a change was approved, on which account, and which signed-in person pressed the button. Workspaces can include an Owner and Members, so each approval remains attributable to the person who made it.
- Compensation inside a failed Meta budget move remains automatic. Supported earned-change receipts separately offer an exact 24-hour undo; other eligible verified receipts prepare a new approval. Undo cannot recover spend or delivery effects, and uncertain platform writes are not automatically replayed.