{{venue.description}}

Description of the venue in use.

{{agenda.0.endTime}}

String of date and time formatted in UTC Timezone. Eg: “2021-06-24T08:35:00.000Z”.

{{agenda.0.logos}}

URL of the logos.

{{venue.name}}

The name of the venue.

{{agenda.0.projectShowcase.showcaseSlug}}

Session livepage of the agenda, appended with a token to ensure value is unique. Eg: Session Livepage: Project –> showcaseSlug: Project-cbdnxU80.

{{agenda.0.speakers}}

Speakers that are relevant to the agenda on a specific livepage. For full description, click here.

{{agenda.0.startTime}}

String of date and time formatted in UTC Timezone. Eg: “2021-06-24T08:35:00.000Z”.

{{project.baseUrl}}

[Deprecated] Represents the URL to the folder of template being loaded

{{project.partials}}

List of HTML codes for partials which are used for rendering preset components on the page, the keys are the name of the html files.

{{setting.backgroundImage}}

The URL of background image.

{{livepage.hasCustomBackground}}

Under livepage settings, if Use a custom background image is selected, this field will be true.

{{livepage.hasCustomLogo}}

Similar to hasCustomBackground.

{{venue.id}}

The ID of the venue.

{{livepage.isPublic}}

Indicates whether the livepage is public.

{{livepage.isPublished}}

Indicates whether the livepage is published.

{{sponsor.logo}}

Logo of the company that sponsors.

{{livepage.showcaseblocks}}

Shows all the details about each block in the livepage. One example for Rich Text block is shown here. You may refer to other block types under Experience JSON tab.

{{livepage.showcaseblocksweight}}

Similar to showcaseblocks. However, the main difference is that for showcaseblocks, the type is in array of objects, with all the showcaseblocks being ordered based on how they are configured.

{{livepage.slug}}

The uniquely identifiable URL slug of the livepage. To generate the full URL of a page, you can use: Rebar Syntax: {{project.rootUrl}}/{{livepage.slug}} Javascript Syntax: window.GEVME.project.rootURL + "/" + window.GEVME.livepage.slug

{{livepage.title}}

The title of the livepage.

{{project.baseUrl}}

[Deprecated] Represents the URL to the folder of template being loaded

{{project.companyId}}

The ID of the company.

{{venue.id}}

The ID of the venue.

{{venue.name}}

The name of the venue.

{{project.partials}}

List of HTML codes for partials which are used for rendering preset components on the page, the keys are the name of the html files.

{{project.rootUrl}}

The root URL of a project. Eg. www.gevme.com/page or customdomain.com/page. Does not end with backslash.

{{setting.backgroundImage}}

The URL of background image.

{{setting.customDomain}}

URL of the custom domain.

{{setting.header}}

Contains attributes for header settings.

{{setting.livebar.closable}}

{{setting.livebar.positionLeft}}

{{setting.livebar.positionRight}}

{{setting.livebar}}

Contains attributes for livebar settings.

{{setting.loginOption.custom}}

{{setting.loginOption.google}}

{{setting.loginOption.microsoft}}

{{setting.loginOption.sharedPassword.enable}}

{{setting.loginOption.sharedPassword.value}}

{{setting.loginOption.sharedPassword}}

{{setting.loginOption.sms}}

{{setting.loginOption}}

Contains attributes for login options.

{{sponsor.logo}}

Logo of the company that sponsors.

{{setting.registrationUrl}}

{{setting.textColor}}

Hex code for the default text color.

{{speakers.0.bio}}

Biography of speaker, in HTML format. Eg: “<p>Biography</p>”.

{{user.company}}

Company of user.

{{user.firstname}}

First name of user.

{{user.jobTitle}}

Job title of user.

{{user.lastname}}

Last name of user.

{{speakers.0.profilePhoto}}

URL of the speaker’s profile picture uploaded.

{{sponsor.code}}

Unique ID when creating the sponsorship company.

{{sponsor.custom1}}

Custom fields that the company would want to add in the sponsorship.

{{sponsor.custom2}}

Custom fields that the company would want to add in the sponsorship.

{{sponsor.custom3}}

Custom fields that the company would want to add in the sponsorship.

{{sponsor.custom4}}

Custom fields that the company would want to add in the sponsorship.

{{sponsor.custom5}}

Custom fields that the company would want to add in the sponsorship.

{{venue.description}}

Description of the venue in use.

{{venue.id}}

The ID of the venue.

{{sponsor.isBookmarked}}

