Loader Google Ads Customer Match Audience

Data In

The loader requires a CSV file in the directory /data/in/tables/import.csv

File structure:

first_name,last_name,country_code,postal_code,phone_number,email
John,Doe,US,10011,+1 234 5678910,test@meiro.io

If the list_upload_key_type is not defined or is set to CONTACT_INFO, you must provide at least one of the following identifiers:

• Email

• Phone_number

• Address identifier - if an address is provided, then all of its fields are required:

  • First_name
  • Last_name
  • Country_code
  • Postal_code

If the list_upload_key_type parameter is set to CRM_ID, then a field third_party_user_id is required.

If the list_upload_key_type parameter is set to MOBILE_ADVERTISING_ID, then the CSV file must contain a field mobile_id.

If there are any unknown columns, they will be ignored. An exception is raised if any of the following is true for: 

• the table schema (i.e., CSV file header);

• the data (i.e., values in a particular record): if there are no usable fields or an incomplete number of address identifier fields.

Learn more: about UserIdentifier.

Data Out

N/A

Developer token

(required)

A unique identifier assigned to an application by Google that grants access to the Google Ads API and controls the API usage limits and environment.

Learn more: about how to obtain a developer token

Customer ID

(required)

The Google Ads client account customer ID. Both 123-456-7890 and 1234567890 formats are accepted.

Learn more: about how to find your Google Ads customer ID

Manager account ID

(optional)

The ID of a Google Ads Manager account

List name (to create)

When creating a customer match list, this string is used as its name.
If the List ID is defined, then settings for List name are ignored. If the List ID is not defined, the List Name is a required field.

List ID (to update)

(optional)

Allows you to update an existing user list by uploading a CSV file to the same user list using a unique list ID, e.g., 7927172198. It's important to ensure that the list already exists and is of the same type as specified in the list upload key type. The user identifiers will be added to the list but the existing ones will not be removed.

In case the list ID parameter is not supplied, a new list is created with the specified List Name.

Warning: if you try to use a different "list upload key type" than those used when the list was created, it will throw an error.

List Membership Life Span

(optional)

The number of days a user's cookie stays on your list since its most recent addition to the list. This parameter can be set to any value between 0 and 540, and the default value is 30. However, for CRM-based user lists, this parameter can be set to 10000, which means no expiration.

Learn more: about mobile advertising IDs and list membership lifespan parameters here.

List upload key type

(optional)

The matching key type of the list. Mixed data types are not allowed on the same list. Possible values:

• CONTACT_INFO (default)

• CRM_ID

• MOBILE_ADVERTISING_ID (If you choose MOBILE_ADVERTISING_ID as the matching key type for the list upload, it is mandatory to specify the Mobile App ID parameter as well).

Remember: using this parameter limits the fields available for matching.

Learn more: about Customer Match Upload Key Type and List upload key type parameter.

Mobile App ID

(optional)

A string that uniquely identifies a mobile application from which the data was collected. 

Learn more: about Mobile App ID

Pre-hashed Email/Phone keys

(optional)

Check if the values of email/phone keys are already pre-hashed in the input CSV, otherwise, leave it unchecked.

Pre-hashed First/Last name keys
(optional)

Check if the values of first/last name keys are already pre-hashed in the input CSV, otherwise, leave it unchecked.