In order to query your data (along with any data you've linked from Google ad platforms), first you will have to import it into BigQuery. Your data must be keyed to an identifier that Ads Data Hub tracks. The following join keys are supported:
- Resettable device IDs (RDIDs) [not available for vendors]
- Custom Floodlight variables
- Cookies
- LiveRamp RampIDs (currently in beta)
Overview of available join keys
Use the following overview to learn more about the differences between the available join keys.
RDIDs
RDIDs are a unique identifier used exclusively for native apps on mobile devices. As such, RDID matching is ideal for advertisers whose data comes primarily from mobile apps, or deliver a large number of impressions on mobile. RDID matching requires the smallest investment in setup.
Learn more about Resettable device identifier matching.
Custom Floodlight variables
Custom Floodlight variables are URL parameters attached to Floodlight tags, which capture information during a conversion event. Because Floodlight tags are exclusive to Google Marketing Platform (GMP) properties, matching is limited to GMP IDs. Custom Floodlight variable matching requires a small investment in setup.
Learn more about Custom Floodlight variable matching.
Cookies
Important: Cookie matching is no longer supported as part of Ads Data Hub onboarding. Existing configurations that include cookie matching are still supported.
Cookie matching associates an advertiser’s cookies with Google’s. Cookie matching requires investment to set up, and requires a variable amount of time for the match tables to populate.
Key point: Users are only eligible for cookie matching if they've interacted with your domain and your ads.
Learn more about cookie matching.
LiveRamp RampIDs
Learn more about LiveRamp matching.
Setup
The specific implementation details differ between each matching option. Generally, you’ll need to:
- Upload your data to at least one dataset in BigQuery (for example,
YourData). You can also split your data across multiple BigQuery projects.
- Create another dataset for the output of joins that you make between Google data and your data (for example,
OutputData). - Give the service account Viewer permission for the dataset containing your uploaded data (for example,
YourData). If your data is split across multiple datasets, the service account will need Viewer permission for all of them.
The service account also requires Editor permission for the dataset containing your data join outputs (for example,.OutputData). The name of your service account can be found in your Ads Data Hub account settings.