For a technical document on the our schema, please see our full Endgame schema documentation: Endgame Schema
Endgame is highly customizable to align with your unique product and go-to-market strategy. While every product and business is different, there are a number of key data points we see many of the most successful PLG customers leveraging within Endgame. We’ve highlighted required fields and some best practices fields below:
Event Type | Field |
group / account | Account Id ⭐️ Required
Domain ⭐️ Required
Name ⭐️ Required
Plan Name ⭐️ Required
Created at
Trial start date
Trial end date
# Paid licenses
# Active users
% Active users / entitled seats (30d)
% Seats used / entitled seats
BDR owner
AE owner
CSM owner
Has open opportunity
# of open renewal opps
Last sales activity
Sales segment (SMB, MM, ENT)
Renewal date
Close date
Opportunity close date
Customer as of
Region
Country
# Employees
Industry |
identify / account_user | User Id ⭐️ Required
Account Id ⭐️ Required
Domain ⭐️ Required
Name ⭐️ Required
Email ⭐️ Required
Created at
Role
Title
Seat type
Link to search on Linkedin
Find prospect in Outreach |
track / event | User Id ⭐️ Required
Account Id ⭐️ Required
Domain ⭐️ Required
Viewed/edited billing page/settings
Sent invite
Used core product feature
Onboarding completion
Viewed documentation |
How Endgame uses your data to empower sales teams
Endgame supports various ‘last mile transformations’, such as:
- Time-bounding data (e.g. the number of invites sent within last 5 days)
- Period-over-period change (e.g. seat count change month-over-month)
- Calculated fields (e.g. number of active users within last 7 days divided by seat count)
To utilize these transformations, you need only send the raw events (e.g. invite sent) and raw properties (e.g. current seat count).
Have questions?
Reach out to us at support@endgame.io!