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

# Connect GA4, TikTok, or Google conversion delivery

> Supply the correct provider fields and distinguish debug validation from recorded production events.

Open **Websites → \[your site] → Destinations** to deliver eligible browser actions to another measurement tool. A website owner or editor can manage these settings; viewers can read them. Install and [verify website events](/websites/install) first, and grant both analytics and marketing consent for the actions being forwarded.

## Supply the provider fields

| Destination | What you need |
| - | - |
| **Google Analytics 4** | The property's **Measurement ID** and a Measurement Protocol **API secret**. |
| **TikTok Events API** | The intended **Pixel code**, an **Access token**, and a **Test Event Code** for isolated testing. |
| **Google Ads conversions** | A connected Google account with Data Manager access, **Conversion action ID**, **Operating Google Ads customer ID**, **Currency**, and a **Manager login customer ID** if needed. The action must belong to the operating customer. |

Choose the provider's **Connect** action, check these values, and choose **Save in test mode**. For Google, use **Reconnect Google Ads with Data Manager access** when the form requires renewed access. Keep provider secrets out of browser code and support messages.

## Test the exact configuration

1. Use a page with the website script set to the Test environment.
2. Grant analytics and marketing consent, then perform one mapped action. Google also requires an actual Google click identifier.
3. Choose **Check test delivery**. It processes eligible events already collected; it does not create a visit or conversion for you.
4. Read the returned result using the provider-specific meaning below.

**GA4:** debug validation checks the event and configuration; the validation event never enters reports. **Google Ads:** validation creates no conversion, so a new recorded conversion is not the expected test result. **TikTok:** verify the accepted isolated test event using the supplied Test Event Code and provider test view.

Once the exact configuration has a successful test, **Enable live delivery** becomes available. Confirm the Production environment and monitor real production outcomes separately. Test events do not later become live events.

## Read a failure honestly

Check consent, environment, mapping, IDs, permissions, and any required click identifier. **Queued**, **Accepted**, **Awaiting Google**, **Delivered**, **Partial**, and **Failed** represent different outcomes; inspect the provider-specific state rather than calling every accepted request a recorded conversion. Changing the configuration requires another successful test. **Pause delivery** stops forwarding and is separate from pausing website collection.

For Meta's Pixel-specific test, use [Test event delivery](/websites/destinations).

<Note>Google Ads live forwarding can remain unavailable after validation or saving Live mode. If the status says live delivery is awaiting availability, contact [support](/help/contact) and confirm it is enabled before relying on conversion delivery. A validation success does not establish that production conversions were sent.</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.