> For the complete documentation index, see [llms.txt](https://help.pagefly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pagefly.io/page-structure-and-elements/pagefly-elements/social.md).

# Social

### About PageFly Social Elements

Turn your visitors into brand advocates with PageFly social elements!

This Social Elements overview explores tools designed to leverage the power of social media and build trust with your audience. You can integrate Instagram/Facebook/Twitter feeds directly on your store pages to keep visitors engaged and informed, all while strengthening your brand identity through social proof. Plus, elements such as Facebook Like & Share buttons help you build trust and foster a sense of community or encourage social sharing, expanding your reach and driving traffic.

Ready to leverage the power of social media on your PageFly store? Explore the following guides and learn how to integrate Social Elements for optimal impact.

### Related Resources

* [How to Use PageFly Icon Element Properly | Updated in 2023](https://help.pagefly.io/manual/icon-element/)
* [Paragraph Element](https://help.pagefly.io/manual/paragraph-element/)
* [Optimize Pages for CRO with PageFly Elements](https://help.pagefly.io/manual/optimize-pages-for-cro-with-pagefly-elements/)


---

# 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://help.pagefly.io/page-structure-and-elements/pagefly-elements/social.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.
