Event Types Reference
Summary: The pixel captures 5 main event types: page views, clicks, scroll depth, text copies, and form submissions. Each includes different details in the event_data field. Resolved events also include full contact and company enrichment.
Overview
Every time a visitor interacts with your website, the Delivr pixel captures an event. Each event has a event_type field that tells you what the visitor did, and an event_data field with the details.
This page explains each event type, what data it captures, and when to use it.
Event Types
page_view
Fires when a visitor loads a page.
The page_view event is the most common event type (typically 50-60% of all events). Every page load generates one.
event_data fields:
| Field | Type | Example |
|---|---|---|
url | string | https://yoursite.com/pricing |
title | string | Pricing - YourSite |
referrer | string or null | https://google.com/search?q=... |
screen | object | {"height": 600, "width": 800} |
viewport | object | {"height": 1080, "width": 1920} |
timestamp | string | 2026-01-28T00:37:48.322Z |
When to use it:
- Find out which pages a visitor looked at
- Filter by URL to find visitors on high-value pages (pricing, demo, contact)
- Track referral sources
Example: Find resolved visitors on your pricing page
curl "https://api.delivr.ai/api/v3/events/resolution_full_profile?source=pixel&pixel_id=YOUR_PIXEL_ID&start_ms=START_MS&end_ms=END_MS&filter=resolved:eq:true,event_type:eq:page_view,event_data:like:/pricing&limit=50" \
-H "X-Api-Key: YOUR_API_KEY" \
-H "X-Api-Secret: YOUR_API_SECRET"The URL lives inside event_data, so event_data:like:/pricing is what narrows to the pricing page. See Filter on the page URL or a custom parameter.
click
Fires when a visitor clicks an element on the page (links, buttons, navigation items).
event_data fields:
| Field | Type | Example |
|---|---|---|
url | string | https://yoursite.com/ |
element | object | {"ariaLabel": null, "className": "btn-primary"} |
elementIdentifier | string | btn-primary cta-demo |
elementText | string | Request a Demo |
coordinates | object | {"x": 450, "y": 320} |
timestamp | string | 2026-01-28T01:16:37.151Z |
When to use it:
- See which CTAs visitors click on
- Track navigation patterns
- Identify visitors who clicked "Request Demo" or "Contact Sales"
scroll_depth
Fires when a visitor scrolls past a threshold on a page (25%, 50%, 75%, 100%).
event_data fields:
| Field | Type | Example |
|---|---|---|
url | string | https://yoursite.com/blog/post |
percentage | number | 51 |
threshold | number | 50 |
timestamp | string | 2026-01-28T01:53:42.355Z |
When to use it:
- Find visitors who read most of a page (not just bounced)
- Combine with
page_viewto identify engaged visitors on key content pages
Example: Find visitors who scrolled past 75% on any page
curl "https://api.delivr.ai/api/v3/events/resolution_full_profile?source=pixel&pixel_id=YOUR_PIXEL_ID&start_ms=START_MS&end_ms=END_MS&filter=event_type:eq:scroll_depth&select=event_data,first_name,last_name,company_name&limit=50" \
-H "X-Api-Key: YOUR_API_KEY" \
-H "X-Api-Secret: YOUR_API_SECRET"Then filter client-side for rows where event_data.percentage >= 75.
copy
Fires when a visitor copies text from your page.
event_data fields:
| Field | Type | Example |
|---|---|---|
url | string | https://yoursite.com/pricing |
text | string | Enterprise plan starts at $499/month |
textLength | number | 38 |
timestamp | string | 2026-01-28T16:43:33.323Z |
When to use it:
- Identify visitors copying pricing information (strong buying signal)
- See what content visitors are saving or sharing internally
form_submission
Fires when a visitor submits a form on your site.
event_data fields:
| Field | Type | Example |
|---|---|---|
url | string | https://yoursite.com/contact |
formId | string or null | contact-form |
formName | string or null | typeform |
formAction | string | https://yoursite.com/submit (native HTML forms only) |
formMethod | string | POST (native HTML forms only) |
formData | object | {"email": "[email protected]", "company": "Acme"} |
responseId | string | abc123 (Typeform only) |
submissionId | string | 9f2c... (HubSpot, Calendly, Tally, Drift) |
timestamp | string | 2026-01-28T01:16:37.151Z |
formName depends on the form tool. For a native HTML form it is the form's name attribute (or null). For an embedded tool it is the tool's name: typeform, hubspot, calendly, tally, or drift.
formData holds the submitted fields. Fields that look sensitive (passwords, card numbers, bank and government ID numbers) are replaced with *****. Values longer than 100 characters are cut off and end with .... An embedded tool's submission is recorded once per page.
When to use it:
- Find visitors who submitted a contact, demo, or signup form
- Tell which form tool a submission came from by reading
formName
Example: Find resolved visitors who submitted a form
curl "https://api.delivr.ai/api/v3/events/resolution_full_profile?source=pixel&pixel_id=YOUR_PIXEL_ID&start_ms=START_MS&end_ms=END_MS&filter=resolved:eq:true,event_type:eq:form_submission&select=event_data,first_name,last_name,company_name&limit=50" \
-H "X-Api-Key: YOUR_API_KEY" \
-H "X-Api-Secret: YOUR_API_SECRET"Supported form tools
| Tool | Captured | What the event carries |
|---|---|---|
| Native HTML forms | Yes, automatically | All submitted fields |
| Typeform (embedded) | Yes | formId and responseId. Answers and the email are not in the event. The email needs the webhook setup below |
| HubSpot forms | Yes, automatically | formId, submissionId, and the submitted fields |
| Calendly | Yes, for completed bookings | submissionId only. Calendly does not share the invitee's email with the page |
| Tally | Yes, automatically | formId, submissionId, and the answers |
| Drift chat | Yes, when a visitor gives their email | submissionId (conversation) and the email |
| Google Forms | No | Submissions cannot be captured from your page |
| Microsoft Forms | No | Submissions cannot be captured from your page |
For tools in the "No" rows, put the form on your own page (a native or supported embedded form) to capture it.
Typeform email webhook
Typeform embeds do not expose the visitor's email to the page. To identify the visitor from a Typeform submission, add a webhook in Typeform. The form needs an email question.
-
In Typeform, open your form and go to Connect > Webhooks.
-
Add a webhook with this URL, using your pixel's own host (the same host your pixel sends events to):
https://YOUR_PIXEL_API_HOST/pixel/core/api/typeform/webhook -
Turn the webhook on. No hidden field or signing secret is needed.
Delivr matches the webhook to the visitor by the Typeform response ID, in either order of arrival, within 24 hours.
Additional Event Types
The pixel can also capture these event types. They may not appear in every account depending on site configuration:
| Type | What It Captures |
|---|---|
search | Visitor used an on-site search bar |
video | Visitor played a video |
download | Visitor downloaded a file (for example, a PDF or a whitepaper) |
custom | Custom events sent via the pixel JavaScript API |
These fire when the corresponding visitor actions are detected. The event_data payload varies by type.
email_open
Recorded by the open pixel in your marketing emails, on an Email pixel. An open is not a site visit, so it is left out of visitor counts, visitor lists, audiences and exports. It is also left out of Events API results, unless your filter asks for it by name: event_type:eq:email_open or event_type:in:email_open;page_view.
An open carries the recipient's identity when its dlvr_et token is valid, plus these row fields:
| Field | Example | Meaning |
|---|---|---|
email_token_result | valid | Whether the token worked. See Troubleshooting. |
email_client_proxy | gmail | gmail or yahoo when their image proxy fetched the open, otherwise unknown |
email_message | spring_launch | The dlvr_msg campaign label from the open pixel, if you set one |
Gmail, Yahoo and Apple Mail fetch images through their own servers. Apple Mail does so when the message arrives. An open is therefore a weak signal. See Identify Email Recipients.
Filtering by Event Type
Use the filter query parameter with the event_type field:
filter=event_type:eq:page_view
You can combine filters. For example, resolved click events only:
filter=resolved:eq:true,event_type:eq:click
Email opens are left out of every query unless your filter names them, so to read them ask for them directly:
filter=event_type:eq:email_open
See the On-Domain Events API for the full list of filter operators.
Event Structure
What's in event_data vs. the Row Itself
The event_data field is a JSON string containing details specific to that event type (for example, the URL visited, the element clicked, or the scroll percentage).
The rest of the row contains the visitor's identity and company information -- but only if the event was resolved (meaning the visitor was identified). Unresolved events have the event fields but no contact/company data.
| Resolved? | What You Get |
|---|---|
| No | event_type, event_data, timestamp, cookie_id, user_agent, referrer_url, client_ip |
| Yes | Everything above, plus first_name, last_name, job_title, company_name, company_domain, personal_email, linkedin_url, and 100+ enrichment fields |
To get only resolved events, add filter=resolved:eq:true to your query.
Next Steps
- On-Domain Events API -- Full API reference for querying events
- High-Intent Visitors -- Build a daily lead list from pricing/demo page visitors
- Export Events to CSV -- Paginate and export visitor data
Updated 12 days ago
