Custom Tracking in Alus Builder
Fire custom Meta events (Lead, Contact, etc.) from any button/CTA in the builder — no code.
Custom Tracking in Alus Builder
Beyond auto events (ViewContent, Purchase, etc.), you can fire custom Meta events from any button in Alus Builder. Useful for CTAs like "Register Webinar", "Contact Sales", "Download eBook", etc.
Setup steps
- Open the Builder editor (
/dashboard/[siteSlug]/pages/[pageId]/builder, template, or popup) - Drop a Button or Checkout Button element onto the canvas
- Click the element → Inspector opens on the right
- Scroll to the Meta Tracking section
- Fill the relevant fields, then Save
Available fields
- Event Name (
metaEvent) — pick from Meta standard events:Lead— lead-gen form submitCompleteRegistration— account / membership signupContact— contact click (WA, phone, email)Schedule— bookingSubmitApplication— application submitSearch— search submitFindLocation— location lookup- Or any custom name (e.g.
WebinarSignup)
- Event Value (
metaEventValue) — number, e.g.50000if a lead is estimated worth Rp50,000 - Event Currency (
metaEventCurrency) — defaultIDR - Content Name (
metaEventContentName) — descriptive label, e.g."Marketing 101 Webinar"
What happens on click
The Pixel JS fires:
fbq('track', 'Lead', {
value: 50000,
currency: 'IDR',
content_name: 'Marketing 101 Webinar'
});
Note: Builder custom events only fire from Pixel (browser). For CAPI as well, use Purchase/Subscribe which Alusio auto-handles.
Verify
After saving the Builder + publishing the page, open the public site → click the button → check Events Manager > Test Events (if Test Code active). The event should appear within seconds.
Tips
- Prefer Meta standard events when possible — Meta auto-recognizes them for optimization. Custom events work too but require Custom Conversion config in Events Manager.
- Set realistic values — Meta uses them for auto-bid and ROAS. Lead = estimated CPA target. Contact = non-transactional, leave empty.
- Never send PII in Content Name (name, email, phone) — Pixel JS leaks to other visitors' browsers via shared session contexts.