Viewing Bing Maps Token Transaction Reports

Important

On March 30, 2012, the Bing Maps Token Service will be retired. If you are an existing customer using tokens, please update your application to use Bing Maps Keys, which are the recommended authentication method for the Bing Maps AJAX Control 6.3, the Bing Maps Silverlight Control, the Bing Maps SOAP Services, the Bing Maps REST Services, and the Bing Spatial Data Services. To learn more about Bing Maps Keys, see Getting a Bing Maps Key and Migrating from Tokens to Keys. Information about transaction accounting provided by Bing Maps Keys is in Understanding Bing Maps Transactions.

Requests sent to Bing Maps with a valid Bing Maps Token are tracked for reporting purposes. You can view application usage reports on the Bing Maps Platform Customer Services site. Log in to the Bing Maps Customer Services site using the Windows Live ID you used to create your Bing Maps Platform developer account. Click on the View Reports menu item on the left-hand side of the Home page. On the View Reports page, select one of the available Bing Maps Platform reports.

Note

You can also view token usage reports for the MapPoint Web Service on the Bing Maps Account Center. For more information, see Understanding Bing Maps Transactions.

Viewing Bing Maps Platform Reports

The Bing Maps Platform reports, which are found on the View Reports page of the Bing Maps Customer Services site, display information about your Bing Maps Platform usage, including your billable transactions ("Billable Transactions"). Bing Maps Platform transactions include MapPoint Web Service (MWS) transactions, Bing Maps (Bing Maps) map control transactions, Bing Maps SOAP Services (Bing Maps SOAP Services) transactions, as well as Photosynth transactions.

Once you have selected a report type, you can choose to filter by Environment to show Staging or Production transactions. Staging transactions are not billable transactions. Production transactions are billable transactions.

To access the Production environment you must be a licensed customer. Contact the Bing Maps Licensing Team for more information.

Billable Transactions

The Bing Maps Platform includes the MapPoint Web Service, the Bing Maps AJAX Control 6.3, the Bing Maps SOAP Services, and Photosynth.

MapPoint Web Service

The MapPoint Web Service (MWS) methods that cause billable transactions to be accrued include Find, FindAddress, FindById, FindByProperty, FindNearby, FindNearRoute, FindPolygon, GetLocationInfo, ParseAddress, GetMap, GetLineDriveMap, CalculateRoute, and CalculateSimpleRoute.

Bing Maps AJAX Control 6.3

Certain Bing Maps (Bing Maps) map control requests made after the VEMap.SetClientToken Method is called with a valid token are included in your transaction reports. The following Bing Maps AJAX Control 6.3 features count as billable transactions and appear in your Bing Maps Platform Reports.

Map navigation (Bing Maps Load Standard Map) – Transactions are counted any time new map tiles are requested from Bing Maps. Bing Maps Platform bills per map view, which is calculated based on the assumption that a map view is multiple tile transactions. This includes VEMap.LoadMap, VEMap.ZoomIn, VEMap.ZoomOut, VEMap.Pan, VEMap.SetMapView, and many other methods that cause the map to move. A single Billable Transaction shall equate to eight (8) Bing Maps image tiles being fetched from Microsoft servers.

Traffic requests (Bing Maps Load Traffic Map) – If traffic is turned on, you are charged double for every tile that includes traffic information. Bing Maps Platform bills per map view, which is calculated based on the assumption that a map view is multiple tile transactions. A single Billable Transaction shall equate to eight (8) Bing Maps image tiles being fetched from Microsoft servers.

Bing Maps Geocode – Any time Bing Maps AJAX Control 6.3 makes a where-only request for a find result, one transaction is counted. This includes where-only requests from the VEMap.Find method as well as the VEMap.GetDirections method.

Bing Maps ReverseGeocode - Each request made using the VEMap.FindLocations method counts as one transaction.

Bing Maps CalculateRoute – If you make a request for a route using the new VEMap.GetDirections method, one transaction per returned route is counted. Use of the deprecated GetRoute method is not counted.

Bing Maps SOAP Services

The following Bing Maps SOAP Services (Bing Maps SOAP Services) requests count as billable transactions and appear in your Bing Maps Platform Reports.

Bing Maps: Load Standard Map – Transactions are counted any time map tiles are requested from Bing Maps using URIs returned from the GetMapUri method or the GetImageryMetadata method. Bing Maps Platform bills per map view, which is calculated based on the assumption that a map view is multiple tile transactions. A single Billable Transaction shall equate to eight (8) Bing Maps image tiles being fetched from Microsoft servers.

Bing Maps SOAP Services: Geocode – Any time a request is made using the Geocode method, one transaction is counted.

Bing Maps SOAP Services: ReverseGeocode - Any time a request is made using the ReverseGeocode method, one transaction is counted.

Bing Maps SOAP Services: GetMapUri - Any time a request is made using the GetMapUri method, one transaction is counted. Note that the use of any URIs returned from the GetMapUri are counted separately as map tile requests.

Bing Maps SOAP Services: CalculateRoute – Any time a request is made using the CalculateRoute method, one transaction is counted.

Bing Maps SOAP Services: CalculateRoutesFromMajorRoads – If you make a request using the CalculateRoutesFromMajorRoads method and the MajorRoutesOptions.ReturnRoutes Property is set to false, one transaction is counted. If you make a request using the CalculateRoutesFromMajorRoads method and the MajorRoutesOptions.ReturnRoutes Property is set to true, one transaction plus one transaction per returned route is counted.

Bing Maps SOAP Services: Search - Any time a request is made using the Search method, one transaction is counted.

Photosynth

The following Photosynth requests count as billable transactions and appear in your Bing Maps Platform Reports.

Bing Maps SOAP Services: PhotoSynthView - Every Synth is associated with a Windows Live ID. Each time a Synth associated with a Windows Live ID that corresponds to a commercial Photosynth account is viewed, one transaction is counted.

See Also

Concepts

Requesting a Bing Maps Token