Custom Data (Field Merge)

Triblio allows you to show account-specific content to visitors in your campaigns. Custom Data refers to the account-specific content that Triblio maps to recognized visitors, with each Custom Data object composed of four fields, described in the table below.

Label CSV Column Name What it means   Example
ID id  Each piece of custom data gets a unique ID used for updates. If left blank, Triblio will automatically assign an ID for each row
Merge Key mergeKey Value that is replaced by custom data  accountName
Merge Value mergeValue The custom data that gets dynamically inserted in replace of the Merge Key  Triblio
Merge Value Type mergeValueType The type of text getting replaced (text or HTML)  text
Account Field domain The domain of the account that should see this piece of custom data  triblio.com

You will likely upload Custom Data in a CSV file rather than manually entering it through Triblio. To do this, use the "Upload Custom Data" button on the top right of the Custom Data home screen. 

Make sure each column in the CSV has the column name written in the top row exactly as shown above.  When saving the CSV, make sure it has the .csv extension or the upload will fail.
Here is a template file that you can use to upload into Triblio.

Once you upload a CSV successfully, a confirmation email will be sent to you and your Custom Data will be available for reference as Field Merges.

Custom Data/Field Merge in Messaging Element

Field Merges allow you to display account-specific information to each visitor. Before using Field Merges, you must upload the account data in your Custom Data section.

To add a Field Merge to a Messaging  Personalization :

  1. Open the on-page messaging editor
  2. Click on editable text where you want the field merge to appear and click "Edit Text"
  3. Beneath the text editor, choose "Insert Field Merge"
  4. Choose which Merge Key to use and add a default value to display in case there is no account match
  5. On the "Messaging Campaign Editor" page, in the "Advanced" section under the link to the personalized URL, make sure the "Has Field Merge" is toggled to "Yes"

Custom Data/Field Merge in Overlay CTA

Field Merges allow you to display account-specific information to each visitor. Before using Field Merges, you must upload the account data in your Custom Data section.

To add a Field Merge to an Overlay CTA:
  1. Open the overlay CTA editor or messaging editor
  2. Click on editable text where you want the field merge to appear
  3. At the bottom of the content editor, click "Insert" and choose "Field Merge"
  4. Choose which Merge Key to use and add a default value to display in case there is no account match

Advanced Use of Custom Data

Field merges can be used to insert company name, industry, tech stack, etc. very easily by replacing text fields. It can also be used for more advanced situations, such as swapping out an image based on the account coming.

Field Merge for Images

Setting up field merges for images is, luckily, still pretty simple. 

  1. Use the CSV template to insert data (or type in manually to 'New Custom Data' if you only have a few)
  2. In the CSV template, write in the Account, Merge Key, Merge Value (this will be the image URL), and Merge Value Type (this will be text)
  3. Once the custom data is loaded into Triblio, add your Messaging or Overlay CTA Element
  4. Select the image you want to customize and add in the field merge code.

Field Merge with Variable Text

Depending on the sentence surrounding your field merge, you may need different grammar for the Field Merge Text compared to the Default Value Text. 

By default, the field merge syntax appears:

{{=it['accountName'] || 'You're'}} on the path to success

This means, when an account visitor encounters the field merge, they will see their account name in the context of the sentence. If they are in the audience but do not match an account IP for the field merge, they will see You're on the path to success.

Matching IP: Triblio on the path to success

Non-Matching IP: You're on the path to success

Note: A visitor could become part of an audience and not qualify for the field merge if they were cookied into the audience at their office and returned to your site at their home IP or if their IP is associated with more than one account.

However, sometimes the grammar won't be an exact match. If we modify the example above, you'll see how the Account Name field now needs an apostrophe:

{{=it['accountName'] || 'Your'}} path to success

This would read "Triblio path to success" or "Your path to success". One solution would be to upload the custom data to match the grammar. However, that is not easily scalable and not simple to reuse in other situations. Instead, we can write a more advanced field merge:

{{? =it['accountName'] }}

{{=it['accountName'] }}'s 
{{??}}
Your 
{{?}} path to success
Ok, that looks a little intimidating. Let's break it down by line.
Line 1: Check to see if the visitor qualifies for the field merge
Line 2: If the visitor qualifies, add in the field merge and the logic statement will finish here
Line 3: If the visitor did not qualify in Line 1, the code looks for what do add in next
Line 4: Add in the default value
Line 5: End the logic statement and add in the rest of the text
Of course, you CSM is also able to help you write this logic.