How can I access the name_with_location_descriptor field on an endpoint / page in the Graph API?
page API Reference Graph has a field named name_with_location_descriptor
which is defined as:
The name of the page with its location and / or global brand descriptor
and has a clue that reads:
This field is only available in version 2.2 or later
However, I cannot get this field to appear on any pages I try using both v2.2 and v2.3. What's the secret to creating this field? (And while we're at it, what should I expect to find in this area?)
To provide more information, the field does not even appear at the root endpoint /<page-id>
, but only as a child node in global_brand_children
. Here's a link An API Browser API link showing that this field is available (albeit greyed out) for this page that has global child brands. I also tried to switch the version to v2.2 with no changes.
source to share
Well maybe not a bug as I thought it looks like the name of the page descriptor i.e. the name of the page with the store location to be filled using functions facebook locations
when registering a specific location for your brand page child. Basically, it's a name and location. Don't see a separate highlighted field to fill this in on the page, but you can quickly check if you have a brand and use facebook places because I haven't found a page with different values for the name
and field yet name_with_location_descriptor field
. If the field is empty, it will not appear.
For example, link and result for coffee day coffee, popular brand in India, for location in Bangalore
{
"name": "Cafe Coffee Day Square",
"name_with_location_descriptor": "Cafe Coffee Day Square",
"location": {
"city": "Bangalore",
"country": "India",
"latitude": 12.971819331327,
"longitude": 77.594207611099,
"street": "Cafe Coffee Day Square , 193926289498",
"zip": "560001"
},
"id": "322605374498798"
}
And elsewhere, but still in Bangalore
{
"name": "Cafe Coffee Day - BTM Layout",
"name_with_location_descriptor": "Cafe Coffee Day - BTM Layout",
"location": {
"city": "Bangalore",
"country": "India",
"latitude": 12.91400869993,
"longitude": 77.609964412192,
"street": "Cafe Coffee Day - BTM Layout , 193926289498",
"zip": "560068"
},
"id": "115977698546185"
}
source to share
While I have not yet been able to directly verify this information, I understand that there name_with_location_descriptor
is literally a field name
attached to it store_location_descriptor
. The Facebook documentation says:
Location descriptor for this store. This will appear after the name page and should only be used if the location has a special location that is not clear from its city or street address. for example if it is inside a mall or if it is best identified by its surroundings.
So, in the example above, if there name
was "Cafe Coffee", but there store_location_descriptor
was a "Day square", then I understand that you will see something like:
{
"name": "Cafe Coffee",
"store_location_descriptor": "Day Square",
"name_with_location_descriptor": "Cafe Coffee (Day Square)",
...
}
If I can find an example from the API, I'll post it, but the ReShiftMedia people have a pretty good blog post that explains how Facebook is trying to block a field name
, so all the locations of the same store have the same name.
source to share