Conversion
Conversions
The screen Conversions centralizes the operational and marketing events triggered in Hablla — creation/update of records, status changes, actions on cards, among others. It works as an auditable log for observability and troubleshooting: you follow the timeline, apply filters and can inspect the raw payload (JSON) of each event.
⚠️ The list of events evolves continuously. New types may be added and some names may change as the product improves.
How to read the timeline
Each row displays:
Event type (e.g.: Conversion, Created a person).
Context/entity (e.g.: person, card, user, organization).
Summary message with what happened.
Date and time (timestamp).
Actions:
JSON → opens the event's full payload.
See updated data / Old data → when there is a before/after comparison.
Filters
Use the button Filters (top right corner) to refine the timeline by:
Event type
Period (date and time)
Source (when applicable)
Entity (person, card, etc.)
Period (Date and Time)
Allows restricting events by a precisetime range, combining date and time.
Fields:
Start date and Start time
End date and End time
Behavior:
The interval is inclusive: events with a timestamp exactly at the start/end time are also included in the results.
If you do not fill in the times:
Start time it assumes
00:00End time it assumes
23:59
Validation prevents end date/time earlier than the start.
The timezone used is the timezone configured in the workspace.
Quick examples:
“Today, from 09:00 to 12:00” → find morning conversion peaks.
“Yesterday, 18:00 to Today, 09:00” → monitor effects of nighttime campaigns.
“Last 7 full days” → Start date = today−7, Start time =
00:00; End date = today, End time =23:59.
Tip: combine Event type + Period to speed up diagnostics on campaigns and integrations.
Event types (displayed on this screen)
Below are the events listed for this page. New events may appear over time.
Conversion
Record of a conversion (e.g.: form, flow, short-link with UTM) linked to a person/lead.
Measure performance, campaign attribution and acquisition journey.
Created a person
A new contact was added to the database.
Confirm ingestion of leads (spreadsheet, API, form, webhook etc.).
Changed the data of
Registration data/attributes of a person were updated.
Audit the source of updates and understand when and who changed a critical field.
Deleted a person
A contact was removed.
Track database cleanses, GDPR/consent or batch adjustments.
Blocked
Person/entity marked as blocked for some flow/channel.
Investigate why a contact stopped receiving communications.
Unblocked
Removal of the blocked status.
Restore eligibility for campaigns and flows.
Other messages you may see (depending on your workspace): updated/moved card, task created, removed tag, dictionary data updated. These events follow the same logic: summary + time + action to open the JSON.
Inspecting the event JSON
Click on JSON to open the raw payload. This is essential for:
Validate variables and IDs used in flows/integrations.
Check before/after of an update.
Reproduce scenarios in test environments.
Best practices: when opening the JSON, look for
id/external_id,origin,timestamp,before/afterand sensitive business fields (e.g.:stage,labels,owner).
Recommended use cases
Campaign attribution: validate if a Conversion came from a short-link with the correct UTM.
Data quality: audit mass updates (e.g.: “Changed the data of”).
Support and CX: explain why a contact blocked/unblocked and when that occurred.
Commercial operations: track card movements and task creation linked to the person.
Limitations and evolution
The nomenclature and set of events may change with new releases.
Some events depend on permissions and integrations enabled in the workspace.
Summary
The screen Conversions is your audit panel for conversational marketing and operations. Use filters to isolate what matters, open the JSON to see technical granularity and ensure end-to-end traceability — from the conversion origin to the contact's status.
Last updated
Was this helpful?