Refers to the current portal request page. This object combines the attributes of the current site map node and the current request entity (usually a Web Page).

The page object provides access to things like the breadcrumbs for the current page, the title or URL of the current page, and any other attributes or related entities of the underlying CRM record.

<ul class="breadcrumb">
{% for crumb in page.breadcrumbs %}
<li><a href="{{ crumb.url | escape }}">{{ crumb.title | escape }}</a></li>
{% endfor %}
<li class="active">{{ page.title | escape }}</li>

<div class="page-header">
<h1>{{ page.title | escape }}</h1>

<div class="page-copy">
{{ page.adx_copy }}

<div class="list-group">
{% for child in page.children %}
<a class="list-group-item" href="{{ child.url | escape }}">
{{ child.title | escape }}
{% endfor %}

<!-- Page {{ }} was last modified on {{ page.modifiedon }}. -->

Page Attributes


Returns the breadcrumb site map node objects for the page, starting from the site map root node and ending at parent.


Returns the child site map node objects of the page.


Returns the parent site map node of the page.

If the page is the Home page, parent will be null.


The title of the page.


The URL of the page.

[attribute or relationship name]

You can access any attribute of the page's underlying CRM record by logical name.

{{ page.createdon }}

{% assign attribute_name = 'name' %}
{{ page[attribute_name] }}

The values of most entity attributes map directly to Liquid types: Two Option fields map to booleans, text fields to strings, numeric/currency fields to numbers, date/time fields to date objects. But, some attribute types are returned as objects:

You can also load any related entities by relationship schema name.

{{ page.adx_webpage_entitylist.adx_name }}

In the case that a relationship is reflexive (i.e. self-referential), a reflexive relationship object will be returned. (Otherwise, the desired result would be ambiguous.)

{{ page.adx_webpage_webpage.referencing.adx_name }}

  Loading large numbers of related entities, or accessing large numbers of relationships in a single template, can have a negative impact on template rendering performance. Avoid loading related entities for each item in an array, within a loop.

Where possible, prefer use of the entitylist and entityview tags to load collections of entities.