Event Setup
Last updated
Was this helpful?
With your Pixel ID and Conversion API activated, the next step is to define the events that JENTIS should send to Meta. Events describe what happened on your website (e.g., a purchase, a form submission, or a page view).
Before configuring anything in JENTIS:
Review your business requirements.
Decide which visitor interactions should be tracked (e.g., Purchase, Lead, AddToCart).
Ensure that legal aspects (e.g., handling PII) are considered.
Go to Meta Business Manager → Events Manager.
Select your Pixel ID.
In the Events Setup, choose which events to configure:
Standard events (e.g., Purchase, Lead, PageView)
Custom events (e.g., NewsletterSignup)
Each event requires parameters to provide additional context:
Standard Parameters (handled automatically by JENTIS if activated):
external_id (internal user reference)
fbc (Meta Click ID cookie)
fbp (Meta Browser ID cookie)
event_id (Deduplication-ID)
Optional Parameters (depending on business needs):
email (must be hashed)
phone (hashed)
ip_address, user_agent
product details (e.g., value, currency, content_ids)
Example configuration in Events Manager:
Meta requires PII values (e.g., email, phone) to be hashed before submission.
JENTIS will forward them as provided.
Always hash data client-side before pushing it to JENTIS.
Example (pseudo-code, do not run):
After configuring events:
Meta Events Manager will display each event.
Ensure parameters are received and mapped correctly.
Use the Test Event Code for real-time debugging before going live.
Now your events and parameters are defined in Meta.
Last updated
Was this helpful?
Was this helpful?
Event: Purchase
Parameters: value, currency, external_id, fbc, fbp, emailvar emh = sha256("mail@address.com");
_jts.push({
"track": "event",
"group": "fbpii",
"name": "purchase",
"emh": emh
});