# Edge Pulse quickstart This guide instructs you through collecting your first measurements with [Edge Pulse](/en/documentation/platform/edge-pulse/). - Open Edge Pulse in Azion Console. - Copy the Edge Pulse JavaScript tag that Azion Console serves. - Add the tag to every page you want to monitor, and publish those pages. - Find where the measurements your visitors produce are read. There is nothing to create in Azion Console. Edge Pulse is a default product, activated for every Azion account, and the tag it serves already exists. The only object you change is your own HTML. One page carries one tag, and a page without the tag is a page Edge Pulse does not measure. That is the whole composition, and it is why this guide ends in your publishing system rather than in Azion Console. --- ## Prerequisites - An Azion account. To create one, refer to [How to create an account on Azion](/en/documentation/fundamentals/creating-account/). - Access to Azion Console. To sign in, refer to [How to access Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/). - The pages you want to monitor, with access to edit and publish their HTML. --- ## Open Edge Pulse in Azion Console The tag is served from the product's own page, and no activation step comes before it. Access [Azion Console](https://console.azion.com/) > **Products menu** > **Observe** > **Edge Pulse**. The **Edge Pulse** page opens, carrying the Edge Pulse JavaScript tag behind a **Copy to Clipboard** button. --- ## Copy the tag The tag Azion Console serves is customized for your account, so copy it from your own Console rather than from anywhere else. It comes in two forms, and choosing between them is a property of your pages rather than a preference. Take the **Default Tag**. Take the **Pre-loading Tag** instead when the page carries Content Security Policy settings that prevent the use of inline JavaScript. For what separates the two, refer to [Edge Pulse JavaScript tag](/en/documentation/platform/edge-pulse/javascript-tag/). To copy the tag in Azion Console: 1. **Select the tag your pages need** 2. **Select Copy to Clipboard** The tag is on your clipboard, ready to paste into a page. --- ## Add the tag to every page you want to monitor Edge Pulse measures a page because that page carries the tag. The tag is not inherited from a parent path, from a template you did not republish, or from another page of the same site. A page you leave untagged produces no measurements at all. To add the tag to your pages: 1. **Paste the tag into the page** In the HTML of the page, paste the tag immediately before the closing `body` tag. 2. **Repeat for every page you want to monitor** Paste the same tag page by page, or distribute it across the pages with a tag management system. 3. **Publish the pages** Each page you published carries the Edge Pulse JavaScript tag, and the browsers of the visitors to those pages run it. --- ## Find where the measurements are read A measurement comes from a real visit. Nothing is collected until a visitor loads one of the pages you published, so the first results follow your traffic rather than the moment you published. On a page with little traffic, allow for that before concluding the tag is wrong. There is no page in Azion Console that shows them. The measurements are read with the GraphQL API that [Real-Time Events](/en/documentation/platform/real-time-events/) serves, and a query is the only way to reach them. The dataset to query is `pulseEvents`. For how to authenticate against that endpoint and send a first query, refer to [GraphQL API first steps](/en/documentation/devtools/graphql/first-steps/). For the fields `pulseEvents` carries, refer to [Real-Time Events GraphQL API fields](/en/documentation/devtools/graphql/gql-real-time-events-fields/). Your pages are tagged, and every visit to one of them produces a measurement Edge Pulse collects. For what a tagged browser does on a visit, how often it repeats the test, and what identifies a visitor, refer to [How Edge Pulse works](/en/documentation/platform/edge-pulse/how-it-works/). --- ## Next steps - [How Edge Pulse works](/en/documentation/platform/edge-pulse/how-it-works.md): Follow a measurement from the browser that performs the test to the result you query. - [Edge Pulse JavaScript tag](/en/documentation/platform/edge-pulse/javascript-tag.md): The two tags, where each one goes in the page, and the browser settings the tag respects. - [Test the speed of an application](/en/documentation/fundamentals/test-speed.md): Where real-user measurements sit among the other ways to measure how fast an application answers. - [Glossary](/en/documentation/platform/edge-pulse/glossary.md): The terms these pages use for the two tags, the test, and the visitor identifier.