Connecting your Meta™️ Dataset (The artist formerly known as a pixel) to Seeka is super easy and can be done in under 30 seconds if you're fast.
This will allow browser and server events to be sent to Meta™️. All it requires is a "Dataset ID" and a "Conversions API token," which you'll find in Meta™️ Events Manager.
🚨 IMPORTANT🚨
Before we begin, please ensure that the Meta™️ dataset (pixel) is not already installed on your site. Learn how to check that here
Connecting your Meta™️ Dataset (Pixel) to Seeka
Open the Seeka App and navigate to Destinations
Make sure you're in the correct Organisation and Brand then click on the Connect Destination button.
Leave this browser window open and open a new tab or window.
Finding your Dataset ID
In a new open tab, log into your Meta™️ business Events manager.
You will see a list of your datasets (pixels) on the left.
Please select the dataset you'd like to connect to Seeka.
On the right of the central menu, select the "Settings" tab.
The Dataset ID will be listed under the "Dataset ID" label. Click the number to copy the ID to your clipboard.
Paste this number into 'Dataset ID' field in the Seeka App.
Ensure 'First-party cookies' and 'Automatic advanced matching' are on.
Remain on the settings tab and scroll down to the website settings section.
Make sure First Party Cookies is on ✅
Then turn the Automatic Advanced Matching toggle to on ✅
If you have Meta™️'s built-in Event Setup Tool on, turn it off ❌
(You will be setting up any events created with this tool using Seeka)
Generate Access Token
Scroll down until you see a blue Generate Access Token button.
Click the button and wait for the access token to generate.
Copy the token, paste it into the 'Access Token' field in the Seeka App, and push connect.
Setting up Events (Optional)
All standard events are automatically set up for certain platforms, including Shopify, Woocommerce and Oztix.
WordPress, GoHighLevel, and Custom Sites sites will require manual event setup, as only the 'View Page' event is automatically set up.
The great news is that Seeka has an Express Setup Tool for super fast generation of web events, including triggering web events from elements such as:
Forms
Buttons
Accordions
Specific Pages
Tables
The Express setup tool is one of the highlights of the Seeka Product, and we encourage you to check the detailed article on it HERE.
Turning off the Meta™ Event Tool
Seeka cannot detect any events set up using the Meta™ Browser Setup tool and vice versa. Any events you rely on that have been set up using Meta™'s tool will need to be rebuilt using Seeka's Express Setup Tool for them to fire and to avoid double event fires.
Rebuilding these events using Seeka will provide a superior data flow for those events and map them to all other platforms connected.
How to turn off the Meta™ Browser Event Tool
Navigate to the Events Manager
Hit settings
Scroll down to Event setup
Turn the toggle off
How to check if your pixel is already installed on your site independent of Seeka 🧐
There is ZERO benefit to having a pixel installed via another method while using Seeka.
If the same pixel that Seeka is sending data to as a 'destination' is also installed independently of Seeka, the following conflicts will most likely occur:
The double firing of events
Platform errors
A decline in campaign performance
A decline in event match quality
Incorrect attribution
The easiest way to check is to download the Meta™️ Chrome pixel helper extension HERE. The installation will allow you to view the pixel and events of any Meta™️ Dataset (pixel) if set up on any website.
Checking for a pixel before setting up Seeka
When using the Meta™ pixel helper tool to check for an installed pixel, you will see your pixel listed as per the example below if it is installed on your site.
Checking for a duplicate pixel after connecting Meta™ to Seeka as a destination
When using the Meta™ pixel helper tool after you have connected Meta™ to Seeka as a data destination, if you see two fires of the same Pixel ID, as shown in the example below, you have the pixel installed on the page twice and need to remove the non-Seeka installation.
v
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;k