Laporan tentang Variabel Floodlight Kustom
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Search Ads 360 Reporting API versi baru kini tersedia. API baru menyediakan
meningkatkan fleksibilitas dalam membuat laporan kustom dan mengintegrasikan data ke dalam aplikasi pelaporan
dan proses. Pelajari lebih lanjut cara bermigrasi ke dan menggunakan
Pelaporan Search Ads 360 versi baru
Google Cloud Platform.
Pengiklan menggunakan variabel Floodlight kustom untuk melaporkan data konversi yang
unik untuk kebutuhan bisnis mereka, seperti genre film yang dibeli pengguna,
toko tempat item dibeli, biaya pengiriman, dan sebagainya. Data tersebut dapat diupload
dengan tag Floodlight di situs pengiklan atau
oleh Search Ads 360 API,
dan Anda dapat menggunakan API untuk mendownload laporan yang berisi data.
Pelajari lebih lanjut Floodlight kustom
variabel di Search Ads 360.
Metrik atau dimensi
Sebagai bagian dari penyiapan variabel Floodlight kustom, pengiklan menggunakan Search Ads 360
UI untuk menunjukkan cara penggunaan setiap variabel dalam laporan:
Metrik: Di sebagian besar laporan, Search Ads 360 menggabungkan nilai
variabel yang ditentukan
sebagai metrik.
Misalnya, pengiklan menggunakan variabel Floodlight kustom untuk melacak biaya pengiriman.
Jika pengguna Search Ads 360 menentukan variabel ini sebagai metrik dan Anda menyertakan variabel tersebut
dalam laporan adGroup,
Anda akan melihat total biaya pengiriman yang dikaitkan dengan setiap grup iklan dalam cakupan laporan.
Di conversion
Search Ads 360 akan memberikan data mentah tentang konversi individual, bukan data gabungan.
Catatan: Metrik kustom juga dapat muncul di
Kolom pelaporan Floodlight. Di kolom
UI Search Ads 360, pengguna menambahkan metrik kustom ke kolom pelaporan Floodlight, lalu menyertakan
kolom pelaporan Floodlight dalam laporan. Anda juga dapat menyertakan kolom Floodlight ini
dalam permintaan laporan, sama seperti
yang dapat Anda sertakan jenis
kolom tersimpan.
Dimensi: Variabel yang ditetapkan sebagai dimensi dapat digunakan untuk menyegmentasikan
sebagian besar laporan.
Misalnya, pengiklan menggunakan variabel Floodlight kustom untuk melacak nama toko. Sesudah
Pengguna Search Ads 360 menentukan variabel ini sebagai dimensi, Anda dapat menggunakannya untuk mengelompokkan
adGroup dan
melihat jumlah pembelian dari setiap toko yang diatribusikan ke iklan dalam grup iklan.
Di conversion
laporan, Search Ads 360 akan memberikan data mentah tentang masing-masing konversi,
dan data teragregasi. Jadi, jika Anda menambahkan dimensi kustom ke laporan conversion,
Anda akan melihat nilai dimensi. Melanjutkan contoh dari paragraf sebelumnya, jika Anda
menyegmentasikan laporan conversion menurut dimensi kustom storeName, Anda akan melihat
nama toko tempat
pembelian spesifik terjadi.
Catatan: Saat pengguna Search Ads 360 menentukan
Kolom pelaporan Floodlight, kolom tersebut
dapat menggunakan dimensi kustom sebagai filter sehingga kolom hanya melaporkan konversi yang
mencatat nilai dimensi tertentu.
Menyertakan metrik kustom dalam permintaan laporan
Untuk menyertakan metrik kustom dalam permintaan laporan:
Kemudian, dalam permintaan laporan, sertakan:
Misalnya, jika pengiklan membuat metrik kustom bernama shippingCost,
sertakan shippingCost customMetricName dalam laporan:
{
"reportScope": {
"agencyId": "12300000000000456", // Replace with your ID
"advertiserId": "21700000000011523", // Replace with your ID
},
...
"columns": [
{
"customMetricName": "shippingCost",
"platformSource": "floodlight"
}
],
...
}
Menyegmentasikan laporan menurut dimensi kustom
Untuk menyegmentasikan laporan menurut dimensi kustom:
Anda harus tahu nama ramah yang
ditentukan saat konfigurasi
Variabel Floodlight dibuat di Campaign Manager.
Nama yang mudah dikenali juga muncul di UI Search Ads 360 saat menyiapkan
dimensi dan metrik kustom.
Cakupan laporan harus merupakan pengiklan tertentu
atau lebih rendah.
-
Setiap permintaan laporan hanya dapat menentukan satu dimensi kustom. Tapi
dapat mencakup
segmen non-kustom lainnya.
Misalnya, Anda dapat menyegmentasikan laporan menurut dimensi kustom storeName dan
berdasarkan kuartal dan segmen non-kustom perangkat. Ketahuilah bahwa
jumlah baris bisa
meningkat secara eksponensial untuk setiap segmen tambahan.
Kemudian, dalam permintaan laporan, sertakan:
Misalnya, jika pengiklan membuat dimensi kustom bernama storeName,
sertakan storeName customDimensionName dalam laporan untuk menyegmentasikan metrik menurut nama toko:
{
"reportScope": {
"agencyId": "20700000000000123", // Replace with your IDs
"advertiserId": "2170000012345" // Replace with your IDs
},
"reportType": "campaign",
"columns": [
{ "columnName": "campaignId" },
{ "columnName": "clicks" },
{ "columnName": "cost" },
{ "columnName": "dfaRevenue"},
{
"customDimensionName": "storeName",
"platformSource": "floodlight"
}
],
...
}
Kecuali dinyatakan lain, konten di halaman ini dilisensikan berdasarkan Lisensi Creative Commons Attribution 4.0, sedangkan contoh kode dilisensikan berdasarkan Lisensi Apache 2.0. Untuk mengetahui informasi selengkapnya, lihat Kebijakan Situs Google Developers. Java adalah merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2024-08-20 UTC.
[null,null,["Terakhir diperbarui pada 2024-08-20 UTC."],[[["\u003cp\u003eThe new Search Ads 360 Reporting API offers increased flexibility for creating custom reports and integrating data.\u003c/p\u003e\n"],["\u003cp\u003eCustom Floodlight variables allow advertisers to report unique conversion data like product details or shipping costs.\u003c/p\u003e\n"],["\u003cp\u003eCustom Floodlight variables can be defined as metrics (aggregated values) or dimensions (report segmentation).\u003c/p\u003e\n"],["\u003cp\u003eTo include custom metrics in reports, use the \u003ccode\u003ecustomMetricName\u003c/code\u003e and \u003ccode\u003eplatformSource: floodlight\u003c/code\u003e in your request.\u003c/p\u003e\n"],["\u003cp\u003eTo segment reports by a custom dimension, use the \u003ccode\u003ecustomDimensionName\u003c/code\u003e and \u003ccode\u003eplatformSource: floodlight\u003c/code\u003e while limiting to one custom dimension per request.\u003c/p\u003e\n"]]],["The new Search Ads 360 Reporting API allows building custom reports and integrating data into reporting applications. Advertisers can use custom Floodlight variables for unique conversion data. These variables can be defined as metrics (aggregated data) or dimensions (segmentation). To include custom metrics, specify the friendly name and set the platform source to \"floodlight\" in the report request. Similarly, segmenting by a custom dimension requires specifying its friendly name and \"floodlight\" as the platform source. Only one custom dimension is allowed per report request.\n"],null,["# Report on Custom Floodlight Variables\n\nThe new Search Ads 360 Reporting API is now available. The new API provides enhanced flexibility to build custom reports and integrate the data into your reporting applications and processes. Learn more about migrating to and using the [new Search Ads 360 Reporting\nAPI](https://developers.google.com/search-ads/reporting/overview).\n\n\nAdvertisers use **custom Floodlight variables** to report conversion data that is\nunique to their business needs, such as the genre of a movie that a user purchases, the name\nof the store from which an item is purchased, shipping costs, and so on. The data can be uploaded\nby a Floodlight tag on the advertiser's site or\n[by the Search Ads 360 API](/search-ads/v2/how-tos/conversions/custom-data),\nand you can use the API to download reports that contain the data.\n\n\n[Learn more](https://support.google.com/searchads/answer/4397154) about custom Floodlight\nvariables in Search Ads 360.\n\n### Metric or dimension\n\nAs part of setting up custom Floodlight variables, an advertiser uses the Search Ads 360\nUI to indicate how each variable can be used in reports:\n\n-\n **Metric** : In most reports, Search Ads 360 aggregates the values of\n variables that are defined as metrics. \n\n For example, an advertiser uses a custom Floodlight variable to track shipping costs.\n If a Search Ads 360 user defines this variable as a metric and you include the variable\n in an [`adGroup`](/search-ads/v2/report-types/adGroup) report,\n you'll see the total shipping costs associated with each ad group in the report's scope.\n\n\n In the [`conversion`](/search-ads/v2/report-types/conversion)\n report, Search Ads 360 provides raw data about individual conversions instead of aggregated data.\n\n Note: Custom metrics can also appear in\n [Floodlight reporting columns](https://support.google.com/searchads/answer/6024745). In the\n Search Ads 360 UI, users add custom metrics to Floodlight reporting columns and then include\n the Floodlight reporting columns in reports. You can also include these Floodlight columns\n in a report request, just as you can include any other type of\n [saved column](/search-ads/v2/how-tos/reporting/saved-columns).\n-\n **Dimension** : Variables that are defined as dimensions can be used to segment\n most reports. \n\n For example, an advertiser uses a custom Floodlight variable to track store names. After\n a Search Ads 360 user defines this variable as a dimension, you can use it to segment an\n [`adGroup`](/search-ads/v2/report-types/adGroup) report and\n see the number of purchases from each store that are attributed to ads in the ad group.\n\n\n In the [`conversion`](/search-ads/v2/report-types/conversion)\n report, Search Ads 360 provides raw data about individual conversions instead of\n aggregated data. So when you add a custom dimension to the `conversion` report,\n you'll see the dimension value. Continuing the example from the previous paragraph, if you\n segment a `conversion` report by the storeName custom dimension, you'll see\n the name of the store in which each specific purchase occurred.\n\n\n Note: When Search Ads 360 users define a\n [Floodlight reporting column](https://support.google.com/searchads/answer/6024721), they\n can use custom dimensions as a filter so the column reports only the conversions that\n recorded a specific dimension value.\n\n### Include custom metrics in a report request\n\nTo include custom metrics in a report request:\n\n-\n You'll need to know the **friendly** name that was\n specified when the\n [custom\n Floodlight variable was created in Campaign Manager](https://support.google.com/dcm/answer/2823222#customvar).\n The friendly name also appears in the Search Ads 360 UI when\n [setting up\n custom dimensions and metrics](https://support.google.com/searchads/answer/6024747#set-up).\n\n-\n The scope of the report needs to be a specific advertiser or lower.\n\nThen in a report request, include:\n\n-\n [`customMetricName`](/search-ads/v2/reference/reports#request.columns.customMetricName): Specifies the friendly name of the custom metric.\n\n The custom metric name is case sensitive.\n\n-\n [`platformSource`](/search-ads/v2/reference/reports#request.columns.platformSource): Always set this to **floodlight**.\n\n\nFor example if an advertiser created a custom metric named **shippingCost** ,\ninclude the shippingCost `customMetricName` in a report: \n\n```text\n{\n \"reportScope\": {\n \"agencyId\": \"12300000000000456\", // Replace with your ID\n \"advertiserId\": \"21700000000011523\", // Replace with your ID\n },\n ...\n \"columns\": [\n {\n \"customMetricName\": \"shippingCost\",\n \"platformSource\": \"floodlight\"\n }\n ],\n ...\n}\n \n```\n\n### Segment a report by a custom dimension\n\nTo segment a report by a custom dimension:\n\n-\n You'll need to know the **friendly** name that was\n specified when the [custom\n Floodlight variable was created in Campaign Manager](https://support.google.com/dcm/partners/answer/2823222#customvar).\n The friendly name also appears in the Search Ads 360 UI when setting up\n custom dimensions and metrics.\n\n- The scope of the report needs to be a specific advertiser\n or lower.\n\n- Each report request can only specify **one** custom dimension. But the\n request can include [additional non-custom segments](/search-ads/v2/how-tos/reporting/segmented-reports#multiple). \n\n For example, you can segment a report by the storeName custom dimension **and**\n by the quarter and device non-custom segments. Just be aware that the number of rows could\n increase exponentially with each additional segment.\n\nThen in a report request, include:\n\n-\n [`customDimensionName`](/search-ads/v2/reference/reports#request.columns.customDimensionName): Specifies the friendly name of the custom dimension.\n\n The custom dimension name is case sensitive.\n\n-\n [`platformSource`](/search-ads/v2/reference/reports#request.columns.platformSource): Always set this to **floodlight**.\n\n\nFor example if an advertiser created a custom dimension named **storeName** ,\ninclude the storeName `customDimensionName` in a report to segment metrics by store name: \n\n```text\n{\n \"reportScope\": {\n \"agencyId\": \"20700000000000123\", // Replace with your IDs\n \"advertiserId\": \"2170000012345\" // Replace with your IDs\n },\n \"reportType\": \"campaign\",\n\n \"columns\": [\n { \"columnName\": \"campaignId\" },\n { \"columnName\": \"clicks\" },\n { \"columnName\": \"cost\" },\n { \"columnName\": \"dfaRevenue\"},\n\n {\n \"customDimensionName\": \"storeName\",\n \"platformSource\": \"floodlight\"\n }\n ],\n ...\n}\n \n```"]]
