Skip to content

Events

BimBeau Privacy Analytics Pro Events screen showing event tracking configuration

Events screen for configuring and reviewing tracked interactions in BimBeau Privacy Analytics Pro.

Events are a BimBeau Privacy Analytics Pro feature that help you track specific actions, interactions, or page behaviors that matter to your website.

Use Events when page views and visits are not enough and you want to measure important user actions more precisely.

Good to know

Events are a Pro feature. If the Events settings or report are not visible, check that your Pro license is active and that your WordPress user has access to BimBeau Privacy Analytics Pro features.

What Events are for

Events help you answer questions such as:

  • How often do visitors click an important button?
  • How often is a specific page viewed?
  • Are visitors submitting or interacting with a form?
  • Which events should appear as dashboard KPIs?
  • Which pages, countries, cities, devices, browsers, or operating systems are associated with triggered events?
  • Are event actions running successfully?

Event examples

Common event use cases include:

  • tracking clicks on a contact button;
  • tracking clicks on a pricing or quote request button;
  • tracking views of a thank-you page;
  • tracking visits to a campaign landing page;
  • tracking form submission behavior;
  • monitoring important calls to action;
  • measuring interactions that support conversions.

Good to know

Events are most useful when they are tied to a clear business, content, or UX goal. Avoid creating too many events without a reporting purpose.

Event triggers

An event trigger defines when an event should be recorded.

Use a click trigger when you want to record clicks on a specific button, link, or interface element. Click triggers usually rely on a CSS selector that matches the target element.

Use a form submit trigger when you want to record form submission behavior. This is often better than tracking only a click on the submit button.

Use a page view trigger when you want to record visits to a specific page or URL pattern, such as a thank-you page or campaign landing page.

Click events

Click events are useful for buttons, links, navigation items, tabs, accordions, downloads, or calls to action.

Good click event examples:

  • a “Contact us” button;
  • a “Request a quote” button;
  • a “Download brochure” link;
  • a pricing CTA;
  • a phone link;
  • a newsletter signup button.

Important

Click events depend on the CSS selector you configure. If the selector is too broad, it may record unrelated clicks. If it is too narrow or changes after a redesign, the event may stop triggering.

Form submit events

Form submit events are useful when you want to track form submission behavior rather than simple button clicks.

For forms, a submit trigger is often more meaningful than a click trigger because a visitor can click a button without successfully submitting the form.

Good to know

If you track both a click and a form submission on the same form, you may create two separate event occurrences for one visitor action. Use this intentionally.

Page view events

Page view events are useful for important page visits.

Common examples:

  • a thank-you page after a form submission;
  • a booking confirmation page;
  • a checkout success page;
  • a pricing page;
  • a campaign landing page;
  • a gated content page.

Page view events are often easier to configure than click events because they rely on a target page or URL pattern rather than a CSS selector.

Event actions

Events can also include actions depending on your configuration.

An action defines what should happen when an event is triggered. For example, a tracking snippet action can run custom JavaScript when the event occurs.

Important

Only add event actions if you understand what the action does. Custom snippets can affect website behavior and should be reviewed carefully before being used on a live site.

Creating an event

  1. Open Events settings

    In your WordPress admin area, go to BimBeau Privacy Analytics → Settings → Events.

  2. Add a new event

    Create a new event and give it a clear label.

  3. Choose the trigger type

    Select whether the event should trigger on a click, form submission, or page view.

  4. Configure the trigger

    Enter the CSS selector, form selector, or target page pattern required by the selected trigger type.

  5. Decide whether it should appear as a KPI

    If the event is important enough for high-level monitoring, enable it as a KPI when available.

    On mobile layouts, open the event accordion to access the Include in KPI and Enable event toggles inside the event card.

  6. Save settings

    Save the event configuration.

  7. Test the event

    Visit the public page where the event should run and trigger the action as a normal visitor would.

Event KPIs

Event KPIs help you highlight important events in reporting views.

