Stay organized with collections
Save and categorize content based on your preferences.
A job containing offline user data of store visitors, or user list members that will be processed asynchronously. The uploaded data isn't readable and the processing results of the job can only be read using GoogleAdsService.Search/SearchStream.
Fields from the above resources may be selected along with this
resource in your SELECT and WHERE clauses. These fields will not segment
metrics in your SELECT clause.
Output only. Match rate of the Customer Match user list upload. Describes the estimated match rate when the status of the job is "RUNNING" and final match rate when the final match rate is available after the status of the job is "SUCCESS/FAILED".
Immutable. The resource name of the offline user data job. Offline user data job resource names have the form: customers/{customer_id}/offlineUserDataJobs/{offline_user_data_job_id}
This is the fraction of all transactions that are identifiable (for example, associated with any form of customer information). Required. The fraction needs to be between 0 and 1 (excluding 0).
Time the advertiser uploaded the data to the partner. Required. The format is "YYYY-MM-DD HH:MM:SS". Examples: "2018-03-05 09:15:00" or "2018-02-01 14:34:30"
The fraction of valid transactions that are matched to a third party assigned user ID on the partner side. Required. The fraction needs to be between 0 and 1 (excluding 0).
The fraction of transactions that are valid. Invalid transactions may include invalid formats or values. Required. The fraction needs to be between 0 and 1 (excluding 0).
This is the ratio of sales being uploaded compared to the overall sales that can be associated with a customer. Required. The fraction needs to be between 0 and 1 (excluding 0). For example, if you upload half the sales that you are able to associate with a customer, this would be 0.5.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-27 UTC."],[[["OfflineUserDataJob objects contain data about store visitors or user list members and are processed asynchronously."],["You can use the GoogleAdsService to search or stream the results of an OfflineUserDataJob."],["OfflineUserDataJob resources have a type that defines how the data is used (e.g., customer match, store sales upload)."],["You can select and filter data based on fields like resource name, status, and failure reason."],["OfflineUserDataJob metadata contains specific details depending on the job type, such as loyalty fraction or partner upload information for store sales."]]],["This document describes the structure of an offline user data job, which processes data from store visitors or user lists asynchronously. The job's data is unreadable, and its results are retrieved via GoogleAdsService.Search/SearchStream. Key attributes include: job ID, external ID, type, status, failure reason, and match rate. It supports data related to user lists and customer information and contains details on third party store sales such as loyalty, transaction fractions and version. Filters are supported on most attributes.\n"]]
