UserLocationPerformanceReport
Use this report to see which locations your traffic is coming from. You can then validate whether your location targeting strategy is successful, and identify opportunities to improve. The report also identifies the physical location of the user and the intended geographical location of the user's search query, for example a user in Seattle searching for services in Portland.
Columns
| Name | Type | Select requirement | Metric | Aggregate | Description |
| Summary | String | True | The report data will be aggregated by the entire specified report time. The report will not include a time period column. | ||
| Hourly | String | True | Each row of the report identifies the hour when the transaction occurred. The report data will be aggregated by each hour of the day. | ||
| Daily | Date | True | Each row of the report identifies the month, day, and year when the transaction occurred. The report data will be aggregated by each day. Each row of the report identifies the month, day, and year when the transaction occurred. The report will include a column named GregorianDate that contains the day formatted as yyyy-mm-dd. | ||
| Weekly | Date | True | Each row of the report identifies the week when the transaction occurred. The report data will be aggregated by each week. The report will include a column named WeekStartDate that contains the date of the Sunday for each week formatted as yyyy-mm-dd. | ||
| Monthly | Date | True | Each row of the report identifies the month when the transaction occurred. The report data will be aggregated by each month. The report will include a column named MonthStartDate that contains the first day of the month formatted as yyyy-mm-dd. | ||
| Yearly | Integer | True | Each row of the report identifies the year when the transaction occurred. The report data will be aggregated by each year. The report will include a column named Year that contains the year formatted as yyyy. | ||
| HourOfDay | Integer | True | Each row of the report identifies the hour of the day when the transaction occurred. The report data will be aggregated by each of the 24 hours across all days | ||
| DayOfWeek | Integer | True | Each row of the report identifies the day of the week when the transaction occurred. The report data will be aggregated by each of the seven days in a week. | ||
| AccountName | String | True | The account name. | ||
| AccountNumber | String | The Bing Ads assigned number of an account. | |||
| AccountId | Long | The Bing Ads assigned identifier of an account. | |||
| AdGroupId | Long | The Bing Ads assigned identifier of an account. | |||
| CampaignId | Long | The Bing Ads assigned identifier of a campaign. | |||
| AdGroupName | String | The ad group name. | |||
| CampaignName | String | The campaign name. | |||
| Language | String | The ad group language. | |||
| Country | String | The country where the user was physically located when they clicked the ad. | |||
| State | String | The state where the user was physically located when they clicked the ad. | |||
| MetroArea | String | The metro area where the user was physically located when they clicked the ad. | |||
| City | String | The city where the user was physically located when they clicked the ad. | |||
| CurrencyCode | String | The account currency type. | |||
| AdDistribution | String | The ad distribution attribute of an ad group. | |||
| ProximityTargetLocation | String | The radius target bid name. The name of the geographic radius where the user was physically located when they clicked the ad. | |||
| Radius | String | The radius of a radius target bid. The geographic radius where the user was physically located when they clicked the ad. | |||
| BidMatchType | String | The keyword bid match type. This can be different from the DeliveredMatchType column, for example if you bid on a broad match and the search term was an exact match. For more information, see Budget and Bid Strategies. | |||
| DeliveredMatchType | String | The match type used to deliver an ad. This can be different from the BidMatchType column, for example if you bid on a broad match and the search term was an exact match. For more information, see Budget and Bid Strategies. | |||
| Network | String | The current network setting of an ad group. | |||
| TopVsOther | String | The report will include a column that indicates whether the ad impression appeared in a top position or elsewhere. | |||
| DeviceType | String | The device name attribute of a device OS target bid. The type of device which showed ads. | |||
| County | String | The county where the user was physically located when they clicked the ad. | |||
| DeviceOS | String | The operating system of the device reported in the DeviceType column. | |||
| LocationId | Long | The Bing Ads identifier of the location where the user was physically located when they clicked the ad. For geographical location identifiers, see Geographical Location Codes. | |||
| PostalCode | String | The postal code where the user was physically located when they clicked the ad. | |||
| QueryIntentCountry | String | The name of a country if the user's geographical intent can be determined. The country is set if the user's intent is related to a country, and not necessarily if they are physically located in the county. | |||
| QueryIntentState | String | The name of a state if the user's geographical intent can be determined. The state is set if the user's intent is a state or sub geography of the state, and not necessarily if they are physically located in the state. | |||
| QueryIntentCity | String | The name of a city if the user's geographical intent can be determined. The city is set if the user's intent is a city, and not necessarily if they are physically located in the city. | |||
| QueryIntentDMA | String | The postal code where the user was physically located when they clicked the ad. | |||
| QueryIntentCounty | String | The name of a county if the user's geographical intent can be determined. The county is set if the user's intent is related to a county, and not necessarily if they are physically located in the county. | |||
| QueryIntentPostalCode | String | The name of a postal code if the user's geographical intent can be determined. The postal code is set if the user's intent is a postal code, and not necessarily if they are physically located in the postal code. | |||
| QueryIntentLocationId | String | The location identifier if the user's geographical intent can be determined. | |||
| Goal | String | The goal name. | |||
| GoalType | String | The goal type. Possible values include AppInstall, Duration, Event, InStoreTransaction, OfflineConversion, PagesViewedPerVisit, and Url. | |||
| Impressions | Integer | True | The number of times an ad has been displayed on search results pages. Without impressions there are no clicks or conversions. | ||
| Clicks | Integer | True | Clicks are what you pay for. Clicks typically include a customer clicking an ad on a search results page or on a website on the search network. Clicks can also come from other sources (for example, spiders, robots, and test servers). | ||
| Ctr | Double | True | The click-through rate (CTR) is the number of times an ad was clicked, divided by the number of times the ad was shown (impressions). For example, if your ads got 50 clicks given 2,348 impressions, your CTR is 2.13 (%). | ||
| AverageCpc | Double | True | The average cost per click (CPC). The total cost of all clicks on an ad divided by the number of clicks. This is the average amount you're actually charged each time your ad is clicked. For example, if you paid a total of 48.35 for 300 clicks, your average CPC is 0.16. | ||
| Spend | Double | True | The cost per click (CPC) summed for each click. | ||
| AveragePosition | Double | True | The average position of the ad on a webpage. | ||
| Assists | Integer | True | The number of conversions from other ads within the same account that were preceded by one or more clicks from this ad. | ||
| Conversions | Integer | True | The number of conversions. A conversion is the completion of an action by a customer after viewing your ad. The action could be purchasing your product, registering for your webinar, joining an organization, or whatever you consider your goal and best measure of the ad's success | ||
| CostPerConversion | Double | True | The cost per conversion. The formula for calculating the cost per conversion is (Spend / Conversions). | ||
| ConversionRate | Double | True | The conversion rate as a percentage. The number of conversions, divided by the total number of clicks. For example, if the ads in your campaign got 300 clicks and four conversions, the conversion rate is 1.33 (%). | ||
| Revenue | Double | True | The revenue optionally reported by the advertiser as a result of conversions. Corresponds to the optional revenue parameter of a Bing Ads campaign analytics tracking script. | ||
| ReturnOnAdSpend | Double | True | The return on ad spend (ROAS). | ||
| CostPerAssist | Double | True | The cost per assist. The formula for calculating the cost per assist is (Spend / Assists). | ||
| RevenuePerConversion | Double | True | The revenue per conversion. The formula for calculating the revenue per conversion is (Revenue / Conversions). | ||
| RevenuePerAssist | Double | True | The revenue per assist. The formula for calculating the revenue per assist is (Revenue / Assists). |
Pseudo-Columns
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| DatePreset | String | The time period to use for the report. You can specify a custom date range or select a predefined date range, for example, Today or ThisWeek.
The allowed values are Today, Yesterday, LastSevenDays, ThisWeek, LastWeek, Last14Days, Last30Days, LastFourWeeks, ThisMonth, LastMonth, LastThreeMonths, LastSixMonths, ThisYear, LastYear, ThisWeekStartingMonday, LastWeekStartingMonday, LastFourWeeksStartingMonday. |
| EndDate | String | The end date of the custom date range. The end date cannot be later than today's date. |
| StartDate | String | The start date of the custom date range. The start date must be earlier than or the same as the end date. |