Event Resolution Field Catalog

API: GET /api/v1/events and GET /api/v2/events on apiv3.delivr.ai Service: Event Store Lookup Service (Rust/DataFusion) Schema endpoint: GET /api/v1/events_schema Last verified: 2026-04-12 Sources: Pixel (on-domain) and DSP (ad impression) events share enrichment fields but differ in core event fields.

---

Quick Reference

• Total schema fields: 132
• Max time window: 25 hours (end_ms - start_ms)
• Default limit: 300 rows
• Resolved on-domain events include identity + enrichment fields (person, company, demographics)
• Unresolved on-domain events include only core event fields (no person/company data)

---

Query Parameters

V2 Query Parameters

Filter Operators

Common Filters

resolved:eq:true                          # Only resolved events
resolved:eq:false                         # Only unresolved events
event_type:eq:page_view                   # Specific event type
event_type:eq:purchase|event_type:eq:refund  # Multiple event types (OR)
resolved:eq:true,first_name:ne:null       # Resolved with first name (AND)

Undocumented Query Parameters

---

Response Metadata

Every response includes a meta object:

---

Field Catalog

Fields are grouped by category. Population rates are based on a sample of 34 resolved events.

Legend:

• Rate: Percentage of resolved events where field is non-null
• Nullable: Whether the Arrow schema allows null values
• Resolved-only: Field is only populated when resolved=true

---

Core Event Fields

Always present on every event (resolved or unresolved).

Source-Specific Event Fields

Fields that differ between pixel and DSP events.

Pixel-Only Fields

Present only on pixel (on-domain) events. Null or absent on DSP events.

DSP Campaign Fields

Present only on DSP (ad impression) events. Null or absent on pixel events.

V2 Metadata Fields

Present on both pixel and DSP events when queried via v2 endpoints.

Network and Client Fields

Raw request data from the pixel capture.

DSP event_data: For DSP events, contains a JSON object with content (app_bundle, traffic_type), device (browser, os, carrier, connection_type, make, model), geo (city, country, lat, lon, postal_code, region), and pricing (advertiser_price, bid_price, win_price) sub-objects.

Identity Resolution Fields

Hashed email identifiers used for identity matching. Present on all resolved events.

Email Hashes (multiple algorithms and case variants)

Elixir-sourced Email Hashes

Duplicated from the Elixir identity graph with emails_ prefix. Populated only when full enrichment data exists.

Person Fields

Contact-level data from the Elixir identity graph. Resolved-only -- null on unresolved events.

Name and Identity

Email

Phone Numbers

Professional Profile

Social Profiles

Personal Address

Demographics

Company Fields

Firmographic data from the Elixir identity graph. Resolved-only.

Internal Identifier Fields

Used for identity graph linking and deduplication.

---

Selectable Fields

All 132 fields can be used with the select parameter. Full list for copy-paste:

event_id,pixel_id,organization_id,event_type,timestamp,ts_millis,cookie_id,hem,hems,
user_agent,client_ip,ip,event_data,headers,referrer_url,extra_json,resolved,
address_id,age_range,business_emails,company_address,company_address2,company_city,
company_country,company_description,company_domain,company_employee_count,
company_employee_count_range,company_id,company_id_right,company_industry,
company_linkedin_url,company_naics,company_name,company_name_history,company_phones,
company_phones_dnc,company_related_domains,company_revenue_range,company_sic,
company_state,company_total_revenue,company_zip_code,current_business_email,
current_business_email_validation_date,current_business_email_validation_status,
department,department_2,department_raw,direct_numbers,direct_numbers_dnc,domain_lc,
dpv_code,education_history,email,email_last_seen,email_validation_status,emails,
emails_md5_lc_hem,emails_md5_uc_hem,emails_sha1_lc_hem,emails_sha1_uc_hem,
emails_sha256_lc_hem,emails_sha256_uc_hem,first_name,first_uuid_norm,flattened_uuids,
gender,has_children,headline,income_range_lc,inferred_gender,inferred_gender_unisex,
inferred_years_experience,invalid_emails,is_email_business,is_email_personal,
is_homeowner,is_international,is_married,is_profile_b2b,is_profile_b2c,job_functions,
job_title,job_title_history,job_title_normalized,last_name,last_updated,linkedin_url,
md5_lc_hem,md5_uc_hem,middle_name,mobile_phones,mobile_phones_dnc,
mobile_phones_validation_date,mobile_phones_validation_status,net_worth,
personal_address,personal_address_2,personal_city,personal_country,
personal_country_alpha2,personal_country_alpha3,personal_country_numeric,
personal_email,personal_email_validation_status,personal_emails,personal_phones,
personal_phones_dnc,personal_state,personal_state_code,personal_timezone,personal_zip,
personal_zip4,phones,phones_dnc,photo_url,primary_contact_emails,profile_pid_all,
seniority_level,seniority_level_2,seniority_level_raw,sha1_lc_hem,sha1_uc_hem,
sha256_lc_hem,sha256_uc_hem,social_connections,subdepartments,valid_emails,twitter_url,
github_url,facebook_url,job_title_normalized

---

Notes

Population Rate Patterns

Fields fall into two tiers based on enrichment availability:

• 100% on resolved on-domain events: Core event fields (event_id, timestamp, cookie_id, ip, hem, email, user_agent, etc.) -- these exist for every resolved on-domain event
• ~24% on resolved on-domain events: Full enrichment fields (person demographics, company firmographics, phone numbers, etc.) -- only populated when the identity graph has a rich profile match via Elixir/HER

The 24% rate reflects on-domain events where only a HEM-to-email resolution occurred without full Elixir profile enrichment. The has_valuable_data=true query parameter can filter to only on-domain events with enrichment data populated.

Field Value Formatting

• Names: Stored and returned in lowercase
• Addresses, industries: Stored in lowercase, returned title-cased by the Events API (e.g., "florida" stored, "Florida" returned)
• Boolean-like strings: "y" / "n" or "true" / "false" (not actual booleans)
• Phone numbers: E.164 format with + prefix, comma-separated when multiple
• DNC fields: Positionally aligned with their phone counterpart (e.g., phones: "+1234, +5678" and phones_dnc: "n, y")
• JSON fields: event_data, headers, education_history are stringified JSON
• Hashes: Lowercase hex strings (MD5: 32 chars, SHA1: 40 chars, SHA256: 64 chars)
• Dates: Date32 fields use YYYY-MM-DD format; timestamps use ISO 8601 with microseconds

Endpoints Summary

DSP Event Types

DSP events have different event types than pixel events: