> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/features/reports/social-media-activity.md).

# Social Media Activity

The Social Media Activity Report summarizes Twitter activity recorded for each location during the selected date range. Use it to compare social engagement across locations.

### Input Variables

* **Date Range:** Define the period when the social media activity occurred. The date range can include up to 90 days and cannot begin before January 2014.
* **Time Zone:** Choose the time zone used to interpret the start and end dates. The report defaults to the time zone in your profile.
* **Locations:** Select the locations whose social media activity you want to include. If no locations or location groups are selected, the report includes all locations you can access.
* **Location Groups:** Include all accessible locations within one or more location groups, such as a franchise or territory.

### Report Values

* **Location:** The location where the social media activity was recorded.
* **Twitter Posts:** The number of Twitter post activities recorded for the location.
* **New Twitter Followers:** The number of new Twitter follower activities recorded for the location.

Locations are sorted by their combined number of Twitter posts and new followers, from highest to lowest. Locations with no recorded social media activity during the selected date range do not appear in the report.


---

# 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.perkville.com/features/reports/social-media-activity.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.
