> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/additional-sources/chrome-store/chrome-store-reviews.md).

# Chrome Store Reviews

| Category           | Record count |
| ------------------ | ------------ |
| Available formats  | JSON         |
| Delivery frequency | On-demand    |

***

## Available resources

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Data dictionary</td><td><a href="/additional-sources/chrome-store/chrome-store-reviews/data-dictionary.md">Data Dictionary</a></td></tr><tr><td>Data sample</td><td><a href="/additional-sources/chrome-store/chrome-store-reviews/data-sample.md">Data Sample</a></td></tr></tbody></table>

***

## Data field overview

### Metadata

This section includes various metadata fields from the record and company profile, such as:

* Record source
* Data object type
* Creation and update timestamps
* Various identifiers
* Deletion status
* Review and extension logo URL.

### Review and author

This section contains information about the review and reviewer, such as:

* Author's name
* Review details
* Review publish date
* Rating given in the review.

### Vendor's answer

This section contains the details about the vendor's answer to the review:

* Vendor's identifier, name, and logo/avatar
* Answer to the review and answer date.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coresignal.com/additional-sources/chrome-store/chrome-store-reviews.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.