Install the Buron pixel
Add one snippet to your site, and Buron starts capturing where every lead and customer comes from.
The Buron pixel is a small snippet you add to your site. Once it's live, we capture the marketing channel behind every visit, signup, and sale, and save the full visitor journey alongside each person.
Your forms, checkout, and CRM can tell you what someone did. They can't tell you which campaign earned it. The pixel fills that gap: it records the channel, campaign, and landing page for every visit, then ties them to the person the moment they identify themselves.
Before you begin
You'll need:
- A Buron workspace (a free trial is fine)
- Admin access to your website or tag manager
- A couple of minutes. There's no code beyond a single snippet.
We create your site and a unique write key for you, so there's nothing to set up first.
Step 1: Copy your snippet
Open Settings → Pixel. We show your snippet with your site's write key already filled in. It looks like this:
<script>window.BuronConfig = { writeKey: "YOUR_WRITE_KEY" };</script>
<script src="https://YOUR-SNIPPET-HOST/b.js?k=YOUR_WRITE_KEY"></script>Click Copy to grab the real one. Your write key and host are already filled in, so you don't need to edit anything.
Step 2: Add it to your site's head
Paste the snippet into the <head> of your site. Pick your platform:
- Webflow: Site settings → Custom code → paste into Head code, then save and publish. (Custom code needs a paid Webflow plan.)
- Google Tag Manager: new tag → Custom HTML → paste → set the trigger to Initialization – All Pages so the first pageview isn't missed → publish.
- Next.js: add both tags to your root layout with
next/script. Client-side navigations are captured automatically. - WordPress: use a header-code plugin such as WPCode, paste before
</head>, then save and clear your cache.
Keep it in the head, not the body. That way the first pageview is recorded before anything on the page redirects.
Step 3: Publish, then verify
Publish your site, then come back to Settings → Pixel and click Verify. A green Verified state means events are arriving.
If it fails, we name the reason. The usual culprits are the snippet landing in the body instead of the head, a Content-Security-Policy meta tag blocking the script, or a cache still serving the old page. Fix it and verify again.
Want to watch it happen? Open the live event feed on the same page and load any page of your site. You'll see the pageview show up within a second. You can also add ?buron_debug=1 to any URL for an on-page overlay.
What Buron captures
For every visit, automatically:
- Channel, source, medium, campaign, content, and term (from UTMs and the referrer)
- Landing page and referrer
- Click IDs such as
gclid, for ad platforms - Device, plus first-touch and last-touch values
When someone submits a form or checks out, we link the journey to them by email. Buron hashes the address (SHA-256) the moment it reaches us and discards the raw value, so it's never stored or queued. We also read Consent Mode signals, and contacts you scrub for GDPR are dropped on the way in.
Where to see it
- Datasets: pick the Warehouse source to slice events, sessions, and touchpoints by any dimension, then build a Report to answer a specific question and pin it to a dashboard.
- Settings → Pixel: the live event feed, for quick spot-checks.
- Once you connect a CRM, we tie each touchpoint to deals and revenue, so you can see pipeline and ROAS by channel.
Frequently asked questions
Does it slow my site down? No. The script is async and tiny, and it loads after your content.
Do I need to track forms or clicks myself? No. Pageviews, form submissions, chat, and meeting bookings are captured automatically. Single-page apps work with no router wiring.
What if Verify keeps failing? The usual causes are the snippet in the <body> instead of the <head>, a Content-Security-Policy meta tag blocking the script, or page caching. The Verify message tells you which one.
Is the data private? Buron hashes each email the moment it arrives and discards the raw address, so it's never stored or queued. We honor Consent Mode, and scrubbed contacts are dropped on ingest.
Can I serve the script from my own domain? Yes. Set a custom domain in Settings → Pixel so the script and collector run first-party.
Next steps
- Connect your CRM (Attio or HubSpot) so revenue ties back to source
- Set up conversion tracking so bidding optimizes toward real revenue
Was this page helpful?