> ## Documentation Index > Fetch the complete documentation index at: https://docs.tryprofound.com/llms.txt > Use this file to discover all available pages before exploring further. # Install Profound Pixel > A step-by-step guide to install and use your Profound Pixel This guide walks you through everything you need to get started with Profound Pixel: getting your pixel ID, adding the code snippet to your website, setting up and verifying conversion tracking. ## Before you start Have these things in place before any code goes on your site: 1. **Sign the data processing addendum.** The pixel sends Profound end-user data your current agreement doesn't cover. Reach out to your ads representative, and don't install until the addendum is signed. 2. **Tell your Profound team your domains.** Each pixel ID carries its own list of allowed domains, and events from a domain that isn't on the list are not processed. Share every hostname you'll install the pixel on. ## Installation steps In the Profound platform, go to **Ad Manager** (in the left sidebar, under **Ads**), select **Conversions** in the top-right corner, then under **Your pixels**, select **Generate pixel**. Each pixel ID covers one site or environment. Install the snippet manually or through Google Tag Manager. Paste this code snippet into the `` of every page you want to measure, and replace `` with the pixel ID you retrieved in [step 1](#step-1): ```html expandable theme={null} ``` Keep both `pfq` function calls. They do different jobs: * `pfq("init", …)` sets up identity and consent handling and captures the ad click ID from the landing URL. It records nothing by itself. * `pfq("track", "page_viewed")` records the page view. Without it, the page reports nothing. **Placement rules**: * Place the snippet on every page you want measured. A good practice is to add it to every page through your global layout or base template. * Place it in ``, as early as practical. The snippet must run before anything can rewrite the landing URL, to prevent the loss of ad click IDs. * Place it once per page. The snippet ignores copies of itself (`if (w.pfq) return`), but the `page_viewed` line doesn't: copies count every page view multiple times. **Single-page apps must record their own page views.** The pixel doesn't watch for route changes, so call `pfq('track', 'page_viewed')` once on each route change you want recorded. If you manage your site's tags in Google Tag Manager, install the pixel as a [Custom HTML tag](https://support.google.com/tagmanager/answer/6107167): 1. In Google Tag Manager, create a new tag and choose the **Custom HTML** tag type. 2. Paste in the code snippet from the **Manual installation** tab, and replace `` with the pixel ID you retrieved in [step 1](#step-1). 3. Set the trigger to **Initialization - All Pages**. 4. Under **Advanced Settings** > **Tag firing options**, choose **Once per page**. 5. Under [Consent Settings](https://support.google.com/tagmanager/answer/10718549), choose **No additional consent required**. The last two settings may look overly permissive, but they're intentional: the pixel manages consent itself, and firing it too late loses the ad click ID, so conversions can't be tied back to ads. If your site is a single-page app, add a second tag that calls `pfq('track', 'page_viewed')` with a [History Change trigger](https://support.google.com/tagmanager/answer/7679322), so route changes are recorded as page views. Learn about how the pixel reads consent signals and what each setting does in [Consent and privacy](/pixel/consent-and-privacy#consent-handling). The pixel starts in opt-in mode: it stores and sends nothing until a consent signal grants it. If your site is in the UK, the EU, or the wider European Economic Area, no action is required. Your consent management platform (CMP) provides the consent signal for the pixel. If you have a US-only site, you likely don't have a CMP, so you need to explicitly set the consent posture to opt-out for the pixel to be able to record events. Edit the `pfq("init", …)` line inside the snippet you added in [step 2](#step-2) so it passes the posture option: ```javascript theme={null} pfq("init", "", { posture: "opt-out" }); ``` If your site enforces a strict [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP), it blocks the pixel until you allow Profound's domains. Add these directives to your policy: * [`script-src`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/script-src) `https://pixel.profound.click` allows the browser to load the pixel script. * [`connect-src`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/connect-src) `https://events.profound.click` allows the pixel to send events. The inline snippet from [step 2](#step-2) also needs a [nonce or hash](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/script-src) on its ` ``` **Notes**: * The `{{DLV - …}}` variable names given above are examples only. Use the variable names defined in your Google Tag Manager container. Learn more in the [Data Layer Variables documentation](https://support.google.com/tagmanager/answer/7683362). * The `* 100` multiplier in the code example only suits currencies with two decimal places, such as USD or EUR. For other currencies, match the multiplier to the currency's number of decimals. For the detailed breakdown of events and their fields, see the [Events reference](/pixel/events). Complete a test conversion on your own site (for example, a test purchase). In your browser's network tab, filter for `events.profound.click`. Locate the event request produced by your test conversion and check the following: 1. It's a `POST` request with a `202` status response. 2. The `amount` field in the payload body is a whole number in minor units (the smallest unit for the given currency): for example, an amount of 129.99 US dollars should show as `12999`. If the amount you see is in different units, go back to the tracking code you added in [step 5](#step-5) and correct the units it sends. 3. If your site receives European/UK traffic, test the conversion as a European visitor. Until you accept the consent banner, the pixel should send no requests and write no cookies. After you accept, requests to `events.profound.click` should appear in the network tab, and the pixel's cookies should appear in your browser's cookie storage. Simulate a visit to your site from Europe by using a VPN, or by setting an EU-based location override in your browser's DevTools. After completing these steps, your pixel should be set up and ready to go. If you have issues during setup, see [Troubleshooting](/pixel/troubleshooting) for the most common issues, or [contact support](mailto:support@tryprofound.com).