Checks if the sponsorship is bookmarked.

{{sponsor.logo}}

Logo of the company that sponsors.

{{venue.name}}

The name of the venue.

{{user.projectId}}

Project ID related to the event.

{{sponsor.socialMediaLinks.0.label}}

{{sponsor.socialMediaLinks.0.url}}

{{sponsor.socialMediaLinks}}

Any social media links such as Twitter, Instagram, Website, etc. Full for description, click here.

{{sponsor.sponsorPackageId}}

If sponsorship is linked to any package, sponsorPackageId will contain the id of the package.

{{sponsor.tagline}}

Optional tagline for the company.

{{template.baseURL}}

Base URL of folder to template

{{venue.name}}

The name of the venue.

{{user.company}}

Company of user.

{{user.firstname}}

First name of user.

{{venue.id}}

The ID of the venue.

{{user.jobTitle}}

Job title of user.

{{user.lastname}}

Last name of user.

{{user.projectId}}

Project ID related to the event.

{{venue.active}}

{{venue.description}}

Description of the venue in use.

{{venue.experience}}

Contains attributes for the experience being used.

{{widgets.0.features}}

Each type of widget has multiple features. For example, live-bar widget has 7 different features whereas a header widget has only 3 features.

{{venue.gallery}}

List of sample preview pictures of the venue.

{{venue.goodFor}}

Suggested usage of the venue.

{{venue.id}}

The ID of the venue.

{{venue.isEditable}}

{{venue.name}}

The name of the venue.

{{venue.sdkBaseUrl}}

The URL of sdk.

{{venue.source}}

Source of the venue. e.g.”github”.

{{venue.thumbnail}}

The URL of the thumbnail image file.

{{venue.version}}

The version number of the venue.

{{widgets.0.features}}

Each type of widget has multiple features. For example, live-bar widget has 7 different features whereas a header widget has only 3 features.

{{widgets.0.featuresOrdering}}

Indicates if the list of features are being ordered in the array.

{{widgets.0.inputs}}

{{widgets.0.options}}

{{widgets.0.position}}

Field is only available when widget is of type: “live-bar”. Position can be “right” or “left”, etc.

{{widgets.0.widget}}

There are 3 types of widgets: “live-bar”, “header”, and “menus”.

{{venue.description}}

Description of the venue in use.

{{agenda.0.endTime}}

String of date and time formatted in UTC Timezone. Eg: “2021-06-24T08:35:00.000Z”.

{{agenda.0.logos}}

URL of the logos.

{{venue.name}}

The name of the venue.

{{agenda.0.projectShowcase.showcaseSlug}}

Session livepage of the agenda, appended with a token to ensure value is unique. Eg: Session Livepage: Project –> showcaseSlug: Project-cbdnxU80.

{{agenda.0.speakers}}

Speakers that are relevant to the agenda on a specific livepage. For full description, click here.

{{agenda.0.startTime}}

String of date and time formatted in UTC Timezone. Eg: “2021-06-24T08:35:00.000Z”.

{{project.baseUrl}}

[Deprecated] Represents the URL to the folder of template being loaded

{{project.partials}}

List of HTML codes for partials which are used for rendering preset components on the page, the keys are the name of the html files.

{{setting.backgroundImage}}

The URL of background image.

{{livepage.hasCustomBackground}}

Under livepage settings, if Use a custom background image is selected, this field will be true.

{{livepage.hasCustomLogo}}

Similar to hasCustomBackground.

{{venue.id}}

The ID of the venue.

{{livepage.isPublic}}

Indicates whether the livepage is public.

{{livepage.isPublished}}

Indicates whether the livepage is published.

{{sponsor.logo}}

Logo of the company that sponsors.

{{livepage.showcaseblocks}}

Shows all the details about each block in the livepage. One example for Rich Text block is shown here. You may refer to other block types under Experience JSON tab.

{{livepage.showcaseblocksweight}}

Similar to showcaseblocks. However, the main difference is that for showcaseblocks, the type is in array of objects, with all the showcaseblocks being ordered based on how they are configured.

{{livepage.slug}}

The uniquely identifiable URL slug of the livepage. To generate the full URL of a page, you can use: Rebar Syntax: {{project.rootUrl}}/{{livepage.slug}} Javascript Syntax: window.GEVME.project.rootURL + "/" + window.GEVME.livepage.slug

{{livepage.title}}

The title of the livepage.

{{project.baseUrl}}

[Deprecated] Represents the URL to the folder of template being loaded

