Google Ads Data Manager API

Renta sends rows from your data warehouse to Google Ads through the Data Manager API as one of two objects: Customer Match audiences and click conversions.

A Customer Match row carries the identifiers Google matches people by, such as email, phone number, and postal address. A click conversion row carries the click that led to the sale, the moment it happened, and its value.

Authentication

Renta authenticates with Google OAuth. Authorize the Google account that already has access to the Google Ads account you want to write into.

On the consent screen Google asks for two permissions: access to your Google Ads accounts and data, and access to your customer data in Google Ads and the Google Marketing Platform. Renta uses them to list the accounts you can reach, to read your Customer Match lists and conversion actions, and to write the rows a pipeline delivers.

Create a pipeline

Once the destination is connected, create a pipeline to send a data model to Google Ads.

Pipeline configuration

On the final step, choose what Renta writes to Google Ads, where it lands, and which columns fill it.

What Renta sends

Pick the Google Ads object and the data model behind it. The settings below the choice differ per object, so make this choice first.

Then pick the Data model. The columns available for matching and mapping below come from this model.

Google Ads account

Tell Renta which account the data lands in.

1. Login account.
   The account Renta connects through, out of everything the authorized Google user can reach.
2. Google Ads account.
   The account the audience or the conversions land in. When the login account is a manager (MCC), this list holds the accounts it manages. When it is an ordinary account, both dropdowns name the same account.

Audience and consent

A Customer Match pipeline writes into a user list, and Google needs to know how the people in it consented.

1. Audience mode Choose where the members go.

   Mode	Description
   Use existing user list	Writes into a Customer Match list that already exists in the account. Renta keeps it up to date and never touches lists other pipelines own.
   Create new user list	Renta creates a Customer Match list when the pipeline is created and writes into it from then on. Name it yourself, or leave the field empty to reuse the pipeline name.

2. Existing user list For the existing mode, pick the list this pipeline keeps up to date. The dropdown holds the Customer Match lists Google Ads reports for the selected account.

3. Consent status Declare whether the people in the model consented to their data being used for ads and for personalization.

   Value	Description
   Granted	The person agreed to this data use.
   Denied	The person refused, and Google restricts how the data is used.
   Unspecified	The consent state is unknown, so Google falls back to the account settings.

Record matching

Tell Renta which column identifies a person, so the same warehouse row updates the same Google Ads member instead of adding a second one.

The left dropdown offers the unique key of the data model, and the right one offers the Google Ads identifier holding the same value. Renta sends the matched value with every row, so you do not need to repeat it in the mapping block below.

Field mapping

Connect the columns of your data model to Google Ads fields. The list on the right depends on the object you chose.

A Customer Match user list pipeline offers the identifier fields Google matches people by.

A Click conversions pipeline offers the fields that describe the conversion itself.

Renta hashes email, phone number, and name parts with SHA-256 before the request leaves, so the raw values never reach Google. Region code and postal code are sent as written, because Google matches on them directly. A value that already arrives hashed is passed through untouched.

Sync behavior

Set what happens to a Google Ads record whose row disappears from the data model.

Then name the pipeline.

Integration name is the name of your pipeline. Edit it to match your preferences.

Schedule

Choose how often the pipeline runs.

For Daily schedules, set the Update time (the exact time each run starts), then click Create pipeline.

The new pipeline appears in the Pipelines section under the Reverse ETL tab, where you can track its runs and progress.

Sync strategy

Renta syncs incrementally. A run compares the data model against the state the previous run recorded and sends only what moved, which keeps an audience current without re-uploading it every night. The first run has nothing to compare against, so it delivers the model in full.

Limits

1. Matching is Google's, not Renta's.
   Renta reports a row as delivered once Google accepts it. Whether it then matches a real Google user, and how long an audience takes to become targetable, is decided inside Google Ads. Audience size stays hidden until the list holds enough matched members.
2. Conversions cannot be withdrawn.
   Google treats an accepted conversion as final, so a conversion pipeline only ever adds. Removing a row from the model does not remove the conversion.
3. A run stops when rejections pile up.
   Renta halts the run when more than 30% of a batch, or more than 10% of the rows delivered so far, come back rejected. Rows already delivered stay in Google Ads, and the next run picks up where this one stopped.
4. Consent is set per pipeline.
   Both consent fields apply to every row of the sync. Different consent states need different pipelines.