Analytics events

Stream the platform's product events — sign-ins, registrations, deposits, trades, and more — straight into a brand's own analytics tags, in real time and under stable, documented names. Your marketing team builds reports, conversions and audiences on top of them inside their own tools; no code change is needed per report.

Events are delivered to every analytics tag the brand has configured:

• Google Tag Manager — pushed to the container's data layer, where your team maps them to GA4 tags, conversions and audiences.
• Google Analytics — sent directly, so a brand running GA without a Tag Manager container still receives the full catalog.
• Meta Pixel — sent as custom events; a completed deposit also fires the standard Purchase event (value and currency) so ads value optimization works out of the box.

These controls live on the Tracking & SEO sub-tab of the brand editor's Client Zone tab, in the Analytics events card — directly under the Analytics tags card where the tag IDs themselves are configured. As with the rest of the editor, changes apply when you click Save in the header.

Prerequisites

• You are signed in to the Backoffice with a role that grants permission to manage brands.
• You have opened a brand from the brands list and selected Client Zone → Tracking & SEO.
• At least one analytics tag ID is configured on the Analytics tags card (a Tag Manager container ID, a Google Analytics measurement ID, or a Meta Pixel ID). Without one, the events card stays inactive — the stream has nowhere to go.

Video walkthrough

A short tour: switching the stream on, choosing event groups, the identity and exact-amounts controls, and the events arriving live as a trader signs in and deposits.

Transcript

• [00:00] Every brand on the platform can stream its product events straight into the broker's own analytics tags — GTM, Google Analytics, and Meta Pixel. In the brand editor, open the Client Zone tab, then Tracking and SEO.
• [00:14] This is the new Analytics events card. One master switch sends ninety-seven documented platform events — sign-ins, deposits, trades — to every tag configured above. No code change per report.
• [00:28] Events come in six groups with live counts: sign-in, registration, deposits, trading, markets, and navigation. Toggle a group off to keep its events out of the broker's container. Let's switch Navigation off, and save.
• [00:44] For identity, the platform sends the trader's account number only — never a name, email, or phone — so GA4 user-ID reporting works out of the box.
• [00:55] Exact deposit amounts put value and currency on the purchase event, for revenue reporting and value-based bidding. And the live preview shows exactly what the broker's container receives.
• [01:06] Let's switch Navigation back on, and save. Every group is live again.
• [01:11] Now the trader side. Sign in on the WebTrader, and the events start flowing.
• [01:17] Make a deposit, and watch the data layer: the sign-in, the identify call, and the deposit events arrive in real time, with the exact amount.
• [01:27] From here, marketing builds GA4 tags, conversions, and audiences on top. The full event reference ships with the platform docs. Configured per brand, in minutes.

Turn the stream on

The master switch — Send platform events to the brand's analytics tags — controls the whole stream. It is effective as soon as at least one tag ID is set above; with no tag configured, nothing is ever sent, regardless of the switch.

Choose event groups

The catalog is organized into six groups, each with its own switch and a sample of the event names it carries:

Group	What it covers
Sign-in & session	Sign-in attempts and outcomes, password resets, screen views
Registration	The signup funnel, from form view to account created
Deposits & withdrawals	The full money-flow lifecycle, transfers, and trading-account creation
Trading	Orders, positions opened and closed, position edits
Markets & watchlist	Instrument selection, favourites, chart engine choices, signals
Navigation & engagement	Menus, help center, live chat, support requests

All groups are on by default. Toggling a group off keeps its events out of every destination — useful when a brand's marketing only wants, say, the funding and registration funnels.

The trader's identity

Include the trader's account number sends a single identity signal after sign-in — to the data layer as an identify event, and to Google Analytics as the user ID — so GA4 user-ID reporting can stitch sessions per trader.

Only the account number is ever sent: never a name, an email address, or a phone number. Turning the toggle off also removes the account number from the few events that carry it as a parameter.

Exact deposit amounts

Send exact deposit amounts puts the exact value and currency on the completed-deposit event, enabling GA4 revenue reporting and Google Ads value-based bidding. It is on by default; switching it off sends privacy ranges (for example 100–500) instead. Either way, the platform's own internal telemetry only ever uses ranges.

The dark preview block at the bottom of the card shows a live example of exactly what the brand's container receives, and updates as you change the toggles.

Notes for the marketing team

• Suggested GA4 mappings: deposit_completed → purchase, user_logged_in → login, sign_up → sign_up. All other names are valid GA4 custom events as they are.
• Don't double-count page views: page_viewed fires on every screen change; if the GA tag's automatic page view is also on, pick one.
• Consent: the event stream itself is consent-inert — enforcement happens on the tags inside the brand's container, so the design is compatible with Google Consent Mode v2. Brands serving EEA traders should run their consent platform inside the container as usual.
• The signup conversion also fires independently of the group switches, so campaign attribution on registrations is never lost.