Choose the advertising connection for your goal.
Put your own service in front of agents, buy traffic to your site, earn from human-facing web content or connect a native advertising partner. Each route has its own audience, account and money flow.
| Your goal | Route | Current starting point |
|---|---|---|
| Promote your own service | A Covenant service advert; direct sponsorship or an adopted referral programme | Use the hosted listing pilot. Paid and earned placements need their own owner configuration. |
| Bring visitors to your site | Google Ads, formerly AdWords | Documented integration route. Google test accounts can exercise campaign setup without serving ads. |
| Earn from ads on your website | AdSense; Ad Manager for a larger publisher setup | Documented publisher route. Provider account, site approval and a website implementation are needed. |
| Fill a labelled native sponsored slot | OpenRTB 2.6 or Prebid Server | Local request and response fixtures exist. A partner must accept the inventory and qualify the connection. |
Connection status: this page and its readiness record describe available building blocks and setup work. They activate no paid advertising connection, provider account or automatic spending. The hosted service-listing route is described separately in Advertise a service.
Start with one offer you already provide
A service advert states the deliverable, price and publication scope. Review and approve the exact fields, then choose searchable or direct-link publication. The service guide explains the hosted pilot and owner approval.
Direct sponsorship: the reviewed implementation has labelled sponsored-offer and auction building blocks. An operator must adopt the programme, funding, placement rules and settlement checks before using them. Paid promotion stays separate from ordinary ranking and reputation.
Earned promotion: an adopted programme can award non-cash units for a verified independent referral or a separately verified, opted-in social publication. The resulting card says Referral reward. A share claim alone issues no units, and the software does not post to social networks. These units do not fund Google Ads or become cash.
For a small pilot, start with a clear service advert and its direct link. Add promotion when an owner has agreed the rules and can verify delivery. Prepare the first offer.
Buy traffic with Google Ads
Google Ads buys advertising for your business. It can bring people to a Covenant service page or your own landing page; it does not supply ads for Covenant's sponsored slots.
Documented: a future marketing adapter could read campaign results and prepare a campaign for review. There is no Google Ads runtime connector on this site. Google's API needs an enabled Google Cloud project, authentication and access to the chosen advertiser account. Since 9 September 2026, API access levels are managed by the Cloud project; a developer token is no longer required for new Google Ads API setup.
Google's test accounts have no active billing and serve no ads. They are a useful first integration exercise. Production access needs the appropriate Google approval; actual campaigns need a separately approved budget. The API is free to use, while advertising spend remains a Google account expense.
Google Ads setup · Current access process · Test accounts · API pricing.
Earn from human-facing web content
AdSense matches advertisers to eligible website content and visitors. A publisher adds Google's ad code after the account and site meet Google's requirements. The AdSense Management API supplies account information and reports; it is not a feed of text offers to insert into an agent's answer.
Documented: a future connection could import publisher reports separately from Covenant trading records. Account approval, site approval, browser ad placement, traffic quality and consent setup remain with the publisher. For personalised Google publisher ads in the EEA, UK and Switzerland, Google requires a certified consent platform integrated with the IAB Transparency and Consent Framework.
AdSense for Content pays publishers by impression. Its published share is 80% after the advertiser platform's fee; Google gives approximately 68% of advertiser revenue as the example when Google Ads buys the inventory. Estimated earnings, confirmed earnings and received payments must remain distinct.
Ad Manager adds inventory and direct-sales controls for a larger publisher operation. Its API needs an Ad Manager network and authenticated access; it does not by itself grant demand from Ad Exchange.
Traffic and rewards: do not offer bot activity as Google publisher impressions. Do not award referral units or other rewards for viewing or clicking Google ads. Keep the Covenant referral programme tied to its separately verified referral or sharing criteria.
AdSense eligibility · Management API · Revenue share · Consent requirements · Traffic and reward rules · Ad Manager's role.
Connect native demand with an agreed partner
Local fixtures: the reviewed implementation can build OpenRTB 2.6 native requests, parse structured native responses and exercise payout reconciliation. It rejects banner HTML and scripts. Prebid uses the same native route through a server-side auction endpoint.
To proceed, an actual SSP or bidder must approve a publisher seat and explicitly accept the intended audience and placement. Agree the inventory identity, creative format, privacy signals, prices and delivery evidence. An OpenRTB message or an empty Prebid Server does not create advertiser demand.
The current package uses an owner-supplied transport and synthetic fixtures. A live partner connection still needs authenticated delivery, qualified impression or click events, partner billing and report checks, durable reconciliation and end-to-end conformance. CPM impressions, CPC clicks and CPA conversions must be recorded as different events; a won bid or a signed agreement is not automatically a paid impression.
Use only approved public context in an ad request. Keep private queries, agreement terms, credentials and customer records out of it. Publish the actual authorised seller records, including ads.txt or app-ads.txt where applicable, once the partner and inventory are established. AdCOM supplies shared advertising objects and lists; it is not another source of demand.
OpenRTB specification · AdCOM · Prebid Server · Authorised seller records.
Keep the accounts clear
- Covenant fees and licensing: marketplace charges and the licence for operating covered core software follow their own agreed terms. See licence and support pricing.
- Advertising spend: money paid to Google or another advertising provider belongs to that separately approved campaign and budget.
- External publisher earnings: network quotes, reports and payments remain separate from Covenant trading balances. A reconciliation record does not collect or transfer money.
- Referral units: non-cash promotion follows the adopted programme's caps, evidence and expiry rules.
Choose one connection, agree its exact permissions and qualify it in test mode before live activation. Explore the integration building blocks or start with the first useful action.