{{project.companyId}}

The ID of the company.

{{venue.id}}

The ID of the venue.

{{venue.name}}

The name of the venue.

{{project.partials}}

List of HTML codes for partials which are used for rendering preset components on the page, the keys are the name of the html files.

{{project.rootUrl}}

The root URL of a project. Eg. www.gevme.com/page or customdomain.com/page. Does not end with backslash.

{{setting.backgroundImage}}

The URL of background image.

{{setting.customDomain}}

URL of the custom domain.

{{setting.header}}

Contains attributes for header settings.

{{setting.livebar.closable}}

{{setting.livebar.positionLeft}}

{{setting.livebar.positionRight}}

{{setting.livebar}}

Contains attributes for livebar settings.

{{setting.loginOption.custom}}

{{setting.loginOption.google}}

{{setting.loginOption.microsoft}}

{{setting.loginOption.sharedPassword.enable}}

{{setting.loginOption.sharedPassword.value}}

{{setting.loginOption.sharedPassword}}

{{setting.loginOption.sms}}

{{setting.loginOption}}

Contains attributes for login options.

{{sponsor.logo}}

Logo of the company that sponsors.

{{setting.registrationUrl}}

{{setting.textColor}}

Hex code for the default text color.

{{speakers.0.bio}}

Biography of speaker, in HTML format. Eg: “<p>Biography</p>”.

{{user.company}}

Company of user.

{{user.firstname}}

First name of user.

{{user.jobTitle}}

Job title of user.

{{user.lastname}}

Last name of user.

{{speakers.0.profilePhoto}}

URL of the speaker’s profile picture uploaded.

{{sponsor.code}}

Unique ID when creating the sponsorship company.

{{sponsor.custom1}}

Custom fields that the company would want to add in the sponsorship.

{{sponsor.custom2}}

Custom fields that the company would want to add in the sponsorship.

{{sponsor.custom3}}

Custom fields that the company would want to add in the sponsorship.

{{sponsor.custom4}}

Custom fields that the company would want to add in the sponsorship.

{{sponsor.custom5}}

Custom fields that the company would want to add in the sponsorship.

{{venue.description}}

Description of the venue in use.

{{venue.id}}

The ID of the venue.

{{sponsor.isBookmarked}}

Checks if the sponsorship is bookmarked.

{{sponsor.logo}}

Logo of the company that sponsors.

{{venue.name}}

The name of the venue.

{{user.projectId}}

Project ID related to the event.

{{sponsor.socialMediaLinks.0.label}}

{{sponsor.socialMediaLinks.0.url}}

{{sponsor.socialMediaLinks}}

Any social media links such as Twitter, Instagram, Website, etc. Full for description, click here.

{{sponsor.sponsorPackageId}}

If sponsorship is linked to any package, sponsorPackageId will contain the id of the package.

{{sponsor.tagline}}

Optional tagline for the company.

{{template.baseURL}}

Base URL of folder to template

{{venue.name}}

The name of the venue.

{{user.company}}

Company of user.

{{user.firstname}}

First name of user.

{{venue.id}}

The ID of the venue.

{{user.jobTitle}}

Job title of user.

{{user.lastname}}

Last name of user.

{{user.projectId}}

Project ID related to the event.

{{venue.active}}

{{venue.description}}

Description of the venue in use.

{{venue.experience}}

Contains attributes for the experience being used.

{{widgets.0.features}}

Each type of widget has multiple features. For example, live-bar widget has 7 different features whereas a header widget has only 3 features.

{{venue.gallery}}

List of sample preview pictures of the venue.

{{venue.goodFor}}

Suggested usage of the venue.

{{venue.id}}

The ID of the venue.

{{venue.isEditable}}

{{venue.name}}

The name of the venue.

{{venue.sdkBaseUrl}}

The URL of sdk.

{{venue.source}}

Source of the venue. e.g.”github”.

{{venue.thumbnail}}

The URL of the thumbnail image file.

{{venue.version}}

The version number of the venue.

{{widgets.0.features}}

Each type of widget has multiple features. For example, live-bar widget has 7 different features whereas a header widget has only 3 features.

{{widgets.0.featuresOrdering}}

Indicates if the list of features are being ordered in the array.

{{widgets.0.inputs}}

{{widgets.0.options}}

{{widgets.0.position}}

Field is only available when widget is of type: “live-bar”. Position can be “right” or “left”, etc.

{{widgets.0.widget}}

There are 3 types of widgets: “live-bar”, “header”, and “menus”.