Use KPI slots for events that matter most, such as:

  • quote requests;
  • contact clicks;
  • form submissions;
  • booking starts;
  • pricing page views;
  • lead-generation actions.

Good to know

Keep event labels short and easy to understand. KPI labels should be clear enough to read quickly in a dashboard context.

Events report

The Events report helps you review triggered events over a selected period.

When event reporting is enabled and advanced tracking is allowed, the Triggered events table includes these columns. Some values may be unavailable if BimBeau Privacy Analytics cannot collect the related signal for an occurrence.

The Event, Channel, Country, and City selectors show the number of matching occurrences across the selected period. Each selector reflects the other active filters, while retaining alternative values for its own dimension. The Reset filters link clears these selectors and text search without changing the reporting period. Existing results remain visible while filtered data refreshes.

Field What it means
Label The event label or identifier
Event time When the event occurrence was recorded
Type The trigger type, such as click, form submit, or page view
Triggered page The page where the event occurred, or all pages for site-wide triggers
Country Geographic country information associated with the event, when available
City Geographic city information associated with the event, when available
Operating system The detected operating system, when available
Browser The detected browser, when available
Device The detected device category, when available
Details A view action for eligible trigger types, when available

Exporting events

Events exports are available from the Triggered events report header. The export action downloads the captured events list for the selected period and active filters. CSV, JSON, and Excel formats are available when report exports are available for the current Pro license and server environment.

Data handling

Exported event files may contain website activity, event context, and geographic or device information. Store and share exports according to your privacy policy and internal data handling rules.

Testing events

Always test a new event before relying on it for reporting.

Recommended test workflow:

  1. Open a private browser window

    Test as a normal visitor rather than only as a logged-in WordPress administrator.

  2. Grant or decline consent as needed

    If your setup requires analytics consent, test both the declined and accepted states.

  3. Trigger the event

    Click the target element, submit the form, or view the target page.

  4. Check Events reporting

    Return to BimBeau Privacy Analytics and check whether the event appears in the Events report.

  5. Adjust the configuration if needed

    If the event does not appear, review the selector, page pattern, tracking settings, and consent behavior.

Events usually depend on advanced tracking and your event configuration.

If your website requires consent for advanced analytics, your CMP should control whether the advanced BimBeau Privacy Analytics tracker is allowed to run.

Important

BimBeau Privacy Analytics is not a consent management platform. Make sure your CMP, privacy policy, and event configuration match your legal and operational requirements.

Choosing good event names

Good event names make reports easier to understand.

Use labels that are:

  • short;
  • specific;
  • action-oriented;
  • understandable by non-technical users;
  • consistent across similar events.

Examples:

Weak label Better label
Button click Contact button click
Form Quote form submit
Page Pricing page view
CTA Homepage CTA click

Avoiding event noise

Too many events can make reports harder to read.

Before creating an event, ask:

  • Will this event support a decision?
  • Will someone review it regularly?
  • Is it tied to a conversion, content goal, or UX question?
  • Can an existing report already answer the question?

Good to know

A small set of meaningful events is usually more useful than a large list of low-value interactions.

Troubleshooting events

If events do not appear as expected, check the following:

  1. Confirm Pro is active

    Events are a Pro feature. Make sure your Pro license or account connection is active.

  2. Check that Events are enabled

    Confirm that the event is enabled in BimBeau Privacy Analytics settings.

  3. Review the trigger configuration

    Check the CSS selector, form selector, or page pattern used by the event.

  4. Test as a logged-out visitor

    Your logged-in WordPress role or exclusions may affect whether your own activity is tracked.

  5. Review consent behavior

    If advanced tracking is blocked by your CMP, event tracking may not run.

  6. Check cache and script optimization

    Aggressive script delay, combination, or blocking rules can interfere with tracking scripts or event listeners.

Next step

Continue with PWA Stats App to learn about the dedicated Pro app-like analytics interface.