A Guide to PJA Merge Tags (& Glossary)

Purpose

In this article, Allbound System Admins will learn about Partner Journey Automation (PJA) merge tags and how to use this article as a glossary reference.

Introduction

PJA merge tags are used to personalize action emails. When composing an email, you can add a merge tag as a placeholder that will be populated with the appropriate value when the email is sent. Customizing emails with personalized merge tags can lead to higher open and engagement rates, as well as help to establish a stronger connection with your partners. It is a best practice that can benefit both the sender and the receiver.

PJA Email Merge Tags

When a PJA workflow action is set to "Send email", Merge Tags are available for use in both the email Subject and Message. The Merge Tags dropdown menu is dynamic and displays values that are relevant to the selected PJA Trigger. This means that if you change the PJA trigger then the Merge Tags dropdown list is also updated.

The Merge Tags dropdown correlates directly to the object that the trigger is related to. View the triggers below to understand which Merge Tags will be available. 

User & Company Related Triggers

Trigger		Merge Tag Objects
User has	Registered	User, Company
User has	Updated profile	User, Company
User has	Logged in	User, Company
User has	Registered a company	Company
User has	Updated a company	Company
User has not	Logged in	User, Company

Triggers related to the User object always include merge tags for both the user and the user's primary company. Whereas, triggers related to the Company object (without user object), only have merge tags for the company.

For all other triggers, the User and Company related merge tags display a contextual label in front of the User and Company merge tags.

Form Related Triggers

Trigger		Merge Tag Objects
User has	Submitted a form	Form, User, Company
User has	Passed a quiz	Form, User, Company
User has not	Submitted a form	User, Company

Form related triggers display contextual merge tags for the User and Company objects as follows:

Content Related Triggers 

Trigger		Merge Tag Objects
User has	Completed a learning track	Content, User, Company
User has	Created a prospect page	Content, User, Company
User has	Co-branded content	Content, User, Company
User has	Viewed content	Content, User, Company
User has not	Completed a learning track	Content, User, Company
User has not	Created a prospect page	User, Company
User has not	Co-branded content	User, Company
User has not	Viewed content	User, Company

Content related triggers display contextual merge tags for the User and Company objects as follows:

Deal Related Triggers

Trigger		Merge Tag Objects
User has	Registered a deal	Deal, User, Company
User has	Updated a deal	Deal, User, Company
User has not	Registered a deal	User, Company
User has not	Updated a deal	Deal, User, Company

Deal related triggers display contextual merge tags for the User and Company objects as follows:

MDF Request Related Triggers

Trigger		Merge Tag Objects
User has	Created MDF Request	MDF Request, User, Company
User has	Updated MDF Request	MDF Request, User, Company
User has not	Updated MDF Request	MDF Request, User, Company

MDF Request related triggers display contextual merge tags for the User and Company objects as follows:

Lead Related Triggers

Trigger		Merge Tag Objects
User has	Registered a lead	Lead, User, Company
User has	Updated a lead	Lead, User, Company
User has not	Updated a lead	Lead, User, Company

Lead related triggers display contextual merge tags for the User and Company objects as follows:

Object Merge Tag Glossary

All merge tags correspond to tags related to the seven main objects:

1. User
2. Company
3. Form
4. Content
5. Deal
6. MDF Request
7. Lead

By understanding these basic rules about the User and Company objects, it's easier to understand that while the object label changes within the merge tag dropdown, the fields that are available are the same.

• All variations of the contextual User merge tags have the same User object merge tags
• All variations of the contextual Company merge tags have the same Company object merge tags

 

User Related Merge Tags

The following merge tags are available for all triggers that include the User (or any variation of User) object as a merge tag. The only differences may be the contextual prefix added to the merge tag option. 

Merge Tag	Definition	Example
User ID	Unique ID of the user record in Allbound	36
User Registration Date	Date the user registered in Allbound	2021-08-02 17:40:58
User Updated	Date the user record was last updated	2023-05-01 13:50:32
User Status	User record status	active
User Can Request MDF	Indicates if the user can request MDF	1 indicates Yes, 0 indicates No
User Email	User's email	[e-mail]
User First Name	User's first name	Peggy
User Last Name	User's Last Name	Smith
User Twitter URL	User's Twitter URL	https://twitter.com/username
User LinkedIn URL	User's LinkedIn URL	https://www.linkedin.com/in/username/
User Facebook URL	User's Facebook URL	https://facebook.com/username
User Google Plus URL	User's Google Plus URL
User Office Phone	User's office phone number	555-123-6543
User Mobile Phone	User's mobile phone number	555-123-7878
User Job Title	User's job title	Marketing Manager
User Profile Photo	File path to user's profile photo	/documents/vendorname/uploads/ profilephotos/mypic-square.jpg
User CRM ID	Unique ID of the user's record in CRM	0035e00000IPR31AAH
User Company Info	Company info, as entered by the User	My company info goes here.
User Appointment Scheduling URL	User's Appointment Scheduling URL (such as Calendly)	https://calendly.com/username/30min
User Custom User Field (Textbox)*	Custom Textbox field label	<text value>
User Custom User Field (Paragraph)*	Custom Paragraph field label	<text value>
User Custom User Field (Rich Text Bio)*	Custom Rich Text Bio field label	<text value displayed as rich text>
User Custom User Field (Dropdown)*	Custom Dropdown field label	<selected text value>
User Custom User Field (radio)*	Custom Radio field label	<selected text value>
User Custom User Field (Checkbox)*	Custom Checkbox field label	<comma separated list of selected values>
User Custom User Field (Multi-select)*	Custom Multi-Select field label	<comma separated list of selected values>
User Custom User Field (Date)*	Custom Date field label	06-23-2022
User Custom User Field (Phone Number)*	Custom Phone Number field label	5556549878
User Custom User Field (Number)*	Custom Number field label	80
User Custom User Field (URL)*	Custom URL field label	https://www.example.com/us/en/catalog
User Custom User Field (Country)*	Custom Country field label	<country code of selected Country>

