V2 Merge Data Field Reference

This reference documents every field available in V2 merge data for tag templates. It is organized by top-level namespace. Use the field paths here directly in template tags.

For tag syntax (loops, conditionals, rich text), see How Tag Templates Work and the Template Expression Reference.

Top-Level Structure

V2 merge data is organized into four namespaces plus several top-level collections.

Important: project_pricing and project_payments are top-level namespaces. They are not children of project. Using {project.project_pricing} will not work.

project fields

Core metadata

Date fields like created_on and printed_on support the .to_short_date filter when Include Formatting is enabled:

{project.printed_on.to_short_date}

Current version object

The current_version object exposes details about the most recently created named version.

Narrative fields

Narrative fields are arrays of strings (one entry per paragraph). Loop over them to render each paragraph, or use the formatted_ version for a single rich text block.

Use the array approach when you need to apply per-paragraph styling or numbering. Use formatted_ when you want a single formatted block without per-item control.

Contacts

All contact objects expose name, email, title, and phone.

Primary contact

The project’s primary customer contact. Wrap in a conditional block in case none is set.

{#project.primary_contact}
{name}
{title}
{email}
{phone}
{/project.primary_contact}

Primary contacts also include user_defined_fields if your account has custom contact variables defined.

Presales engineer and sales executive

{#project.presales_engineer}
{name} — {email}
{/project.presales_engineer}

{#project.sales_executive}
{name} — {email}
{/project.sales_executive}

All contacts (loop)

project.contacts is an array of all active contacts on the project. Each contact includes name, email, title, phone, and contact_type (a slug such as primary_customer_contact).

{#project.contacts}
{name} ({contact_type})
{/project.contacts}

Teammates

Project collaborators (internal team members). Each teammate exposes the same name, email, title, phone fields.

{#project.teammates}
{name} — {email}
{/project.teammates}

Client object

project.client is an object with all non-sensitive client attributes. Commonly used fields:

Business unit

project.business_unit is an object with the project’s business unit, if assigned.

Rate table

Tags

project.tags is an array of tag strings applied to the project.

{#project.tags}{.}{/project.tags}

Terms and conditions

An array of active terms and conditions attached to the project. Each item has name, slug, content (plain text), and formatted_content (HTML).

{#project.terms_and_conditions.length>0}
  {#project.terms_and_conditions}
    {~~formatted_content}
  {/project.terms_and_conditions}
{/project.terms_and_conditions.length>0}

Note: terms and conditions must be accessed with the project. prefix. {#terms_and_conditions} without a prefix will not render.

Text blocks

Text blocks are pre-written content configured in ScopeStack settings. Access them under project.text_blocks using the block’s slug. Always use {~~} rich text syntax.

{~~project.text_blocks.signatures}
{~~project.text_blocks.project_acceptance}
{~~project.text_blocks.change_management}

User-defined fields (custom project variables)

Custom variables defined in your account settings are available under project.user_defined_fields. Each field is accessed by its variable name and exposes a value property.

{project.user_defined_fields.project_number.value}
{project.user_defined_fields.duration_weeks.value}
{project.user_defined_fields.sow_id.value}

Use conditionals to show content based on a custom variable’s value:

{#project.user_defined_fields.msa_on_file.value=="yes"}
MSA is on file.
{/project.user_defined_fields.msa_on_file.value=="yes"}

Attachments and logos

project.attachments is an array. Each attachment has a slug (derived from its type name) and a url.

{#project.attachments}
{url}
{/project.attachments}

project_pricing fields

Top-level totals

These are the rollup financial figures for the entire project.

Currency fields require .to_currency when Include Formatting is enabled.

professional_services

The professional_services object contains phases, locations, and lines of business for PS work, plus summary figures.

Phases

project_pricing.professional_services.phases is an array. Each phase contains a list of services and rollup financials.

{#project_pricing.professional_services.phases}
  {^slug=="no_phase"}Phase: {name}{/slug=="no_phase"}
  {#services}
    {name}
    {~~formatted_service_description}
  {/services}
{/project_pricing.professional_services.phases}

Common phase slugs: no_phase, inhouse_prep_language, onsite_implement_language, remote_implement_language, post_support_langauge (note: the last slug has a typo in the platform — “langauge” — and must be used exactly as written).

Lines of business

project_pricing.professional_services.lines_of_business is an array of LOB objects. Each LOB has name, code, slug, services (array), and service_categories (array of service category objects).

Each service category under a LOB also has name, code, slug, and services.

Locations (within professional_services)

project_pricing.professional_services.locations is an array of location objects. Each location has name, address, services, and rollup financial fields (total_revenue, service_revenue, etc.).

managed_services

resources

project_pricing.resources is an array of resource summary rows. One row per resource, plus a TOTAL row at the end.

To loop over resources and exclude the total row:

{#project_pricing.resources}
  {^resource_slug=="project_total"}
    {resource_name} | {quantity} hrs | {hourly_rate.to_currency}/hr | {total.to_currency}
  {/resource_slug=="project_total"}
{/project_pricing.resources}

To show only the total row:

{#project_pricing.resources}
  {#resource_slug=="project_total"}
    Total: {total.to_currency}
  {/resource_slug=="project_total"}
{/project_pricing.resources}

product

The project_pricing.product object contains hardware and product line items.

Each item in project_pricing.product.items:

project_governance

project_pricing.project_governance contains governance items (project management, overhead, etc.).

Each item in project_pricing.project_governance.items:

travel_and_expense

project_pricing.travel_and_expense contains expense line items.

Each item in project_pricing.travel_and_expense.items:

payment_credits

project_pricing.payment_credits contains applied payment credits.

Each item:

third_party_services

project_pricing.third_party_services contains subcontractor quotes.

Each item in items:

Service fields

Service objects appear inside phase loops ({#services}), location phase loops, LOB loops, and managed services. A service can be either a professional service or a managed service.

The following fields are available on every service object.

Identification

Hours and quantity

Pricing

Resource

Description

Uniqueness and deduplication

Use unique to de-duplicate services when you want to show each service name only once:

{#services}
  {#unique}
    {name} (appears {unique_count} times)
  {/unique}
{/services}

Language fields on a service

Each service has a language_fields object keyed by language field slug. Access per-service language content directly without an outer loop:

{#services}
  {name}

  {#language_fields.deliverable.sentences}
    {.}
  {/language_fields.deliverable.sentences}

  {#language_fields.customer.sentences}
    {.}
  {/language_fields.customer.sentences}
{/services}

User-defined fields on a service

If your account has custom service variables defined, they appear under user_defined_fields on each service object, using the same structure as project-level variables.

Subservices

Each service has a subservices array. Subservices share most fields with services but have a reduced set.

{#services}
  {name}
  {#service_description}{.}{/service_description}

  {#subservices}
    ({quantity}) {name}
    {#service_description}{.}{/service_description}
  {/subservices}
{/services}

locations fields

locations is a top-level array of service location objects. Use this for location-first document layouts. Each location includes all its phases and services pre-organized.

Location object fields

Phases within a location

Each phase object inside locations[].phases has:

Location-first template pattern

{#locations}
  {name}
  {address}

  {#phases}
    {^slug=="no_phase"}
      Phase: {name}
    {/slug=="no_phase"}

    {#services}
      {name}
      {~~formatted_service_description}

      {#subservices}
        ({quantity}) {name}
        {#service_description}{.}{/service_description}
      {/subservices}
    {/services}
  {/phases}
{/locations}

language_fields

Language fields aggregate supplementary content (deliverables, assumptions, customer responsibilities, out-of-scope items) across all services. They exist at three scopes: top-level (entire project), per-phase, and per-service.

Top-level language_fields

language_fields is a top-level array. Each entry represents one language field type.

Standard language field slugs

Note: the slugs are abbreviated. Use "out", not "out_of_scope". Use "customer", not "customer_responsibilities".

Top-level language field loop

{#language_fields}
  {#slug=="deliverable"}
    Deliverables
    {~~formatted_introduction}
    {#phases}
      {#sentences}{.}{/sentences}
    {/phases}
    {~~formatted_conclusion}
  {/slug=="deliverable"}

  {#slug=="customer"}
    Customer Responsibilities
    {~~formatted_introduction}
    {#sentences}{.}{/sentences}
  {/slug=="customer"}
{/language_fields}

Phase-scoped language content

To show language content grouped by phase, use the phases array within each language field:

{#language_fields}
  {#slug=="deliverable"}
    {#phases}
      {name}
      {#sentences}{.}{/sentences}
    {/phases}
  {/slug=="deliverable"}
{/language_fields}

project_payments fields

Payment terms and schedule data live under project_payments.

Pricing model and payment terms

Currency objects

Payment schedule

project_payments.schedule is an array of payment schedule items.

{#project_payments.schedule.length>0}
  Payment Schedule:
  {#project_payments.schedule}
    {description}: {amount_due.to_currency}
    {#payment_date}{payment_date.to_short_date}{/payment_date}
  {/project_payments.schedule}
{/project_payments.schedule.length>0}

project_payments.arr_schedule follows the same structure but groups payments annually.

Conditional blocks by pricing model

{#project_payments.pricing_model=="fixed_fee"}
  This is a fixed fee engagement.
{/project_payments.pricing_model=="fixed_fee"}

{#project_payments.pricing_model=="time_and_materials"}
  This engagement is billed on a time and materials basis.
{/project_payments.pricing_model=="time_and_materials"}

{^project_payments.payment_terms.include_expenses}
  Expenses are billed separately and are not included in this estimate.
{/project_payments.payment_terms.include_expenses}

currency fields

currency is a top-level object with the project’s currency settings.

survey_responses

survey_responses is a flat object keyed by response slug. Each value is the response text or a selected option value. Date-type responses are formatted according to account settings.

{survey_responses.implementation_scope}
{survey_responses.customer_size}

Formatted fields summary

Every field that has a formatted_ counterpart is listed below. These fields contain HTML and must be rendered with {~~}.

User-defined fields summary

Custom variables can be defined at multiple levels in ScopeStack. Each level’s variables appear under a user_defined_fields object on the corresponding item.

The variable name in the path is the internal variable name set in your account’s project variables configuration, not the display label.