# Patronage Ads Sync Docs

> Public developer and operator documentation for Patronage Ads Sync.

## Start

- [Ads Sync developer documentation](https://adsync.patronage.com/): Configure, verify, and understand the Patronage Ads Sync public contract.
- [Quickstart](https://adsync.patronage.com/tutorial/quickstart): Deploy the Ads Sync Reference Deployment to your own Cloudflare account and Postgres, and complete one scheduled Qualified Run in under an hour.
- [Configure your first sync](https://adsync.patronage.com/tutorial/configure-your-first-sync): Build and validate isolated Google Ads and Meta Ads connection definitions.

## Operate

- [Verify a bounded run](https://adsync.patronage.com/how-to/verify-a-bounded-run): Prepare canary evidence, review backfill bounds, and compare stable history.
- [Admit a provider](https://adsync.patronage.com/how-to/admit-a-provider): Run the executable provider admission command that verifies a Supported Provider end to end against your deployment and its built image.
- [Ejection Path](https://adsync.patronage.com/how-to/eject-from-loop): How a Loop tenant resumes its Ads Sync connections single-tenant on the open-source core, with re-enrollment of credentials and state.

## Reference

- [Public contract reference](https://adsync.patronage.com/reference/public-contract): Every public export of every @patronage/ads-sync entry point, with written contracts for the load-bearing functions.
- [Connector image HTTP contract](https://adsync.patronage.com/reference/connector-image-http-contract): Exact HTTP surface of the Ads Sync connector images, the metadata verification consumers must do, and the build inputs that produce the images.

## Understand

- [Architecture and boundaries](https://adsync.patronage.com/explanation/architecture-and-boundaries): Why Ads Sync separates public contracts, reference deployment, and private dogfood operations.
- [Google Search Console caveats](https://adsync.patronage.com/explanation/google-search-console-caveats): What to expect from Google OAuth Testing mode, the seam's cold-start retry, final versus provisional data, and the two auth modes of the Search Console image.