*Note: Since the User form is customizable per portal, your actual Merge Tags may vary. These examples are intended to outline custom User fields of specific field types.

Company Related Merge Tags

The following merge tags are available for all triggers that include the Company (or any variation of Company) object as a merge tag. The only differences may be the contextual prefix added to the merge tag option. 

Merge Tag	Definition	Example
All Visible Fields	Bulleted list of all non-hidden fields, displayed in the format <Field Label>: <Field Value>	<Field Label1>: <Field Value> <Field Label2>: <Field Value>
All Fields	Bulleted list of all fields on the form, displayed in the format <Field Label>: <Field Value>	<Field Label1>: <Field Value> <Field Label2>: <Field Value>
Company Created	Date the company was created	2022-08-29 18:21:29
Company Updated	Date the company record was last updated	2023-01-13 12:20:40
Company Status	Status of the company	active
Company CRM	Unique ID of the company in the CRM	3214854214
Company Channel Account Manager	Email of the Channel Account Manager assigned to the company; usually synced from CRM	[e-mail]
Company Company Name	Name of the company	My Partner Company
Company Website	Company website	mypartnercompany.com
Company Type	Type of the company, as selected on the company form	VAR (value-added reseller)
Company Street Address	Company street address line 1	434 Main St.
Company Address Line 2	Company street address line 2	Suite 30
Company City	Company city	Los Angeles
Company State/Province	Company state/province	CA
Company Zip/Postal	Company zip/postal code	90210
Company Country	Company's Country	United States
Company Description	Description of the company	My company description goes here. Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Company Include Partner Locator Display	Indicates if the the company is included in the Partner Locator Display	No
Company Company Logo	URL of the company's logo	https://portal.allbound.com/wp-content/documents/portal/ uploads/forms/companyLogo1.jpg
Company Account Type	Indicates the Allbound account type (Vendor, Partner)	Partner
Custom Company Field (URL)*	Custom URL field label	https://example.com
Custom Company Field (Text)*	Custom Text field label	Lorem ipsum dolor sit amet, consectetur adipiscing elit. Viverra accumsan in nisl nisi scelerisque eu. Enim nec dui nunc mattis.
Custom Company Field (Paragraph)*	Custom Paragraph field label	Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Purus gravida quis blandit turpis. Viverra accumsan in nisl nisi scelerisque eu. Enim nec dui nunc mattis.
Custom Company Field (Multi Select)*	Custom Multi-select field label	["B","C"]
Custom Company Field (Dropdown)*	Custom Dropdown field label	option 2
Custom Company Field (Phone)*	Custom Phone field label	[phone]
Custom Company Field (Number)*	Custom Number field label	12345678
Custom Company Field (Email)*	Custom Email field label	[e-mail]
Custom Company Field (Date)*	Custom Date field label	2023-06-01
Custom Company Field (Currency)*	Custom Currency field label	15750.00

*Note: Since the Company form is customizable per portal, your actual Merge Tags may vary. These examples are intended to outline custom Company fields of specific field types.

Form Related Merge Tags

The following merge tags are available for all triggers that include the Form object as a merge tag.

Merge Tag	Definition	Example
<All form fields that have an API Database Key are displayed as a merge tag>*	<as defined by the form field label>	<field value>

*Note: Since all forms are customizable per portal, your actual Merge Tags may vary.

Content Related Merge Tags

The following merge tags are available for all triggers that include the Content object as a merge tag.

Merge Tag	Definition	Example
Content Title	The title of the Content	Partner Newsletter - March 2023
Content Link	Link to the Content	https://portal.allbound.com/engage/partner-newsletter-march-2023/

Deal Related Merge Tags

The following merge tags are available for all triggers that include the Deal object as a merge tag.

