Integration Values

PeerSpot Integration Values Table

List of additional values which are available for integrations

These values don’t appear as the standard available options in the peerspot.com integration forms. Copy and paste these values to the relevant field in the integration form.

Integration terms & uses:

"~" - enables you to enter a dynamic object property (e.g.,first_name from user or industry from company) in a static text field. This is useful when you
a. Don't have a dropdown to select the property (e.g., Marketo)
b. The property is not in the dropdown
c. You need to apply a translation function

"%" - inserts dynamic text into an existing sentence. The reference used to identify the source of the dynamic text (e.g., cats, prods, etc.) follows the % wrapped inside curly braces { }.

For example:
“This lead is from PeerSpot and should be followed up with ASAP. This lead is from a Company recently researching %{cats} solutions.”

"~" Is only used as the first part of a field value. Anything that needs to be added within or after that value will start with %.

Field Name: Enter the field name that you received from the customer.
Dropdown Field Values: You may select a predefined user, lead, or field from the dropdown list. The value of the field depends on the campaign actively being posted to.
Static Text Field: You can enter a static value that will be passed through as-is for every lead.
~(object).field_name: Where object can be user, company or lead and field_name is any legal field name or method belonging to the object.

There are 3 types of objects:
1. User- The user object contains all values relevant to information found on a user page (email, first_name, etc.)
2. Lead- Custom questions+responses or the timestamp of when the lead became a lead on the site
3. Company- Any info stored in the user's company (company size, industry).

Keywords:
cats - Category name(s)
ltype - lead type
prods - lead product interests

For interpolations:
Option 1: %{name.subname}. All objects besides keywords are added like this. E.g. %{user.first_name}
Option 2: %{keyword}. E.g. %{prods}

Custom Question Responses have a magic method: ~lead.cqr_field_symbol where field_symbol is the field_symbol of a Custom Question. Example: ~lead.cqr_valuable_aspects.
Date Fields: If the field you selected is a date, you may format the string using square bracket notation. The default format is [%Y-%m-%d], e.g. 2023-02-27.
In addition, you can add a VendorIntegration function after the field name, e.g. ~user.phone ITCS_to_QS_phone. These functions need to be created by the dev team.
For Retargeting Leads vendor asset and vendor landing page url we have magic methods: ~lead.edj_vendor_asset and ~lead.edj_vendor_lp

Values & their codes:

Value Name

Value Code

Description

Company Size - letter

~company.company_size

Company Size - written range (default)

~company.company_size_display

Company Size - highest number in the range

~company.company_size Company_size_ITCS_to_upper_bound

Number/integer

Company Size - lower number in the range

~company.company_size Company_size_ITCS_to_lower_bound

Number/integer

Company Size - middle number in the range (for specific numbers see metallics sizes below)

~company.company_size Metallic_company_size

Number/integer

Company Size - without the word 'employees'

~company.company_size Company_size_ITCS_to_range_only

Company Size - without the word 'employees' and without the comma in the numbers

~company.company_size Signavio_company_size

PeerSpot company size values

A Self Employed

B 1-10 Employees

C 11-50 Employees

D 51-200 Employees

E 201-500 Employees

F 501-1,000 Employees

G 1,001-5,000 Employees

H 5,001-10,000 Employees

I 10,001+ Employees

Country code values:

Value Name

Value Code

Country Code, e.g. US, CA, etc

~user.country

Country Full Name with US as United States

~user.country_name us_as_united_states

Country Name e.g. USA, Canada, etc

~user.country_name

Country Name with US as United States of America

~user.country_name us_as_united_states_of_america

Country Name with US as United States all upercase letters (UNITED STATES/AUSTRALIA)

~user.country_name us_as_united_states_upcase

State code Values:

Value Name

Value Code

State - generally 2 digit, e.g. NY, but not always. If there is a state that has more than 2 digits, that's what will show up.

~user.state

State - full name, e.g. New York

~user.state_name

State - US/CA only 2 digit

~user.state us_canada_states_only

State - US/CA only full name (Include states only for US/CA.Full name)

