Conversions API

Overview

Meta Conversions API in Kraya lets your team send lead and stage-based conversion events directly to your Meta Pixel. You can connect your Pixel, choose which CRM stages trigger events, and control which lead data is shared with Meta.

This feature is useful when you want better attribution in Meta Events Manager and more reliable conversion tracking than browser-only events.

What you can do

Connect your organization’s Meta Pixel using Pixel ID and Access Token
Enable or disable Event Tracking for your organization with one toggle
Map CRM stages to Meta event names (including custom event names)
Set event value using either a static number or a lead attribute
Set event currency per stage mapping
Send a test event from any saved stage mapping
Choose which user data and custom attributes are sent with each event
Automatically track mapped events on new lead creation and stage changes

How it works

Kraya provides a dedicated Meta Conversions API page in Integrations. Once connected, tracking is controlled by your stage mappings and the Event Tracking toggle.

Each mapping links a specific pipeline stage to an event name. When a lead is created in a mapped stage, or when a lead moves to a mapped stage, Kraya sends the configured event to Meta.

Kraya avoids duplicate tracking for the same lead and mapping, so returning a lead to the same previously fired stage-event combination does not send the same event again.

Step-by-step guide

Opening the feature

Go to Dashboard.
Open Integrations from the sidebar.
Click Meta Conversions API.
Confirm the page sections are visible:
- Connect Meta Pixel
- Map CRM Stages to Events
- Select Lead Data to Send

Connecting your Meta Pixel

In Connect Meta Pixel, enter your Access Token.
Enter your Pixel ID (numbers only).
(Optional) Enable Test Event Code and enter your test code.
Turn Event Tracking on from the top toggle when you are ready to send events.

Notes:

Access Token and Pixel ID are required for live/test sending.
Token visibility can be toggled (show/hide) while editing.
Connection settings save automatically when you finish editing fields.

Creating stage-to-event mappings

In Map CRM Stages to Events, click Add Event Mapping.
Select Pipeline and Stage.
Choose an Event:
- Pick Lead from the list, or
- Choose Custom and type your own event name.
Select Value Source:
- Static to send a fixed number, or
- Attribute to read value from a selected lead attribute.
Set Currency if needed.
Use the row status toggle to enable/disable that mapping.
Click the green check icon to save the new row.

Important behavior:

Existing saved rows auto-save as you edit them.
If required fields are missing, saving is blocked until completed.
The first default Lead mapping may be locked and not deletable.
Delete icon removes a mapping.

Sending a test event

Save at least one mapping row first.
Click the play icon in that row.
Wait for success or error feedback.

What to expect:

If a lead exists in that mapped stage, Kraya uses that lead for test payload.
If no lead exists in that stage, Kraya still sends a synthetic test payload.
If Meta rejects the event, you will see an error.

Selecting lead data to send

Go to Select Lead Data to Send.
In User Data, review checkboxes.
In Custom Attributes, choose optional attributes to include.
Selections save when toggled.

Important behavior:

Name, Phone, and Email are mandatory and always enabled.
lead_id (leadgen_id sent when available) is auto-included.
external_id (kraya lead_id) is auto-included.
Some user data options only appear or become selectable if that attribute exists in your organization.
If your org has no custom attributes, this section will show no available custom fields.

Settings and configuration

Event Tracking: Master on/off switch for sending events.
Access Token: Required Meta credential for API calls.
Pixel ID: Numeric Meta Pixel identifier.
Test Event Code: Optional; useful while validating events in Meta Events Manager.
Status (per mapping): Turns an individual stage mapping on or off.
Event name: Predefined or custom event name sent to Meta.
Value Source:
- Static: send fixed numeric value
- Attribute: read value from selected lead attribute
Currency: Optional currency code for mapped value.
User Data fields: Controls personal/event matching fields sent to Meta.
Custom Attributes: Extra lead attributes sent as custom event properties.

Role-based behavior

Admins: Can access and configure Meta Conversions API settings and mappings.
Members: Cannot configure this integration from the dashboard.

Limits and quotas

Meta Conversions API setup is available only where premium integrations are enabled for the organization.
A stage-event row must be complete before it can be saved/tested.
Static value supports positive values within standard numeric limits shown in the form.
Duplicate stage + event combinations are prevented.

Common edge cases

No lead exists in selected stage during test A test event can still be sent using synthetic payload data.
Lead moved back to a previously tracked stage-event The same stage-event combination is not sent again for that lead.
Attribute-based value points to non-numeric data Event still sends, but value is skipped.
A selected attribute is removed from your org later That mapping/data selection may reset and require re-selection.
Default Lead mapping appears locked This is expected in some organizations; it cannot be deleted from the table.

Troubleshooting

“Please configure Pixel ID and Access Token before sending a test event.”

Cause: Connection settings are incomplete.
Fix: Enter both fields in Connect Meta Pixel and retry.

“Please save the stage mapping before sending a test event.”

Cause: Test was triggered on an unsaved row.
Fix: Save the row first using the check icon, then test again.

“Validation failed” while saving stage mappings

Cause: Missing required fields, invalid value format, or duplicate stage-event combination.
Fix: Complete Pipeline/Stage/Event, correct value format, and remove duplicates.

Test event fails with Meta rejection

Cause: Invalid credentials, Pixel mismatch, or rejected payload.
Fix: Re-check Pixel ID, Access Token, and optional Test Event Code. Retry with a clean mapping.

Decision tree

If test event does not send → verify Pixel ID + Access Token → re-save connection
If connection is saved but test still fails → verify stage mapping is saved and enabled
If mapping is correct but Meta still rejects → verify credentials in Meta Events Manager and retry
If none of the above works → contact support with the exact error message shown in Kraya

FAQs

Do events fire only on stage changes? No. Events can fire both on new lead creation (when the initial stage is mapped) and on later stage changes.
Can I use custom event names? Yes. Choose Custom in the Event column and enter your event name.
Can I disable tracking without deleting setup? Yes. Turn off Event Tracking from the top toggle.
What happens if my value attribute is empty? The event can still be sent, but value is not included.
Can I map multiple stages? Yes. Add multiple rows in the mapping table.
Do I need to save manually every time? Existing rows generally auto-save on edit; new rows require confirming with the save icon.

Tips and best practices

Start with a test event code before enabling production tracking
Keep stage-event naming consistent with your Meta reporting conventions
Use static values only when consistent across leads; otherwise prefer attribute-based values
Keep required user data fields accurate in lead records for better Meta match quality
Periodically test one mapping after major pipeline/stage changes

Meta Lead Ad Forms — Capture Meta form leads into Kraya before conversion tracking
Dashboard — Stage movement workflows that trigger mapped events
Import Leads — Imported leads can participate in stage-based tracking once mapped
Webhooks — Additional outbound automation patterns alongside CAPI tracking