Skip to content

Help · How Adintel decides

How builds are made

The rules behind a build: what it starts from, its products, budget and bidding, what is switched off, and how it is created, switched on, changed and undone.

Reviewed 21 November 2026

What does a build start from?

What the account has already sold over its last 90 days, from Adintel's copy of the account. The 90 days end on the newest day whose conversions have had time to arrive, such as three days ago, so the newest days are not counted (conversion days). A seller is a product with conversions in those days, under its feed label; a fraction of a conversion counts. Each seller is judged against the break-even of the campaigns it ran in, weighted by what it spent in each, so a product that ran in two campaigns is judged against both. A seller whose conversion value did not cover that is marked Below break-even. Whether Google shows a product now comes from Google's own product status, read each morning (product status). Until you check the build, it uses only Adintel's copy: nothing is read fresh from Google.

What is a market?

A Merchant Center account and one of its feed labels. Google identifies a product by its feed label and its item ID, so the same item under two labels is two products, in two markets. A market is named by the countries its campaigns target, such as US, UK or Canada. Where two labels get the same name, the one no campaign serves now, or else the one with fewer sellers, is named as a second feed, such as "US, second feed". A campaign serves a market when its products under that label had impressions or spend in the last 30 of the 90 days. The market's places are those its serving campaigns target, or, when none serves it now, those of the campaigns that served it earlier. Of the markets a campaign serves now, the page opens on the one with the most sellers.

Which products start ticked?

  • Under The sellers, every seller Google shows now, above or below break-even alike, except one that an enabled campaign serving this market excludes by its item ID: someone took it out there, so it starts unticked. A seller Google does not show now starts unticked too, with Google's reason.
  • By brand, product type, custom label or category, at the level chosen, each value that has a seller and whose products, together, returned at least your break-even; with no break-even set, every value that has a seller.
  • By item starts with nothing ticked, and Every product holds the whole feed label.

Each product the rule did not tick says why on its row, and you can change any tick.

How does a build make its product groups?

They are the new campaign's product groups, in its one asset group. In a build by item, each item is its own product group under one subdivision, and the catch-all group is excluded. Google allows at most 1,000 product groups in an asset group, the subdivision and its catch-all group included, so a build by item holds at most 998 products. By brand, product type, custom label or category, the subdivision is on that attribute, with a value below the first level nested under the levels above it: the ticked values are shown and each catch-all group excluded, or the reverse when every other product is shown. Every product is one product group, the whole feed label.

What are its budget, bidding and places?

The budget is the one you type, never filled in: a daily amount, or a total for a test period that starts tomorrow at the earliest, in the account's time zone, and runs at most 90 days, Google's limit. It is always the campaign's own. Google gives a total budget no channel setting of its own, so a campaign on one follows the account's default. The bidding follows your goal in Business context: with a ROAS goal, Maximize conversion value with your goal as its target ROAS; with a cost per conversion goal, Maximize conversions with your goal as its target CPA; either with no target, if you choose. Your break-even is never a target. Its places reach people in them or regularly there, never people who are only interested in them.

What does it bid to with no goal set?

The account's own figure, the one Adintel would assume under Fully automatic (the goal it assumes), in the measure Business context states: a cost per conversion where it states that, otherwise a ROAS.

  1. The target your enabled campaigns bid to in that measure; where several do, weighted by what each spent over the last 30 days, or a plain average when none spent.
  2. Otherwise, the account's own ROAS or cost per conversion over the 90 days ending on its newest day whose conversions are in, provided those days hold at least 10 conversions and some spend.
  3. Otherwise, none: the build starts with no target, and you can type your own.

The bidding then reads Bid to your campaigns' target or Bid to the account's own figure, with a line naming the figure and where it came from. A goal with a target set in Business context is always used first. A volume goal gives no figure: the page says Business context states your goal as volume with no target.

What is switched off?

Every automation switch a new Performance Max campaign has: text customization, final URL expansion, image extraction, enhanced videos, image enhancement, design versions of images and video crawl, seven in all, so the campaign shows your products as the feed has them. Google refuses its other automation switches on a new Performance Max campaign. Brand guidelines are off too: a campaign with no assets has no business name or logo of its own to show.

How is a build created?

Google checks the whole campaign first, without making it, and a build is created only from the draft Google accepted; change the draft afterwards and it needs a fresh check. If Google could not check it, the confirm asks you to check again rather than create it. Google asks every new campaign to declare whether it contains political advertising in the European Union, so the confirm asks you to tick that this one does not. Then one request creates everything: the budget, the campaign paused, its places and language, its asset group with no assets, its product groups, and, if it bids on your real outcomes only, a conversion goal of just those outcomes for this campaign. Google makes all of it or none of it. Adintel logs it as one change and reads it back from Google, to confirm the campaign is paused with a budget of its own, and has the feed label, asset group, product groups, places and language that were sent. The request is sent once: if Google's answer never comes, Adintel looks for the campaign by its name before calling it failed. Create and switch on creates the campaign the same way, then opens the switch-on's confirm only if it reads back as sent.

What does a build's Undo remove?

What the build made, in one request: the campaign, its own budget, and the goal it made, if it made one. The asset group and its product groups go with the campaign. Adintel reads the removal back from Google, and the build's draft stays under Builds, so you can build it again. A build that is switched on cannot be removed until you undo its switch-on, so that any products it excluded are back in your other campaigns before the campaign goes. If anything was changed in Google Ads since it was built, such as the campaign enabled or renamed, its budget or target changed, asset groups or assets added, or its product groups, places or language changed, the confirm lists it, and Undo goes ahead only once you tick the box it shows.

