關於​ Google Ads API​ ​中​的​網站​強化​轉換

Enhanced conversions for web​ is a feature that can improve the accuracy of ​your conversion measurement. It supplements your existing conversion data by sending hashed first​-party customer data in a privacy-safe way​. The hashed customer data ​已​雜湊​資料會​將​原始字串​對​應到​固定​長度​的​資料。​ ​瞭解​詳情​ ​ is compared to hashed customer data of signed​-​in Google accounts and attributed to ad events such as clicks and video views​ ​to help measure your campaign conversions.

This article will explain how ​to set up enhanced conversions using the Google Ads API.

Benefits

• First​-party data can be provided after the conversion event: Unlike other enhanced conversions options like tagging that require you ​to send first​-party data at the time of the conversion, you can use the API to send hashed first​-party data up to 24 hours after the conversion event. This also enables you ​to locate first​-party data from other sources, such a customer database or CRM system.
• More choices for ​your data source: Using the API enables you ​to locate first​-party data from a variety of sources, such as a customer database or CRM system.

How it works

Using the Google Ads API, you can leverage enhanced conversions by sending first​-party customer data in the form​ of ​conversion adjustments. The process for sending enhanced conversion data is similar to other conversion adjustments wit​h some key differences. Learn how ​to implement enhanced conversions for we​b​ using Google Ads API conversion adjustments.

In order to implement enhanced conversions using the Google Ads API, you must record conversions using a regular conversion tracking tag on your website. After a conversion is recorded, you can then send hashed first​-party data ​(such as email address, phone number, name, and/or ​home address)​ via an API connection up until 24 hours after the conversion.

The hashed data you send us is matched against Google logged​-​in user data and a conversion is reported in your account.

Before you begin

• Make sure you’ve Set up conversion tracking for ​your website.

• Know ​t​he conversion page URL where the conversion tag fires ​(such as the confirmation page URL)​ and the conversion event trigger ​(for example, a button click or a page view)​.
• Make sure that there is first​-party customer data available ​(email, full name and home address and/or phone number)​.
• Make sure that you’ve reviewe​d​ the Customer data policies and agreed to the Terms of Service and policies in Google Ads ​(refer to steps on this below,​ ​under Instructions)​.

Instructions

Set up enhanced conversions wit​h the Google Ads API
​Follow ​t​he instructions in Google Ads developer documentation for enhanced conversions.

1. In your Google Ads account, click the Goals icon .
2. Click the ​Conversions drop​-​down​ in the section menu.
3. Click Settings.
4. Expand the ‘Enhanced conversions for we​b​’ panel.
5. Check ‘Turn on enhanced conversions for we​b​’.
6. Review ​compliance statement. To enable enhanced conversions, you must confirm that you’ll comply wit​h our policies and that the Google Ads Data Processing Terms apply to your use of enhanced conversions. Click Agree to acknowle​dge your acceptance of these terms.
7. Click the dropdown​ to choose a method for setting up and managing user​-provided data. Select ‘Google Ads API’.

8. Make sure you’ve set up a conversion tracking tag on your website and that you’re Using the transaction ID function tag so Google is able to match your tag conversions wit​h your API conversions to avoid duplication.
9. Set up a server in your internal system that’s capable of sending the data ​(first​-party customer data, conversion data and click identifier data)​ using an HTTPS connection, the industry standard for secure data transmission.
10. Use the Google Ads API to send conversion data to Google. You’ll need to format the data into a standard format and then hash it using SHA​-​256 before sending it to Google. Learn more about how ​to format and send enhanced conversions for we​b​ data to Google via the API.

11. After sending data to Google, review ​t​he responses your server receives to ensure there are no errors.