NAVTEQ's LocationPoint™ Advertising (LPA) product uses location and context to provide valued advertising to consumers while sharing the revenue with you, the developer.  This product continues to grow in features and functionality as seen by the latest update below.  For more info on this application, see our white paper and technical documentation.

What’s New in Version 2.3
 
The major changes moving from LPA v2.2 to v2.3 are:

1. Deprecate WAPurl and STOREINFO as it will no longer be supported
2. Update Interest Categories supported – Appendix G - Demographic Targeting – This allows for stronger ad relevance and will provide for a non-obtrusive ad experience enticing consumers to interact more frequently and therefore enabling new ad models such as “Cost Per Action”.

What’s New in Version 2.2

• Third-party Tracking Support
   
  NOTE – REQUIRED FEATURE – This feature must be implemented in order to have your application approved.
   
  LPA now supports a TrackURL element in our check-in response.  This is used to allow our advertisers to verify our reporting using third-party validation.  This is an ad industry standard for doing business larger advertisers.
   
  The IMPRESSION and LANDINGPAGE Calls to Action now contain a TRACKURL element.  As a part of the publisher reporting, you will need to send an HTTP GET request using the tracking URL when an IMPRESSION or LANDINGPAGE is reported. 
   
  More details can be found in the ‘Support for Third-party Tracking’ section in the Integration Guidelines document.
   
• DefaultUserAction Element
   
  NOTE – REQUIRED FEATURE – This feature must be implemented in order to have your application approved.
   
  LPA now supports the concept of a default user action (i.e. what happens when the banner is clicked?).  Currently, the default action is assumed to be LANDINGPAGE.  Before this release, every time a banner was clicked, the Landing Page was shown.  Now the default action allows LPA(with your help) to change the behavior of campaigns.  If the Default Action is set to WEBURL, for example, rather than showing the Landing Page, the application should redirect the user to the WEBURL specified.
   
  More details can be found in the ‘Support for DefaultUserAction’ section in the Integration Guidelines document.
   
• Operator and Device Parameters
  
  LPA can now capture operator and device information via the following new optional parameters in the endusercheckin call: 
  
  

  smcc	string	Optional.  SIM MCC (Mobile Country Code).
  smnc	string	Optional.  SIM MNC (Mobile Network Code).
  nmcc	string	Optional.  Network MCC (Mobile Country Code
  nmnc	string	Optional.  Network MNC (Mobile Network Code
  user-agent	string	Optional.   The User-Agent header field for the device making the request.
  user-ip	string	Optional.  The ip address for the device making the request.

  
  This information provides a great deal of value to our advertisers and ad network.  Advertisers can now target campaigns to device type, and our network can better understand how to design and serve the unique display and hardware of the mobile handsets.  For more information on these fields, please refer to the endusercheckin API later in the API Specification document.
  

• Support for Global Applications

  If your application is designed to work globally, please refer to the new 'Global Application Support' section in the Integration Guidelines document for a description of how to access LPA on a global basis.

• Proximity Banner
   
  The new feature that was previously called Hyper-Dynamic Local Banner has now been renamed.  It is now referred to by the term Proximity Banner.