What these fields are
When you connect AEvent to GoHighLevel, AEvent can push each registrant's event details into GoHighLevel contact custom fields. Every registrant then carries their own webinar time, date, and links on their contact record, so your GoHighLevel workflows can act on them.
You choose which AEvent field maps to which GoHighLevel custom field on the integration setup screen. This article explains what each field holds so you can pick the right one. The field names below are exactly what AEvent shows you in that mapping list.
Two things trip people up, so they are worth stating up front:
The timestamp fields hold a UNIX timestamp in seconds (a plain number like 1753120800). Use these when a workflow needs to calculate a time. They are not meant to be shown to a person.
The replay expiration fields describe when the replay ends, not when the event starts. Do not use them to schedule reminders for the live event.
Quick reference: use this for that
I want to... | Use this field |
Set the event start time in a workflow, drive a countdown, or run a "wait until" step |
|
Show the event time to the registrant in an email or SMS |
|
Build a readable date like "July 21, 2026" in copy |
|
Show the day of the week (for example "Monday") |
|
Do the same for when the replay expires | the matching |
Give the registrant their join link or replay link |
|
Event time fields: webinarTimestamp vs webinarTime
These two both describe when the event starts, but they are for different jobs.
webinarTimestampis the event start as a UNIX timestamp in seconds (a number). This is the field to map when GoHighLevel needs to do math with the time: set an event start date, drive a countdown, or fire a "wait until a date/time" step. It is time-zone neutral because a UNIX timestamp is the same instant everywhere.webinarTimeis the event start as human-readable text in the registrant's time zone. This is the field to drop into email or SMS copy so a registrant sees a friendly time. Do not try to run wait steps off this one.
Rule of thumb: if a machine reads it, use webinarTimestamp. If a person reads it, use webinarTime.
Date-part fields: year, month, day of month, day of week
These give you the pieces of the event date, each in the registrant's time zone. Combine them when you want to write a date in your own format:
webinarYear: the year (for example 2026)webinarMonth: the monthwebinarDOM: the day of the monthwebinarDOW: the day of the week (for example Monday)
For example, webinarMonth + webinarDOM + webinarYear renders a date like "July 21, 2026" in your copy.
Replay expiration fields: replay END, not event start
Each event-time field has a replay-expiration twin. These describe when the replay stops being available, so use them for replay-window reminders, not for the live event.
replayExpirationTimestamp: replay expiration as a UNIX timestamp in seconds (use for countdowns and wait steps about the replay window)replayExpirationTime: replay expiration as readable text in the registrant's time zone (use in copy)replayExpirationYear/replayExpirationMonth/replayExpirationDOM/replayExpirationDOW: the date pieces of the replay expiration
If a reminder is firing at the wrong moment, double-check you did not map a replayExpiration... field where you meant a webinar... field.
Link fields: joinURL and replayURL
These are links, not times.
joinURL: the registrant's personal link to join the live eventreplayURL: the registrant's personal link to watch the replay
Each link is unique to the registrant, so map these into contact custom fields and reference the contact field in your GoHighLevel emails and SMS.
Where you map these fields in GoHighLevel
On the AEvent integration settings screen you match each AEvent field to a GoHighLevel custom field, then click Update Settings. Here is what that mapping panel looks like:
