# Web Activity **Web activities are experiences that happen outside of an app.** The combination of Web Activity and Web Tracking is a powerful mechanism that allows any off-app activity & pathway integration to be limited only by the imagination. Off-app experiences can take the form of websites, LMSes, web games, single-purpose interactives, or linking through to just about any platform. {% embed url="" %} How to create a web activity. {% endembed %} **To simply track that a user has visited the URL, use the code snippet provided when you set up a Web Activity.** This option is perfect if your web activity is server-less, or if it is a single-purpose interactive experience. If you wish to provide deeper tracking with push and pull events, please read our [Web Tracking API documentation](https://beta.falkor.io/u/webtracking-api-docs/). ## Web Activity Example: Javascript Web Tracking **Here is a simple example of using the Javascript Web Tracking API.** {% embed url="" %} Javascript Web Tracking example {% endembed %} **Along the pathway, users are presented with a Web Activity that requires them to push a button 10 times in order to complete.** When selecting the activity, the user will be taken to the external location/URL where the activity is hosted. Once the fulfilment has been reached (in this case pushing a button 10 times), the activity on the pathway will be marked as complete. Access the full source code on GitHub. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://everyday-digital.gitbook.io/pathways-docs/pathway-editor/pathway-activities/web-activity.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.