Merge Tag	Definition	Example
All Changed Fields	Bulleted list of all updated fields, displayed in the format <Field Label>: <Field Value>	<Field Label1>: <Field Value> <Field Label2>: <Field Value>
All Visible Fields	Bulleted list of all non-hidden fields, displayed in the format <Field Label>: <Field Value>	<Field Label1>: <Field Value> <Field Label2>: <Field Value>
All Fields	Bulleted list of all fields on the Deal Registration form, displayed in the format <Field Label>: <Field Value>	<Field Label1>: <Field Value> <Field Label2>: <Field Value>
Deal Link	Link to the Deal Registration form	https://portal.allbound.com/deal/yvviabcmnx/
Deal Created	Date the deal was registered	2023-04-27 21:14:47
Deal Updated	Date the deal was last updated	2023-05-12 13:45:10
Deal Rep Registering Deal	The unique Allbound ID of the user that registered the deal; also known as the Deal Owner	88
Deal Status	Current deal stage	New
Deal Deal Name	The name of the Deal; usually populated once the Deal is converted to an opportunity (if applicable)
Deal Company Name	The name of the prospect company	Acme Consulting
Deal Website	The prospect company's website	acmeconsulting.com
Deal First Name	The first name of the prospect contact	Max
Deal Last Name	The last name of the prospect contact	Cooper
Deal Customer Title	The title of the prospect contact	Director of IT
Deal Phone Number	The phone number of the prospect contact	[phone]
Deal Email	The email of the prospect contact	[e-mail]
Deal Street Address	The street address of the prospect company	121 Avery St.
Deal Address Line 2	The street address line 2 of the prospect company	#302
Deal City	The city of the prospect company	Boston
Deal State/Province	The state/province of the prospect company	MA
Deal ZIP/Postal Code	The ZIP/postal code of the prospect company	02111
Deal Country	The country of the prospect company	United States
Deal Amount	The amount of the deal	448540.00
Deal Estimated Close Date	The estimated close date of the deal	2023-06-03
Custom Deal Field*	Custom Deal field label	<field value>

*Note: Since the Deal Registration form is customizable per portal, your actual Merge Tags may vary.

MDF Request Related Merge Tags

The following merge tags are available for all triggers that include the MDF Request object as a merge tag.

Merge Tag	Definition	Example
MDF Link	Link to the MDF Request	https://portal.allbound.com/mdf/ekmtiabcd/
MDF Created	Date the MDF Request was submitted	2022-02-15 22:00:54
MDF Updated	Date the MDF Request was last updated	2022-07-11 14:30:24
MDF Submitter	The ID of the user that submitted the MDF request	42
MDF Status	Status of the MDF request	Approved
MDF Proof of Performance Status	Proof of Performance status for the MDF request	Ready for Submission
MDF Request Type	The type of MDF Request, configured as options in the MDF request form	Event
MDF Amount Granted	The currency amount of the MDF request granted to the partner	10000
MDF Denied Reason	The reason the MDF request was denied	Event conflicts with another conference
MDF Returned Reason	The reason the MDF request was returned	POP attendance not attached as csv file
MDF Event Type	The type of event	Trade Show
MDF Event Date	The date of the event	02/16/2022
MDF Demand Generation Type	The type of demand generation campaign	Email Campaign
MDF Campaign Start Date	The start date of the demand generation campaign	2023-05-20
MDF Campaign End Date	The end date of the demand generation campaign	2023-05-30
MDF Advertising Type	The type of advertising	Web
MDF Advertising Frequency	The frequency of advertising	Multiple
MDF Advertising Start Date	The advertising start date	2023-05-08
MDF Advertising End Date	The advertising end date	2023-05-31
MDF Amount Requested	The currency amount of MDF requested	10000
MDF Description	The description of the MDF request as entered by the submitter
Custom MDF Field*	Custom MDF field label	<field value>

*Note: Since the MDF Request form is customizable per portal, your actual Merge Tags may vary.

Lead Related Merge Tags

The following merge tags are available for all triggers that include the (legacy) Lead object as a merge tag. Although the (legacy) Lead object may be repurposed in Allbound and referred to as another object in the front end, PJA still refers to the object as Lead.

Merge Tag	Definition	Example
Lead Link	Link to the Lead	https://portal.allbound.com/lead/nabcgfgfmz/
Lead Created	The date the lead was created	2023-04-28 21:12:30
Lead Updated	The date the lead was last updated	2023-05-21 10:19:10
Lead Status	The status of the lead (if field exists on the re-purposed Lead object)	Submitted
Custom Lead Field*	Custom Lead field label	<field value>

*Note: Since the (legacy) Lead form is customizable per portal, your actual Merge Tags may vary.

If you still have questions, please reach out to your Customer Success Manager or Open a Support Ticket.

Also, please refer to this article to further learn about Partner Journey Automation:

• How to Create Automated Slack Notifications with Zapier
• How to Create Partner Journey Automation Workflows
• How to Create Partner Journey Automation Workflow Actions
• How to Create Partner Journey Automation Workflow Triggers
• How to Manage Partner Journey Automation Workflows
• Glossary for PJA Triggers, Events, and Filters
• How to Create Webhooks for PJA
• Best Practices for Partner Journey Automation