The Folloze-Demandbase Custom Fields Connector enables you to pull more account data from Demandbase into Folloze.  
Integrating Demandbase custom fields into your Folloze instance allows you to use them in personalization rules and merge tags. These merge tags are particularly useful in text elements, enhancing the customization of your content.  

To set up the DB Account Connector, you will need to perform technical setup steps in both Demandbase and within the Folloze Company Admin settings. 

To learn more about the Folloze-Demandbase integration, read here.  

Demandbase Integration Setup  

Before you begin, you must first set up the Account Connector to enable sending Demandbase account data to Folloze. 

1. From the left menu bar, go to Settings > Demandbase-Wide Settings > Account Connector. 
2. Click Create New Integration. 
3. Select Folloze from the dropdown list of integrations. 
4. From the Search Field(s) drop-down list, select the fields with the account data to send to Folloze. Field types include: Firmographics, Scores: Qualification Scores, Pipeline Predict, Engagement Minutes, Source, etc. 

       

5. To create the connector that includes the API token and JSON file, click Create.
   Demandbase reviews the integration setup, which typically takes 24-48 hours for approval on their end. Once the status changes from Processing/Inactive to active, the custom fields become valid for use in Folloze.
6. Download the JSON file and copy the new API token. You will need the downloaded JSON file to upload in Folloze, and connect the new API token. .

Folloze Company Admin Setup 

After creating a Folloze account connector in Demandbase, you can now set up the integration in the Folloze Company Admin.  

1. Go to Company Admin > Integrations > Data Providers > Demandbase. 
2. To upload fields in bulk via JSON file, click Upload File. The custom fields will populate the Demandbase custom fields management table. 
3. To add individual Demandbase custom fields, click New Field.
4. Fill in the Create Custom Field form. 

• Display name: the field name displayed to the user. It will include `[DB]` at the end to indicate it is a Demandbase field. 
• Attribute name: the custom field’s unique identifier in Demandbase.
• Used for merge tags: Company admins can control which custom field can be used for merge tags (text replacement) in the personalization designer. This enables you to avoid displaying unnecessary custom field values in your live boards, while still allowing users to use these fields for personalization rules. 
• Values type: custom field values can be determined in 2 ways: 
  • User input: Users can manually add values for each field via the personalization rule builder. This option may be more prone to errors for logical comparisons but is suitable for general text replacements. 

• • Closed list: custom field values are predefined and managed by the Company Admin via the custom field table. When a user uses the custom field for creating personalization rules, they cannot add values. Values can be added and edited in 2 possible ways:
    • One by one - Click +Add Value to add a new input line for the new value. To change the order of values, drag and drop the input line. 
    • Edit as comma-separated values list - Turn on the Edit as CSV toggle to add a values list separated by commas for convenience. 
• # boards: this provides an indication of where each custom field is currently used for personalization rules. By clicking on the board’s name or the number of board indication, you can navigate to the exact boards where the custom field is being used. You cannot delete custom fields that are currently in use. You will be prompted to remove all related personalization rules before deleting a custom field.

Important to know

When uploading a JSON file to a populated table, any existing custom fields will be ignored, and only the new fields present in the JSON file will be added to the table.