~user.state_name us_canada_states_only

State - US only full name

~user.state us_states_fullname

State -2 letter code for US/CA/Australia

~user.state us_ca_au_state_codes_only

State -Full name for US/CA/Australia

~user.state us_ca_au_state_names_only

State - US only 2 digit

~user.state us_states_only

State - Canada States 2 digit

~user.state ca_states_only

Phone number values:

Value Name

Value Code

Main Phone

~user.primary_phone

Phone 2

~user.phone2

Phone number with no spaces

~user.primary_phone strip_whitespace

Phone2 with no spaces

~user.phone2 strip_whitespace

Phone with US validation only- format of (888) 888-8888

~user.primary_phone phone_to_us_ca_format

Phone 2 with US validation only- format of (888) 888-8888

~user.phone2 phone_to_us_ca_format

Phone 2 added within text (e.g. to the notes: "This lead has researched %{cats} solutions and specific products %{prods} on PeerSpot. %{secondary_phone}"

%{secondary_phone}

Date values:

Value Name

Value Code

Date - needs to be long (Converts a date/datetime to the Unix Timestamp (in ms) of midnight of that date (for UTC timezone))

~lead.created_at date_to_JS_time_at_midnight

Date regular

~lead.created_at[%Y-%m-%d]

Date: when it needs to be: yyyy-MM-dd HH:mm:ss

~lead.created_at[%F %T]

Date: when it needs to be: MM/dd/yyyy

~lead.created_at[%m/%d/%Y]

When needing date inserted into a static field

%{lead_formatted_created_at}

When a customer requests a specific date format

In order to apply date formatting you have 2 options:

1. Set the default date format on the integration access edit page to %m/%d/%Y. Add %{lead_formatted_created_at} as static text where all the fields are.

2. Add a formatting modifier to lead created_at field. You would enter that in the static text field as: ~lead.created_at[%m/%d/%Y]

Smarter question/answer values:

Value Name

Value Code

Smarter Leads - vendors specific questions & answers only

%{campaign_custom_question_responses_text}

Smarter Leads with other text - all the questions & answers in the category

%{custom_question_responses_text}

Smarter Leads by itself - vendors specific questions & answers in the category

~lead.campaign_custom_question_responses_text - this isn't created

Smarter Leads by itself - all questions & answers in the category

~lead.custom_question_responses_text

Smarter Leads separated out - just answers are sent, in separate fields

~lead.cqr_fieldsymbol

Smarter Leads with other text - just answers

%{campaign_custom_question_responses_only_text}

Notes values:

Value Name

Value Code

Standard Notes

This lead has researched %{cats} solutions and specific products %{prods} on PeerSpot.

Intent Lead Notes

This lead is from PeerSpot and comes from a company that has been researching %{cats} solutions.

Smarter Leads Notes

This lead researched %{cats} solutions and specific products %{prods} on PeerSpot and answered the following questions: %{campaign_custom_question_responses_text}.

Smarter Intent Lead Notes

This lead is from a company that has recently been researching %{cats} solutions on PeerSpot and has answered the following questions: %{campaign_custom_question_responses_text}.

TA Intent Lead Notes (Signal)

This lead is from a company that has recently been researching %{cats} solutions on PeerSpot.

Aged Leads

This lead is from a company that has recently been researching %{cats} solutions on PeerSpot.

Others:

Value Name

Value Code

Job Level

~user.job_level_display

Job Level within text

%{user_job_level_display}

Job Level when creating a translation function

~user.job_level

Department

~user.department

LinkedIn Info

~user.linkedin_url (when used with another code- %{user.linkedin_url})

City

~user.city

Region (NA, EMEA, APJ, LATAM)

~user.country country_to_region

Lead Code

~lead.lead_code

Lead Code - to add it into a field with other text

%{lead.lead_code}

Industry

~company.company_industry_display

Industry with translation function

~company.industry (company name)_industries

Industry within text

%{user_company_industry_display}

Category - only 1 category out of all potential options, it will be a category being targeted in the campaign

~composite.campaign_lead_intersecting_category_name