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	1
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

Note: 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 :

Open the on-page messaging editor
Click on editable text where you want the field merge to appear and click "Edit Text"
Beneath the text editor, choose "Insert Field Merge"
Choose which Merge Key to use and add a default value to display in case there is no account match
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

Note: 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:

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

Custom Data/Field Merge on Smart Pages

Note: 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 Smart Page:

Open the template editor on the Smart Page Group
Click into a section of the Smart Page that has the content you want to field merge in
On the Quick Edit panel on the left hand side of the page, select the drop down arrow on the content you want to place the field merge and select Insert Field Merge:
A modal will appear that gives you some field merge options:
1. Custom Data: This is the most widely used form of dynamic content, as it gives you the most control over the exact content that you want to map to a given account. Simple select the custom mapping value that you have already uploaded to this section, such as accountNameClean in the image below:
2. Account Firm: This gives you access to Triblio's account database, most commonly to field merge in an Account Name. Simple select the value you want to merge in from the available options:
3. SFDC Data: If you use Salesforce, then you have the ability to dynamically pull in either Account Object Fields or Account Owner/User fields directly from Salesforce on to the Smart Page
  
  For example, the Account Owner entity could be used to pull in an About Me paragraph on to the page based on whose account the page is:The Account entity could be used to grab Salesforces Account name and add it to the page:
Finally, plug in a default value at the bottom of the modal, where it says Field Merge Default. This will guarantee that there will always be content on the page for this value.

Note: You can field merge in more complex things on the page such as images, forms, embedded videos, or entire HTML blocks. You can do this by dropping the Field Merge Tag into any section of your template. An example of this might be utilizing a unique rep image by updating the image tag's source with a field merge value:

<img src="{{= it['repImage'] || 'https://www.Your_Default_Rep_Image_Here.com'}}">

If you have questions about how to best think through and implement more robust Custom Data deployments for your Smart Pages, reach out to your CSM.

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.

Use the CSV template to insert data (or type in manually to 'New Custom Data' if you only have a few)
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)
Once the custom data is loaded into Triblio, add your Messaging or Overlay CTA Element
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'] }}'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

Want to use multiple field merge values in a singular field? You can compound the or logic of the field merges this way:

{{= it['Link1'] || it['Link2'] || it[Link3] || it['Link4'] || 'Fallback link' }}

The logic here will check if each link exists for an account, and proceed from link 1 -> link 4 until it finds one that exists. If none of them exist for a given account, they will receive the fallback link instead.

Of course, you CSM is also able to help you write this logic.