Changing Event Mappings

In the Settings tab of your tracking container, the Standard and Custom Events table gives you a full overview of all current event mappings and lets you remap events per Connector.

The Table Layout

The table is split into two sections by a horizontal divider:

• Above the devider Standard Events (Tracklution’s pre-set events)
• Below the devider Custom Events, which Tracklution automatically picks up the first time they appear in your incoming data

On the right side of the vertical divider, you’ll see a column for each of your active Connectors. By default, only active Connectors are shown. Use the Select visible events and Select visible connectors controls in the top-right corner of the table to adjust which rows and columns are displayed — useful if you have a lot of events or Connectors and want to focus on a specific subset.

If the table extends further to the right than what’s visible, a blue clickable arrow button on the right edge indicates there’s more to see, click or scroll horizontally.

Editing Event Mappings

To remap an event, click Edit on the relevant row and update the event name under the Connector column(s) you want to change, then click Save.

Example: To send the Purchase event to Meta as CustomEvent1, find the Purchase row, click Edit, update the name in the Facebook column to CustomEvent1, and save.

If you leave an input field empty and save, it will revert to the default mapping value for that event.

GA4: Switching Between Server and Pixel

The Google Analytics 4 column has an extra option not available on other Connectors where you can switch each event between two tracking modes:

• Measurement Protocol (server-side) sends the event directly from Tracklution’s server to GA4
• gtag (pixel) sends the event via the browser-side GA4 tag

You can toggle this per event, giving you fine-grained control over how each event reaches GA4. For most setups, Tracklution’s automatic detection for when to use server-side via Measurement Protocol is all you need, but the setting is available for customizability.

Blocking Events

To prevent an event from being sent to a specific Connector, enter block as the event name for that Connector and click Save. The value will be highlighted in the table as a visual reminder that the event is blocked for that Connector.

Deduplication

The Deduplicated column shows whether server-side deduplication is enabled for each event. When active, Tracklution tracks/counts the event once per occurrence, for example if the same purchase is sent multiple times, the duplicates will be filtered out automatically.

This does not mean a user can only trigger an event once. A real customer making two separate purchases will have both tracked correctly. Deduplication uses multiple signals in the server and well tested logic to detect duplicates, preventing the event from being counted multiple times in your ad platforms.