- Previous: GET /v1/match/byphone
- Up: Central Index API
- Next: GET /v1/syndication_log/by_entity_id
GET /v1/stats/entity/by_date
NOTE: This method is not accessible to users on Starter Plan API keys. Please contact us if you want premium access to our service
HTTP Method: GET
Path: /v1/stats/entity/by_date
Authentication: API Key required
Description: Get a count of how many times an entity has been served by the Central Index API in a given period of time
Parameters:
parameter | type | description | Required |
entity_id | string | The id of the entity, e.g. 3791234532345 | Yes |
year | integer | The year for which stats are required | Yes |
month | integer | The month for which stats are required, e.g. for April, month = 4 | No |
Sample Responses:
If month is provided, the API will produce a response that shows how many times the entity has been served in advertiser search API calls ("advertiser"), in regular search API calls ("serps") and in single entity API calls ("bdp" - Business Details Page), how many emails have been sent to the business via the CI messaging path ("emails").
In addition, the following data points will be reported for actions that originate on sites that are powered by Central Index:
- gallery - views of entity photo gallery
- mappin - clicks on entity map pin
- social - clicks on any social links on the entity profile
- telephone - clicks to call on the entity phone numbers
- video - clicks on entity video
- website - clicks on link to entity website
{ "success": true, "msg": "ok", "data": [ { "entity_id": "437932693745664", "year": 2013, "month": 6, "event_type": "advert", "value": 81 }, { "entity_id": "437932693745664", "year": 2013, "month": 6, "event_type": "bdp", "value": 100 }, { "entity_id": "437932693745664", "year": 2013, "month": 6, "event_type": "email", "value": 60 }, { "entity_id": "437932693745664", "year": 2013, "month": 6, "event_type": "gallery", "value": 76 }, { "entity_id": "437932693745664", "year": 2013, "month": 6, "event_type": "mappin", "value": 66 }, { "entity_id": "437932693745664", "year": 2013, "month": 6, "event_type": "serps", "value": 71 }, { "entity_id": "437932693745664", "year": 2013, "month": 6, "event_type": "social", "value": 62 }, { "entity_id": "437932693745664", "year": 2013, "month": 6, "event_type": "telephone", "value": 70 }, { "entity_id": "437932693745664", "year": 2013, "month": 6, "event_type": "video", "value": 86 }, { "entity_id": "437932693745664", "year": 2013, "month": 6, "event_type": "website", "value": 69 } ] }
If only year is provided, the API will produce a response that shows the above values rolled up into one number for each month of the given year.
{ "success": true, "msg": "ok", "data": [ { "entity_id": "379236639285248", "year": 2013, "month": 3, "value": 104 }, { "entity_id": "379236639285248", "year": 2013, "month": 4, "value": 794 }, { "entity_id": "379236639285248", "year": 2013, "month": 5, "value": 283 } ] }
- Previous: GET /v1/match/byphone
- Up: Central Index API
- Next: GET /v1/syndication_log/by_entity_id
Docs Navigation
- Introduction
- Getting Started
- Using IODocs
- Responses
- Creating a sample request
- Sample Libraries
- Central Index API
- What data do we store in an entity?
- GET /v1/advertiser/updated
- GET /v1/autocomplete/category
- GET /v1/autocomplete/keyword
- GET /v1/autocomplete/location
- GET /v1/entity
- GET /v1/entity/advertisers
- GET /v1/entity/advertisers/inventorycheck
- GET /v1/entity/by_supplier_id
- GET /v1/entity/search/keyword/bynearest
- GET /v1/entity/search/what
- GET /v1/entity/search/what/bylocation
- GET /v1/entity/search/what/byboundingbox
- GET /v1/entity/search/what/bynearest
- GET /v1/entity/search/who
- GET /v1/entity/search/who/bylocation
- GET /v1/entity/search/who/byboundingbox
- GET /v1/entity/search/who/bynearest
- GET /v1/location
- GET /v1/location/context
- GET /v1/lookup/category
- GET /v1/match/byphone
- GET /v1/stats/entity/by_date
- GET /v1/syndication_log/by_entity_id
- GET /v1/token/add
- GET /v1/token/report
- GET /v1/token/claim
- GET /v1/token/message
- GET /v1/tools/docs
- GET /v1/user/by_email
- PUT /v1/business
- PUT /v1/business/json
- PUT /v1/entityserve
- POST /v1/entity/advertiser/cancel
- POST /v1/entity/advertiser/create
- POST /v1/entity/advertiser/renew
- POST /v1/entity/advertiser/upsell
- POST /v1/entity/category
- POST /v1/entity/claim
- POST /entity/claim/cancel
- POST /v1/entity/claim/reseller
- POST /v1/entity/description
- POST /v1/entity/document
- POST /v1/entity/email
- POST /v1/entity/fax
- POST /v1/entity/featured_message
- POST /v1/entity/geopoint
- POST /v1/entity/image
- POST /v1/entity/image/by_url
- POST /v1/entity/list
- POST /v1/entity/logo
- POST /v1/entity/logo/by_url
- POST /v1/entity/name
- POST /v1/entity/opening_times
- POST /v1/entity/payment_type
- POST /v1/entity/phone
- POST /v1/entity/postal_address
- POST /v1/entity/socialmedia
- POST /v1/entity/special_offer
- POST /v1/entity/tag
- POST /v1/entity/testimonial
- POST /v1/entity/video/youtube
- POST /v1/entity/website
- POST /v1/syndication/cancel
- POST /v1/syndication/create
- POST /v1/signal
- POST /v1/user
- DELETE /v1/entity/category
- DELETE /v1/entity/description
- DELETE /v1/entity/image
- DELETE /v1/entity/phone
- DELETE /v1/entity/logo
- DELETE /v1/entity/website
- syndication api