Skip to main content
Conga Support

Hiding or showing content in Sections and Pages: Logic Builder


Conga Collaborate administrators can create pages and sections in templates that show or hide based on specific criteria. Conga Collaborate calls these conditional sections and pages.

If you are using the newest version of Logic Builder, see Logic Builder Basics


Conditional sections and pages provide Conga Collaborate admins with a way to ensure that content is present in a document only if it is needed, thus eliminating user error and speeding up document creation time. Our conditional logic builder provides a simple point-and-click interface that enables you to build your logic statements without code. Conditional sections or pages can leverage document variables, CRM variables, or survey form variables in their logic statements.

For example, many Conga Collaborate administrators want pages in a template that will show only if a prospect is purchasing a specific product or if a proposal is for a specific situation, like a renewal. In that case, they may create a page that uses show/hide logic based on Opportunity Line Item data or an Opportunity variable coming in from a Salesforce Opportunity record.


To create conditional sections or pages in a document or template:

  1. Hover over the section or page in the Table of Contents.

  2. A gear icon will appear. Click the gear icon and select Edit Properties.

  3. Click the Include Logic tab on the Section or Page properties.  The fields on the logic tab will guide you through writing the logic statement.

  4. Use the first drop-down to select a variable that will be evaluated.

  5. Use the second drop-down to select an operator.  A large number of operators are supported, and they vary based on your variable’s data type.

  6. Use the third drop-down to define a value to act as the operand.

  7. You will now see the full expression. Click Save.

Here are a few examples:




(Document Variable)



(Salesforce Variable)


New Customer

(Salesforce Variable)

not equal



When building show/hide logic statements using CRM variables, you must use variables that are related to your launching object.  For example, when launching from an Opportunity but using the Industry field on the Account object, you need to use the variable that gets mapped from the Opportunity up to the Account, Opportunity_Account_Industry.

Notes on logic based on child object data:

Some Conga Collaborate administrators may want to write logic statements that are not based on fields on the launching object, but instead use fields from a child object of the launching object, such as Opportunity Line Items present on an Opportunity in their CRM.  In this case, the fields are treated as a data array filled with key value pairs. If a child object is selected in the variable drop-down, additional logic builder fields become present.

Here’s an example of writing such a logic statement:



A Record Where







In this example, this page or section would show if any of the products in my Opportunity Line Items on the Salesforce Opportunity record that I have launched from have a product family equal to “Services.”

Going Further with Conditional Page and Section Logic

Admins can use the  “Show Advanced” option in the logic builder to write more advanced logic statements with other operators or AND/OR statements.  Statements written in the advanced builder must be all lowercase, with the exception of variable values, which are case sensitive.


opportunity_region__c == ‘Northeast’ or opportunity_region__c  == ‘Midwest’

proposal_name.include?(“Octiv Document”) or proposal_client.include?(“Octiv Client”)

opportunity_amount >= 1000 and opportunity_type == ‘New Customer’ or opportunity_type == ‘Renewal’

If you established logic to hide a page or section in an active document (not a template), refresh your browser or go to the Variables panel and click Refresh Variables and CRM pages to see your changes in draft mode. Otherwise, your new logic statement doesn’t take effect until you publish your document.

  • Was this article helpful?