Skip to content

Tracking

Site pixel

One tag, /freebuff-tag.v2.js, on every page. It captures the click id, measures visits from your ads, and records conversions. No key, no backend, nothing charged.

Install

Every page
<!-- Once, in <head>, on every page. Tag id: console → Events. -->
<script async src="https://freebuff.com/freebuff-tag.v2.js?t=YOUR_TAG_ID"></script>
If you call freebuff() inline
<!-- If you call freebuff() before the tag loads, keep the stub first. -->
<script>window.freebuff=window.freebuff||function(){(window.freebuff.q=window.freebuff.q||[]).push(arguments)}</script>
<script async src="https://freebuff.com/freebuff-tag.v2.js?t=YOUR_TAG_ID"></script>

The tag updates in place within an hour; events are only ever added. For bytes that never change, use the pinned build. The Events page also copies a complete prompt for your coding agent.

Google Tag Manager

With Google Tag Manager already installed on your website:

  1. Copy your pixel snippet from Freebuff → Events → Set up Freebuff Pixel.

  2. In Google Tag Manager, open Tags → New → Tag Configuration → Custom HTML.

    Name the tag Freebuff Pixel and paste the full snippet, including your own tag ID.
  3. Set Triggering to All Pages.

    Follow your site’s consent policy. Save the tag, use Preview to check that it fires, then Submit → Publish.
  4. In Freebuff → Events → Conversion goals, add a page or analytics-event rule.

    Follow the goal setup below. With a rule, you do not need a separate Freebuff conversion tag in GTM.
  5. Click Continue to Verify, create a test link, and complete the real action.

    Confirm that the matching Test event arrives in Freebuff.

Alternatively, download the Freebuff Pixel template and import it under Templates → New → ⋮ → Import. Create a tag from that template, enter your tag ID, and fire it on All Pages.

Goals without code

After installing the pixel, open Events → Conversion goals (or choose Page or analytics event during pixel setup). Select your campaign, choose a rule below, select what it Counts as, and click Add rule.

KindMatchesExample
analytics_eventAn event name as your analytics tool sends itsign_up, purchase, CompleteRegistration
urlA page path; * is one segment/welcome, /thanks/*

For a success-page URL, choose Page URL and enter the Success page URL, such as /thank-you. Choose a page reached only after the action succeeds. Plain paths also match pages underneath them; query strings and fragments are ignored.

For an existing event, choose Event and enter its exact name, such as sign_up, or select a detected event. Your site must already emit that event through a supported analytics tool or GTM’s data layer; the rule does not create the event.

Use one reporting method for each goal. If you use a rule, do not also send an explicit Freebuff conversion for the same action. Click Continue to Verify, open a test link, and complete the action to check that a Test event arrives. You can turn off saved rules from Conversion goals.

  • Goals: Signup, Trial started, Demo booked, Installed, Paid subscription.
  • Up to 5 active rules per campaign. To change one, turn it off and add another.
  • Refused on a rate-card campaign, or one whose server postback reported the goal in the last 30 days.

Goals in code

freebuff()
// A conversion, in the success callback. value and plan are reported, never charged.
freebuff('conversion', 'subscription_started', {
  eventId: 'subscription_started:' + order.id,
  value: 49, currency: 'USD', plan: 'team_monthly',
})

// Any funnel step. Activity, not a conversion.
freebuff('track', 'pricing_calculator_used', { seats: 12 })
  • Names: signup_completed, trial_started, demo_booked, installation_completed, subscription_started, or your own snake_case.
  • eventId: your stable id, namespaced. Without one, repeats on the same click collapse to one.
  • Fire on success, not on a click. Do not double-report what your server reports.

Verify

  1. Deploy. Events shows the domains the tag was seen on.

  2. Verify → test click → do the real action. Watch for the Test event.

  3. Debug on your own site

    Add ?freebuff_debug=1 to any page, or run freebuff('debug') in the console. Logs locally, sends nothing extra.

What it records

Every visitor, under a random first-party id; a visit after an ad click also carries the click id. Text is scrubbed of emails, phones, keys and tokens before it leaves the page. The console's data level bounds all of it:

LevelAdds
Conversions onlyWhether the tag is installed on your site (a count per site, no visitor data); Conversions your rules or code report
StandardPages viewed, time on page and scroll depth; Form progress: started, submitted or abandoned, with field names but never what was typed; Video watching, downloads and chat-widget opens; Events you send yourself with freebuff('track', …); Page speed and the visitor’s cookie-consent choice
FullButton and link text, and links out to other sites; Code copied from code blocks (other copies record only their length); Site searches, error messages, and rage and dead clicks
Recorded and never recorded, by area
AreaRecordedNever
PagesOrigin, path (ids become :id), title, referrer originURL fragment, full referrer
Queryutm_*, ref, source, search terms, keys you allowEverything else (tokens live there)
EngagementVisible and active time, scroll depth, visit numberRecordings, snapshots
AnalyticsEvent names you send to GA4, GTM, Segment, PostHog, Meta, Reddit, TikTok, with value and planOther properties, identify and alias calls, user traits
ClicksButton and link text, outbound targets, rage and dead clicksid and data-* attributes
Copy and searchCode copied from code blocks, site searchesOther copied text (length only)
FormsStart, submit, abandon; field namesValues, keystrokes, passwords
JourneyVideo play and watch %, download names, chat opensChat text
HealthTTFB, load, LCP, error messagesStack traces
DeviceViewport, language, time zone, automation flag; country and UA added server-sideIP, other cookies, any email, phone or user id
Delivery and retries

Sends with fetch + keepalive, no cookies. Failed sends retry at 2, 10, 30, 60 and 120 s, up to five times within 24 hours, including on the next page load. Each batch has an id, so a resend never counts twice. Automated browsers are received but never count as landed or engaged.

Domains, pinned builds, CSP

  • Subdomains share the click id (widest domain, last click wins). For a different domain, add it under linked domains (up to 10) and install the pixel there too.
  • Using Google Tag Manager? Follow the GTM setup instructions.
Pinned build (never changes)
<script async src="https://freebuff.com/freebuff-tag/v2/ab6607d7e54f3501.js?t=YOUR_TAG_ID" integrity="sha384-RdCDlqAOAfMXKQCCv+9WCKhFNb08sdloLyXyDxQJzQXIWpWgrTtmfWZXjolZ1gsa" crossorigin="anonymous"></script>
Content-Security-Policy
script-src https://freebuff.com
connect-src https://freebuff.com