What does switching it on change?

First the campaign, from paused to enabled, through the same confirm and check as a campaign's controls. By default, Leave them as they are, your other campaigns do not change. Only if you choose Exclude these products from them does the switch-on also change each product group in those campaigns that holds one of the build's products, whether Google shows that product now or not, so that once Google shows it, it shows only through the new campaign. Those product groups are in every other enabled Performance Max or Standard Shopping campaign on the same Merchant Center account that uses the build's feed label or none. Products and product groups are read from Google as you open the confirm. Each ad group's or asset group's product groups change in one request, a logged change of its own. A product group Google refuses to change is left as it is, as are those below unless ticked, and one that holds none of the build's products is not touched. In Adintel, until a build is switched on from the Build page, nothing else switches its campaign on, and once it is, nothing else pauses it or switches it on again (outside the Build page).

How are its products excluded from your other campaigns?

Wherever one of the build's products sits now, the part of the other product group that holds it changes so the product stops showing there:

  • A part holding only the build's products, such as an item's own product group, is excluded.
  • A catch-all group under a subdivision on the build's own attribute gets the build's values added beside it, excluded.
  • Any other part is subdivided on that attribute: the build's values excluded, the rest of it as it was.

A build by item excludes its items from your other campaigns. A build by brand, product type, custom label or category excludes its values from them, so a product that takes one of those values later is excluded from that part too. For a build that shows every product except some values, your other campaigns keep those values and exclude the rest.

When is a product group left as it is?

When you choose Exclude these products from them, these are listed separately, marked Left as it is, each with its reason:

  • One that would be left with no product Google can show once the build's products are excluded. It changes only if you tick Exclude them here too. A build of every product leaves each product group in your other campaigns this way.
  • One whose campaign shows every feed label: excluding the build's products there would exclude the same items under its other labels too. It changes only if you tick it.
  • One Adintel cannot change as it stands, which is never sent: it cannot be read whole from Google Ads, or it subdivides on the same attribute twice, so Adintel cannot tell where a product sits in it, or a Performance Max asset group has no room left under Google's 1,000 product groups.

With room for only part of the change, as many as fit go ahead, and the line says how many of the build's products stay in it. On Standard Shopping, a part that still shows products keeps its bid; where a new part replaces parts that had different bids, it takes the lowest of those bids, and the confirm says so.

How is the switch-on undone?

Undo the switch-on puts every product group it changed back as it was, and only then pauses the campaign, so each product keeps showing through at least one campaign; where nothing was excluded, it only pauses the campaign. If a product group does not go back, because Google refuses it, it was changed in Google Ads since and the box to replace that change was not ticked, or the send failed, Adintel stops before pausing: the campaign stays enabled, and Adintel says how many product groups did not go back. Once paused, the build reads In Google Ads, paused again, with its own Undo. If the campaign was already enabled in Google Ads when it was switched on from the Build page, Undo the switch-on puts back any product group it changed, without pausing the campaign. The switch-on, and each product group it changed, is undone only from the Build page, and so are its products changed there, a pause and a later switch-on.

How is a change to its products made?

With the same grouping, only the product groups that change are sent, in one request. With a new grouping, every product group is removed, the lowest first, since Google refuses a group removed before the groups under it, and the new ones made, in the same request. Either way Google makes all of it or none, and the build's record follows what Google holds. Where its switch-on excluded products from your other campaigns, products added are excluded there too by default, by the same steps as the switch-on (how), unless you leave them as they are; products taken out go back by removing the exclusions the build made for them, unless you leave them out. Those campaigns change first where products go back, and last where they are excluded, so the order of the change never leaves a product the build held out of every campaign. A product taken out that cannot go back, such as from a build that shows every product except some values, holds the change until you leave it out of every campaign. The change's Undo takes the steps back in reverse; for a change that reached your other campaigns, only while the switch-on it was made under is in force.

What stays fixed?

The market, its Merchant Center account and its feed label: a different market is a new build. A daily budget cannot become a total for a period, or the reverse: Google fixes a budget's kind when the campaign is made. Audience signals and assets are not built for a feed-only campaign, and the Build page does not change them.

How does a build show in the record?

  • On the Timeline, the build and its removal each have a line, with no dot on the chart and no verdict, since a campaign built paused changes nothing that serves. Its status, its products, its settings and the products it excluded from your other campaigns or put back each have a line too, judged as Did it work says.
  • Made by Adintel lists the build, each change made to it and its removal, and leaves them all out when the build and its removal fall in the same period.
  • The client report counts the build under What we changed as "built, paused", one built earlier and removed in the period as removed, and, in a line of their own, the products its switch-on excluded from each of your other campaigns.
  • Automation treats a build, its switch-on, a pause and a later switch-on as a person's change to that campaign's budget and bidding, so no budget move touches the campaign for 14 days after any of them (automation).

Who can build?

An account's editors, on the Build page, on their own click; nothing builds or changes a campaign there on its own. Checking, creating, switching on, switching on again and every change need an active trial or plan; pausing and undoing do not. A viewer reads the page and its builds. In the demo, every button that would save or send something is switched off. An account set to observe-only shows its products, and nothing can be saved, checked or created there.