Skip to main content

Track events and identification with GTM

Updated over 3 weeks ago

With the Triggerbee Event Logger Template, you can easily send goals and purchase events to Triggerbee from Google Tag Manager, using your existing data layer variables.

Key features include:

  • Log Goals with or without identification: Track key customer journey events like "Add to cart", "Initiated checkout", and "Registered membership". Add identification for the events that capture the visitors' email address (such as Logins).

  • Log Purchases and Revenue: Purchases can also be tracked, together with revenue data, order ID, coupon codes, and customer details. Revenue is useful for attributing your campaigns.

  • Compatible with your existing GTM Variables: Use data variables from your existing GTM setup to send revenue and order details.

How to work with the Event Logging Template

The Event Logging Template consists of three event types:

  • Goal

  • Goal with Identification

  • Purchase

Each of these event type have different parameters. Goals only have a goal name, since that's all you need to track a basic event in Triggerbee. "Goal with identification" is useful for logging events where you'll also have the email address of the visitor, such as when they log in or register for a membership. And the Purchase event is what it sounds like, to track a purchase together with revenue and order data.

You can also add Custom goals, which can be anything you wish to track. A click on a button, a visit to a certain page, or a specific behaviour that you have a trigger for in GTM.

Note: You do not need to declare any events in Triggerbee before adding it in Google Tag Manager - they will be automatically created.

Best practice:

  • Always use Event Type "Goal with identification" for events where you have an email address. Identification of visitors is key in building great audiences in Triggerbee.

  • Use Event Type "Purchase" for purchases (and not just a goal 'completed purchase'), and make sure to log Revenue. By logging revenue, you can attribute order values to campaigns, making it possible to quickly see ROI from your work.

Note: Purchase events should only be logged once, and all goals should be logged in separate tags. If you want to log Purchase (Event), Add to Cart (Goal), and Logins (Goal with Identification), create 3 separate tags that fire on separate events.


How to add Events in GTM

Step One. Install the Triggerbee Event Tracking template

Start by adding the Triggerbee Event Tracking template as a Tag Template in GTM. You will find the template in the Community Template Gallery in GTM by searching for Triggerbee.

Step Two. Add an Event

Once you have installed the Event Logging Template, go to your Tags in the left menu and create a new tag. Select the Event Logging Template as the tag type.

Add a basic goal

  1. Select the goal type "Goal"

  2. Add what goal to log, either from the dropdown of default goals, or by entering a custom goal name.

  3. Lastly, add a trigger to control when this event fires. Likely, you are already sending some events to Google Ads, GA4, or Meta using custom triggers, you can use the same triggers for Triggerbee.

Add a goal with Identification

For events where you may also capture the visitors email address, such as Logins - you should use the event type "Goal with identification", which will let you pass the email address of the visitor together with the event to Triggerbee.

  1. Select the goal type "Goal with Identification"

  2. Add what goal to log, either from the dropdown of default goals, or by entering a custom goal name.

  3. In the Customer Email field, add the variable containing the email address of the visitor

  4. Lastly, add a trigger to control when this event fires. Likely, you are already sending some events to Google Ads, GA4, or Meta using custom triggers, you can use the same triggers for Triggerbee.

Add a Purchase Event

Use the event type "Purchase" to log completed purchases to Triggerbee. You may also insert your variables for revenue, transaction ID, and user email.

We highly recommend you insert your variable for revenue to send revenue data to Triggerbee. All fields are optional, but without revenue data, you will not be able to attribute revenue to your campaigns.

  1. Select the goal type "Purchase"

  2. Add variables for Revenue, Transaction ID, Coupon Code and Customer Email. The most important ones are Revenue and Customer Email.

    Note: The revenue variable can contain decimals, but make sure to separate with dots - not comma. Ie. 49.9 and not 49,9

  3. Add a trigger to control when this event fires. We recommend you use a custom event for purchases, since it's an event sent to the data layer. Likely, you are already sending some events to Google Ads, GA4, or Meta using custom triggers, you can use the same triggers for Triggerbee.



Did this answer your question?