Understanding Pixel Implementation
Seeka uses first-party tracking, meaning it collects data directly as the website owner rather than through third-party pixels. When using Seeka, it's important to understand how pixels are implemented:
Seeka installs all connected pixels across your entire website.
Pixels are installed on every page and can’t be filtered to only appear on certain URLs.
Each brand can have multiple pixel connections.
The same events will fire for all connected pixels.
On eCommerce and ticketing platforms, Seeka will automatically fire the events the platform includes in the purchase funnel.
Example: view content, add to cart, initiate checkout, purchase.
For lead generation, you will need to manually set up the events you want to fire. To achieve this in the easiest way, we created our Express Setup tool, which allows basic users to set up complex events in a few clicks.
In Go Hi Level, Seeka will automatically track:
On all pages
Page view event.
Identity tracking occurs when a user submits a form.
On checkout pages
Add a payment method event when the user completes the Stripe payment details.
The current GoHighLevel™ cart is automatically collected to feed to auto-tracking events and events set up via the Express Setup tool.
An order/purchase event including items in the order.
On calendar booking flows
ScheduleTimeSelected custom event when a time slot is selected.
ScheduleDateSelected custom event when a date is selected.
Schedule event when a user completes the booking form.
What This Means For You
Plug and Play Setup: Seeka provides a seamless, no-code solution you can set up in minutes.
Complete Data Collection: Every customer interaction is tracked, giving you a full picture of how visitors interact with your site.
Consistent Reporting: All your marketing platforms receive the same accurate data, so you can rely on the data you see to make decisions while also improving your campaign performance.
Duplicate Firing Events: Causes & Fixes
Double firing pixel events are the most common implementation issue. They typically occur when a pixel is firing more than once for a single customer action.
Common Causes of Duplicate Firing Events
Manual pixel implementation alongside Seeka, such as via Google Tag Manager or code directly embedded into the site (common with older sites).
Duplicate event triggers set up in Seeka.
Duplicate fires triggered by the incorrect setup of another pixel that isn’t configured to fire as ‘track single’.
Solutions by Scenario
1. Duplicate firing events caused by manual pixel implementation alongside Seeka
To fix double-firing events, simply remove any pixels installed in Seeka that are installed on your website. This applies to both websites and GHL funnels. A second pixel with a different ID correctly installed on the site will not cause double fires.
Important: Installing the same pixel via another method and also installing it in Seeka has zero benefit. In fact, it can create data conflicts and inaccurate reporting.
Follow these steps to check and remove any pre-installed pixels on your website that are also installed in Seeka.
2. Duplicate firing events caused by duplicate event triggers set up in Seeka
This often happens when events are mistakenly set up multiple times via the Express Setup Tool. Fortunately, these duplicate triggers are easy to fix.
To remove or edit duplicate event triggers:
Open the Seeka App.
Launch the Express Setup Tool.
Locate the event you want to modify.
Click the three dots in the blue box to the right of the event.
Select Delete to remove the duplicate trigger.
Click Save.
Note: Changes made in the Express Setup Tool will take effect within 15 minutes.
3. Duplicate fire events caused by incorrectly configured ’track single”
In this instance, the pixel will fire its event at all pixels on the page. This is the most common form of a ghost event that isn’t set up in Seeka but still results in Seeka firing an event due to misconfiguration.
To fix this, update the event code for the third-party pixel usually in Google Tag Manager or your site’s source code to use track single mode. This ensures the event only fires for that pixel and doesn’t unintentionally trigger the pixels installed by Seeka.
Update the event code so it uses a track single configuration.
Example before:
Example with trackSingle where 11232213421 is the ID of the Meta pixel:
This ensures the event only fires for the intended pixel and doesn’t cascade to others (like Seeka).
If using GTM, double-check the event tag settings and ensure it's not firing globally.
Best Practices
Ensure there are no pixels already installed on your website or funnel that Seeka will be installing - you can check by following the steps in this article: https://support.seeka.co/en/articles/8605730-how-to-check-if-a-pixel-is-already-installed-on-your-website
Monitor event firing in real-time using Seeka’s diagnostic tool and pixel helpers in your browser.
For complex funnels, create a funnel map in a spreadsheet first. This resource will become your checklist for both setup and ongoing testing.
Verification Steps
To verify proper pixel implementation:
Use Seeka’s diagnostic tool to easily test your events by navigating your customer journey and watching the events stream into the event log.
Use browser developer tools like Chrome Pixel Helper.
Monitor Events Manager for your connected pixels.
Getting Help
If you continue experiencing issues:
Review your Express Setup configuration
Check pixel connections in Seeka
Document when/where double firing occurs
Contact support@seeka.co with specific examples, and our team will be happy to assist!