Skip to content
English
More support
Gamoshi.com
  • There are no suggestions because the search field is empty.

Setting Up Client-Side Web Conversion Tracking (No-GTM Method)

How to track full-funnel advertiser actions directly within your Gamoshi DSP account using native Client (Browser) Pixels and CSS selectors.

This guide explains how to track full-funnel advertiser actions (page loads, form submissions, and button clicks) directly within your Gamoshi DSP platform using native Client (Browser) Pixels and CSS selectors.

By using Gamoshi’s native event listening capability, you do not need Google Tag Manager (GTM) or any other third-party container tag installed on the advertiser's website.


Overview of the Flow

Instead of requiring separate code snippets for every user action, Gamoshi uses a single master script. Once deployed on the advertiser's site, this master script actively "listens" for user behaviors and communicates them back to your DSP dashboard based on rules you define using Page URLs and CSS selectors.


Step 1: Create the Conversion Script in Gamoshi DSP

Before tracking specific behaviors, you must generate the master tracking script inside your platform account.

  1. Navigate to your Gamoshi DSP dashboard.
  2. Go to the Conversions management section and click Add Conversion.
  3. Fill in the conversion Name and select the Advertiser from the drop-down list.
  4. Select the value Web in the Conversion Type dropdown menu.
  5. The Pixel Type radio button Client (Browser) Pixel should be on.
  6. Locate the Listen On Events toggle switch and turn it ON (Activated).
  7. Fill in the remaining required settings for the conversion profile and click Save.

Step 2: Define and Configure Your Conversion Goals

Once saved, a default goal is automatically generated under your new conversion profile. You can edit this default goal and create additional goals to build your conversion funnel.

For every goal you track, complete the following fields:

  1. Goal Name: Assign a clear, custom name (e.g., Signup Complete, Homepage Visit).
  2. Event Type: Choose the rule condition from the dropdown menu based on the user action:

Configuration Mapping Matrix - Examples


User Action

Event Type to Select

Field Configuration Required

Page View / Load


(e.g., Landing pages, static articles)

Page Load

In the Goal Page URL field, enter the exact URL string or pattern of the page you want to track.

Form Submission


(e.g., Registering, lead captures)

Form Submission

In the Goal Page URL field, enter the URL where the form resides (Note: Only use if the form submission stays on or is bound to that page).

Element/Button Click


(e.g., CTA clicks, video plays, file downloads)

Click Action

In the CSS Selector field, input the exact CSS value of the targeted element (e.g., #submit-btn or .cta-primary).


You can create a goal to track any CSS events on the relevant pages by using a custom event type or use the predefined event types to capture global events.

Step 3: Example Setup Framework

To help map out a campaign, here is a standard full-funnel implementation strategy.

Important: User journeys vary by site layout. Always validate the funnel structure with the advertiser. It is strongly recommended to involve a technical team member or developer from either your team or the advertiser's team to confirm site selectors before going live.

  • Goal 1: Homepage (Traffic)
    • Event Type: Page Load
    • Goal Page URL: https://advertiser.com/
  • Goal 2: Signup Start (Intent)
    • Event Type: Page Load
    • Goal Page URL: https://advertiser.com/signup
  • Goal 3: Signup Complete (Lead/Acquisition)
    • Event Type: Form Submission
    • Goal Page URL: https://advertiser.com/signup
  • Goal 4: Initial Deposit (Monetization)
    • If the user is redirected to a unique "Thank You" or confirmation screen post-deposit, use Page Load paired with that success URL.
    • If the user remains on the payment screen while the balance updates via an AJAX frame, use Form Submission or a Click Action on the deposit confirmation button selector.
    • Configuration Rule: This depends heavily on site architecture.

Step 4: Deploy the Code on the Advertiser Website
  1. Return to the conversion management interface in your Gamoshi account.
  2. Find your newly configured conversion row and click Copy main conversion script for web. (Actions column)
  3. Send this script block to the advertiser's web developer.
  4. Instruct them to embed this single script block into the global template header (<head>...</head>) or footer section of all pages on the website where event listening needs to take place.

Once the code is live globally, any trigger matching the rule conditions defined in Step 2 will automatically record back into your Gamoshi DSP reporting metrics.