> ## Documentation Index
> Fetch the complete documentation index at: https://academy.uagenius.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Publish to Google

> Upload finished variations into Google Ads campaigns and ad groups.

Upload finished variations to Google Ads from a project's results view: **Select All → Upload ads → Google**.

Google uses a three-pane walkthrough that you complete for each batch.

## Before you start

Two connections are needed under [Integrations](/integrations):

<CardGroup cols={2}>
  <Card title="Google Ads manager" icon="google">
    The account the ads are created in.
  </Card>

  <Card title="YouTube" icon="youtube">
    Video ads are uploaded to your connected YouTube account before Google serves them, so this one pairs with Google Ads.
  </Card>
</CardGroup>

<Tip>
  Connect YouTube at the same time as Google Ads manager. With both in place, a finished batch can go live straight away.
</Tip>

## The three panes

<Steps>
  <Step title="Review your assets" icon="list-check">
    The left pane lists everything you selected. **Rename** each asset or **remove** it from the batch.

    Renaming here is worth the minute it takes, because Google Ads reporting shows you these names. A name carrying the hook and the text variant makes the report readable weeks later.
  </Step>

  <Step title="Choose the Google Ads account" icon="user">
    The middle pane selects which connected account the ads are created in.
  </Step>

  <Step title="Configure selected ads" icon="sitemap">
    The right pane is a checkbox tree of your account structure, with **Campaign (CA)** expanding into **Ad group (AG)**.

    Tick the ad groups that should receive the batch. Selecting several sends the same creative to each of them.
  </Step>
</Steps>

Each asset also has its own configuration panel for per-asset detail, reachable from its row.

## Working with the campaign tree

The tree mirrors your live Google Ads structure, so a tidy account makes this step quick. Two habits help:

* **Know the destination before you open the flow.** Deciding which ad group a test belongs to when you plan the test, rather than at upload time, keeps this to a few clicks.
* **Send a test batch to one ad group.** Keeping the creative in one place makes performance straightforward to attribute.

## After uploading

**Upload history** in the [Projects](/projects) sidebar logs every attempt, with the platform, a status of **Success** or `n/n failed`, timestamp and uploader.

**View details** shows the per-file message returned by Google. Reading it first tells you exactly what to adjust before you run the batch again.

## Meta and Google compared

|                       | Meta                                  | Google                         |
| --------------------- | ------------------------------------- | ------------------------------ |
| **Reusable settings** | Templates                             | Configured per batch           |
| **Destination**       | Campaign and ad set                   | Campaign and ad group tree     |
| **Paired connection** | Facebook page                         | YouTube account                |
| **Copy variants**     | Multiple primary texts, headline, CTA | Configured per asset           |
| **Bulk editing**      | Bulk edit on the settings table       | Selection applies to the batch |

If you publish to both platforms regularly, start with Meta. The template makes it the faster of the two, so the larger batch is on its way while you work through Google's tree.