Issues with Importing GA4 Data into Search for Retail

[PavelKosan]

Hello Google Cloud Community,

I am encountering an issue while trying to import GA4 data (historical user events) from BigQuery into Search for Retail. Despite following the setup and ensuring all necessary permissions and configurations are correct according to the documentation, I receive the following error:

404 tenant_project_info_id 'default_tp_info' not found for project 'my project number'

I successfully imported the product catalog and set up real-time user events recording, but I cannot proceed with importing the historical user events.

I appreciate any guidance or suggestions to resolve this issue.

Thank you,
Pavel Kosan

[dawnberdan]

Hi @PavelKosan,

Welcome to Google Cloud Community!

The error message "404 tenant\_project\_info\_id 'default\_tp\_info" not found for project 'my project number suggests that Search for Retail is unable to locate the project information required to access your BigQuery data.

To ensure successful data connectivity, verify that the Google Cloud project ID you're using for your GA4 property and Search for Retail configuration are identical. Cross-check that the project number in the Search for Retail configuration matches your actual Google Cloud project ID - a typo or mismatch can lead to lookup failures. Refer to the Search for Retail documentation for importing GA4 data. Another important step is to ensure that your Search for Retail instance and BigQuery dataset reside in the same region, as cross-regional data access may not be supported by Search for Retail.

As an alternative solution, consider refreshing the connection between Search for Retail and BigQuery within the console. This action has been known to resolve temporary glitches in some cases.

Since you cannot proceed with importing user events, it seems we do not directly support user events with event_name == "search". Such user events are omitted as a result. Instead, we support GA4 events with the name "view_item_list", and convert them into search events. You can refer to this image below or to this link.

I hope the above information is helpful.

[Snoshone07]

Hi @PavelKosan the error "404 tenant_project_info_id 'default_tp_info' not found for project 'my project number'" suggests that the tenant project information needed for the import is either missing or incorrectly configured. Here are some steps to help you resolve this issue:

1. Verify the Tenant Project Setup

• Ensure that your Google Cloud project is properly linked to the correct tenant project for Search for Retail. Double-check that the tenant_project_info_id is accurately configured in your project settings.
• If another team handled the setup process for Search for Retail, confirm with them that the appropriate tenant project was provisioned for your use case.

2. Check Permissions

• Make sure the service account being used to import historical user events has all the required permissions. This includes access to both the BigQuery dataset and the Search for Retail configuration.
• Missing permissions can often lead to errors when connecting systems, so it’s important to confirm that everything is correctly granted.

3. Confirm Dataset and Schema Compatibility

• Review the schema of your historical user event data in BigQuery. Ensure it matches the expected structure for Search for Retail. Any differences in field names or data types could cause import errors.
• Additionally, verify that the BigQuery dataset is either in the same project or that it has proper permissions for cross-project access.

4. Reach Out to Google Cloud Support

• If none of the above steps solve the issue, consider contacting Google Cloud Support. They can help confirm whether the tenant project is set up correctly and assist with troubleshooting historical user event imports.

5. Consider an Alternative Approach

• If you’re looking for a more flexible way to manage and integrate your GA4 data, tools like Windsor.ai might be worth exploring. They simplify the process of transferring and transforming GA4 data into various destinations, including BigQuery. While this won’t directly address the 404 tenant_project_info_id error, it can offer a reliable alternative for managing your data workflows.