Pixel Tracking

Pixel tracking lets you fire server-side conversion events to ad platforms (Facebook CAPI and TikTok Events API) when contacts reach specific statuses. This enables accurate attribution reporting without relying on client-side pixels.

How It Works

Pixel rules define:

• When to fire (trigger point)
• Where to send (platform and pixel)
• What to send (event name and value)

When a contact reaches the trigger status, VayaFlow automatically fires the conversion event with the contact's contact info, IP address, user agent, and platform click IDs (fbclid, ttclid, etc.).

Creating Pixel Rules

Navigate to the Marketing tab on a playbook.

Rule Configuration

• Rule Name — A descriptive label
• Trigger Point — When to fire:
  • Contact Qualified
  • Contact Delivered
• Platform — Facebook or TikTok
• Pixel — Select from your connected pixels (configured in Integrations)
• Event Name — The conversion event (e.g., Contact, Purchase, CompleteRegistration)
• Action Source — Where the conversion occurred: Website, Phone Call, Chat, or System Generated
• Event Value — Optional override for the conversion value and currency
• Fire Once — When enabled, the event only fires once per contact (prevents duplicate conversions)

Conditions

Optionally add conditions to only fire for specific contacts using the conditional rules builder. For example, fire only for contacts from a specific state or with a certain questionnaire answer.

Testing

Use the Test Fire button to send a test event:

1. Select the pixel rule to test
2. Optionally enter a Test Event Code from your ad platform's Events Manager
3. Fire the test event — it will appear in the platform's test events view without affecting production data

Firing History

The pixel tracking section shows a history of fired events with:

• Success/failure status
• Contact ID
• Pixel and event name
• Event value
• Timestamp

API

You can also fire pixel events programmatically via the Fire Pixel API.