Line format<\/b>: [Latitude],[Longitude],[Radius] (Radius can be either 150 or 2251)<\/span>
Example<\/b>: 123.414,-123.424,<\/span>2251<\/p>\n\n\n\n
This Audience has a limit of 100,000 coordinates per list.<\/span><\/p>\n\n\n\n Lat Long Audiences & Campaign Scale<\/strong><\/p>\n\n\n\n These audiences should be used with Mobile In-App and Mobile Web inventory only. Lat\/Long targeting relies on mobile GPS data and location services to pinpoint the exact latitude and longitude where the user is located. This data is not typically shared by browsers, so most impressions will be for mobile applications. It is strongly recommended to always include Mobile In-App inventory on Lines targeting Lat\/Long Audiences. Note, that approximately 30% of mobile impressions received contain location data that you can target with lat\/long segments. <\/p>\n\n\n\n Scaling lat\/long campaigns can be difficult as several conditions must be met in order for an impression to be eligible and accessible for targeting:<\/p>\n\n\n\n This strategy is only recommended for certain use cases, such as an event, where your target audience is in a very tight geo at the same time. We encourage users to consider incorporating a Geo-framed Custom Audience to retarget visitors that have visited the location at a later date into their strategies as well, as these audiences tend to provide better scale. Read more about these audiences here: Geoframed Commercial Address Segments<\/mark><\/a><\/p>\n\n\n\n Estimating Potential Budget for a Lat\/Long Campaign<\/strong><\/p>\n\n\n\n Here is an example of the recommended math to estimate the potential spend for your lat\/long campaign:<\/p>\n\n\n\n <\/p>\n\n\n\n This is an estimate and not a guarantee, as there is a lot of room for uncertainty as to the percentage of users that will open ad-enabled apps monetized on the open exchange AND have their location services turned on while they are in the designated geo-fence.<\/p>\n\n\n\n NOTE<\/strong>: any other targeting parameters applied to the Line Item, for example, an app list, frequency capping, OS targeting, day parts, limiting the exchange list, etc. will further limit scale and IS NOT RECOMMENDED.<\/p>\n\n\n\n\n
\n
Estimate the number of users that you think will attend the event, or that will be within the geo-fence in a 24-hour period. In this case we will use an event with 1,500 attendees as an example.
We estimate that 50% of all attendees will use their mobile phones in ad-enabled apps during the event:
1,500 * 0.5 = 750<\/li>\n<\/ol>\n\n\n\n\n
An estimated 30% of those impressions would be targetable by lat\/long (location services on and app sharing precise location):
750 * 0.3 = 225 addressable users
We will then estimate that these 225 users can be served 3-5 ads as they use the app:
225 * 3 = 675
250 * 5 = 1,125
This would give us an estimated range of 675 \u2013 1,125 potential impressions per day
<\/li>\n\n\n\n
In-App inventory typically runs between $6-$12 CPM depending on the App.
This would give you a daily budget range:
675\/1000 * $6 = $4.05
1125\/1000 * $12 = $13.5
The estimated daily potential budget would be between $4.05 and $13.50<\/strong>.<\/li>\n<\/ol>\n\n\n\n
![\"\"](\"https:\/\/sec-wiki.pontiac.media\/wp-content\/uploads\/2021\/01\/Lat-Long-Audience-1.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/sec-wiki.pontiac.media\/wp-content\/uploads\/2021\/01\/Lat-Long-Audience-2.png\")
<\/p>\n\n\n\n![\"\"](\"https:\/\/sec-wiki.pontiac.media\/wp-content\/uploads\/2021\/01\/Lat-Long-Audience-3.png\")
<\/p>\n\n\n\n![\"\"](\"https:\/\/sec-wiki.pontiac.media\/wp-content\/uploads\/2021\/01\/Lat-Long-Audience-4.png\")
<\/p>\n\n\n\n