[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-17。"],[[["\u003cp\u003eThis document provides guidance for both end users and identity providers on configuring and utilizing entity resolution within BigQuery.\u003c/p\u003e\n"],["\u003cp\u003eEnd users must first establish a relationship with an identity provider, such as LiveRamp, and obtain necessary credentials and a remote function signature to begin the entity resolution process.\u003c/p\u003e\n"],["\u003cp\u003eEnd users are required to set up an input and output dataset in their project, grant specific IAM roles for data access, and then work with the identity provider to initiate a resolution job.\u003c/p\u003e\n"],["\u003cp\u003eIdentity providers must create a Cloud Run job or function, set up a remote function, collect end-user principals, and establish the necessary permissions for their service account and end users to operate.\u003c/p\u003e\n"],["\u003cp\u003eIdentity providers can optionally share metadata and are recommended to integrate with the Google Cloud Marketplace to handle billing and customer onboarding.\u003c/p\u003e\n"]]],[],null,["# Configure and use entity resolution in BigQuery\n===============================================\n\nThis document shows how to implement\n[entity resolution](/bigquery/docs/entity-resolution-intro)\nfor entity resolution end users (hereafter referred to as *end users*) and\nidentity providers.\n\nEnd users can use this document to connect with an identity provider and use the\nprovider's service to match records. Identity providers can use this document to\nset up and configure services to share with end users on the\nGoogle Cloud Marketplace.\n\nWorkflow for end users\n----------------------\n\nThe following sections show end users how to configure entity resolution in\nBigQuery. For a visual representation of the complete setup, see\nthe\n[architecture for entity resolution](/bigquery/docs/entity-resolution-intro#architecture).\n\n### Before you begin\n\n1. Contact and establish a relationship with an identity provider. BigQuery supports entity resolution with [LiveRamp](mailto:LiveRampIdentitySupport@liveramp.com).\n2. Acquire the following items from the identity provider:\n - Service account credentials\n - Remote function signature\n3. Create two datasets in your project:\n - Input dataset\n - Output dataset\n\n### Required roles\n\n\nTo get the permissions that\nyou need to run entity resolution jobs,\n\nask your administrator to grant you the\nfollowing IAM roles:\n\n- For the identity provider's service account to read the input dataset and write to the output dataset:\n - [BigQuery Data Viewer](/iam/docs/roles-permissions/bigquery#bigquery.dataViewer) (`roles/bigquery.dataViewer`) on the input dataset\n - [BigQuery Data Editor](/iam/docs/roles-permissions/bigquery#bigquery.dataEditor) (`roles/bigquery.dataEditor`) on the output dataset\n\n\nFor more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\nYou might also be able to get\nthe required permissions through [custom\nroles](/iam/docs/creating-custom-roles) or other [predefined\nroles](/iam/docs/roles-overview#predefined).\n\n### Translate or resolve entities\n\nFor specific identity provider instructions, refer to the following sections. \n\n### LiveRamp\n\n#### Prerequisites\n\n- Configure LiveRamp Embedded Identity in BigQuery. For more information, see [Enabling LiveRamp Embedded Identity in BigQuery](https://docs.liveramp.com/identity/en/liveramp-embedded-identity-in-bigquery.html#enabling-liveramp-embedded-identity-in-bigquery).\n- Coordinate with LiveRamp to enable API credentials for use with Embedded Identity. For more information, see [Authentication](https://docs.liveramp.com/identity/en/liveramp-embedded-identity-in-bigquery.html#idm45591476327824).\n\n#### Setup\n\nThe following steps are required when you use LiveRamp Embedded Identity for the\nfirst time. After setup is complete, only the input table and metadata table\nneed to be modified between runs.\n\n##### Create an input table\n\nCreate a table in the input dataset. Populate the table with RampIDs, target\ndomains, and target types. For details and examples, see\n[Input Table Columns and Descriptions](https://docs.liveramp.com/identity/en/perform-rampid-transcoding-in-bigquery.html#input-table-columns-and-descriptions-50).\n\n##### Create a metadata table\n\nThe metadata table is used to control the execution of LiveRamp Embedded\nIdentity on BigQuery. Create a metadata table in the input dataset.\nPopulate the metadata table with client IDs, execution modes, target\ndomains, and target types. For details and examples, see\n[Metadata Table Columns and Descriptions](https://docs.liveramp.com/identity/en/perform-rampid-transcoding-in-bigquery.html#metadata-table-columns-and-descriptions-50).\n\n##### Share tables with LiveRamp\n\nGrant the LiveRamp Google Cloud service account access to view and\nprocess data in your input dataset. For details and examples, see\n[Share Tables and Datasets with LiveRamp](https://docs.liveramp.com/identity/en/perform-rampid-transcoding-in-bigquery.html#share-tables-and-datasets-with-liveramp).\n\n#### Run an embedded identity job\n\nTo run an embedded identity job with LiveRamp in BigQuery, do the\nfollowing:\n\n1. Confirm that all RampIDs that were encoded in your domain are in your input table.\n2. Confirm that your metadata table is still accurate before you run the job.\n3. Contact [LiveRampIdentitySupport@liveramp.com](mailto:LiveRampIdentitySupport@liveramp.com) with a job process request. Include the project ID, dataset ID, and table ID (if applicable) for your input table, metadata table, and output dataset. For more information, see [Notify LiveRamp to Initiate Transcoding](https://docs.liveramp.com/identity/en/perform-rampid-transcoding-in-bigquery.html#notify-liveramp-to-initiate-transcoding).\n\nResults are generally delivered to your output dataset within three business days.\n\n#### LiveRamp support\n\nFor support issues, contact\n[LiveRamp Identity Support](mailto:LiveRampIdentitySupport@liveramp.com).\n\n#### LiveRamp billing\n\n[LiveRamp](/find-a-partner/partner/liveramp) handles billing for entity\nresolution.\n\nWorkflow for identity providers\n-------------------------------\n\nThe following sections show identity providers how to configure entity\nresolution in BigQuery. For a visual representation of the\ncomplete setup, see the\n[architecture for entity resolution](/bigquery/docs/entity-resolution-intro#architecture).\n\n### Before you begin\n\n1. Create a [Cloud Run](/run/docs/overview/what-is-cloud-run) job or a [Cloud Run function](/functions/docs/concepts/overview#functions) to integrate with the remote function. Both options are suitable for this purpose.\n2. Note the name of the service account that's associated with the\n Cloud Run or Cloud Run function:\n\n 1. In the Google Cloud console, go to the **Cloud Functions** page.\n\n [Go to Cloud Functions](https://console.cloud.google.com/functions)\n 2. Click the function's name, and then click the **Details** tab.\n\n 3. In the **General Information** pane, find and note the service\n account name for the remote function.\n\n3. Create a\n [remote function](/bigquery/docs/remote-functions#create_a_remote_function).\n\n4. Collect end-user principals from the end user.\n\n### Required roles\n\n\nTo get the permissions that\nyou need to run entity resolution jobs,\n\nask your administrator to grant you the\nfollowing IAM roles:\n\n- For the service account that's associated with your function to read and write on associated datasets and launch jobs:\n - [BigQuery Data Editor](/iam/docs/roles-permissions/bigquery#bigquery.dataEditor) (`roles/bigquery.dataEditor`) on the project\n - [BigQuery Job User](/iam/docs/roles-permissions/bigquery#bigquery.jobUser) (`roles/bigquery.jobUser`) on the project\n- For the end-user principal to see and connect to the remote function:\n - [BigQuery Connection User](/iam/docs/roles-permissions/bigquery#bigquery.connectionUser) (`roles/bigquery.connectionUser`) on the connection\n - [BigQuery Data Viewer](/iam/docs/roles-permissions/bigquery#bigquery.dataViewer) (`roles/bigquery.dataViewer`) on the control plane dataset with the remote function\n\n\nFor more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\nYou might also be able to get\nthe required permissions through [custom\nroles](/iam/docs/creating-custom-roles) or other [predefined\nroles](/iam/docs/roles-overview#predefined).\n\n### Share entity resolution remote function\n\nModify and share the following remote interface code with the end user. The end\nuser needs this code to start the entity resolution job. \n\n `PARTNER_PROJECT_ID.DATASET_ID`.match`(\u003cvar translate=\"no\"\u003eLIST_OF_PARAMETERS\u003c/var\u003e)\n\nReplace \u003cvar translate=\"no\"\u003eLIST_OF_PARAMETERS\u003c/var\u003e with the list of parameters that are\npassed to the remote function.\n\n### Optional: Provide job metadata\n\nYou can optionally provide job metadata by using a separate remote function\nor by writing a new status table in the user's output dataset. Examples of\nmetadata include job statuses and metrics.\n\nBilling for identity providers\n------------------------------\n\nTo streamline customer billing and onboarding, we recommend that you integrate\nyour entity resolution service with the\n[Google Cloud Marketplace](/marketplace).\nThis lets you set up a\n[pricing model](/marketplace/docs/partners/integrated-saas/select-pricing)\nbased on the entity resolution job usage, with Google handling the billing for\nyou. For more information, see\n[Offering software as a service (SaaS) products](/marketplace/docs/partners/integrated-saas)."]]