Contents:

• Overview
• UserGems Entry Nodes
• UserGems Tracking Trigger Nodes
• UserGems Updated Tracking Trigger Node
• Appendix
• Sample Flow
• Summary

 

Overview

The UserGems Guided Trigger node will allow Sales Ops, Sales Managers, Marketing Managers, and Customer Success teams to route Leads and Contacts created/updated by UserGems through LeanData’s FlowBuilder. 

UserGems Contact Tracking allows users to see: 

• When a champion has left a job
• Where that champion is working now
• Their new contact information

With the UserGems trigger nodes, you will be able to trigger LeanData Lead and Contact Routing for New and Existing Leads/Contacts via field updates to the UserGems fields on the Lead and/or the Contact Records from the UserGems /SFDC Integration.

 

Example: Kiran is the LeanData Admin for OnPoint Communications. She is currently building their Lead Router Flow. She would like to initiate the routing of Leads when there are changes to the UserGems fields. She configures the UserGems New Tracking and UserGems Updated Tracking nodes to route when there are specific values in specific fields.
Please Note: LeanData leverages your existing UserGems integration with SFDC to trigger routing from updates to the Lead and/or Contact records that are made by the UserGems enrichment in place.

 

UserGems Entry Nodes

There are two entry nodes that will allow you to initiate routing based on UserGems updates to selected fields.

1. UserGems New Tracking Trigger Node
2. UserGems Updated Tracking Trigger Node

These nodes will trigger Lead and/or Contact Routing based on changes to the UserGems fields on a Lead or Contact Record. When you use UserGems and LeanData, additional UserGems fields will typically be added to the Lead and Contact records. Changes in these fields can be used to trigger a Lead or Contact for Routing. These nodes are located on the Trigger menu when you select UserGems.

 

UserGems Tracking Trigger Nodes

If you need to route a new Lead/Contact that has been updated with data from UserGems, you can use the UserGems Tracking Trigger Node to specify the values in the UserGems fields that trigger routing.

 

Description
This field is not required but we recommend adding a description to document any customizations made to the node. If someone else needs to take over the management of the graph, they will be able to understand the goal of the customizations.

Trigger Rules

In the Trigger Rule, specify the condition that will trigger routing. Each condition is made up of a UserGems Lead/Contact field, an operator, and a value. You will also specify the Target for the routing.

This guided trigger node has a default condition, UG - IsAPastUser = true, which allows you to identify job changes tracked by UserGems.

You can edit the default rule to fit your specific situation. You can also add any additional Trigger Rules you need.

 

Click Add Trigger Rule to add additional routing trigger rules.

 

UserGems Updated Tracking Trigger Node

If you need to initiate routing on an existing Lead or Contact that has been updated by UserGems, you can use the UserGems Updated Tracking Trigger Node to specify the values in the UserGems fields that have been changed.

 

Description
This field is not required but we recommend adding a description to document any customizations made to the node. If someone else needs to take over the management of the graph, they will be able to understand the goal of the customizations.

Trigger Rules

The Node has 1 default rule/edge. As you add a new Trigger Rule, you will get a new edge for routing.

This guided trigger node has a default condition UG - IsAPastUser = true, which allows you to identify job changes tracked by UserGems.

 

In a new  Trigger Rule, specify the condition that will trigger routing. Each condition is made up of a UserGems  Lead/Contact field, an operator, and a value. You will also specify the Target for the routing.

You can edit the default rule to fit your specific situation. You can also add any additional Trigger Rules you need.

Click Add Trigger Rule to add additional routing trigger rules.

 

Multiple Trigger Rules

You can create multiple trigger rules as needed on the node. Each new rule creates a new edge for records to follow. If using this entry node, you will have to define at least one rule. You can add additional conditions to the rule and/or add additional rules with conditions, allowing you to have very complex triggering rules.

When you have a rule with multiple conditions, LeanData will assume an AND relationship between the conditions. If you need to use an OR relationship, you will have to create another trigger rule.

When using multiple rules, the node will process each rule sequentially until the record meets a rule, and then it will direct the record using the edge for the corresponding rule.

 

Appendix

With this guide there are 2 sample flows you can import into your Lead and Contact graphs. The two files are:

• UserGems Example Lead Routing Graph.txt
• UserGems Example New Contact Graph.txt

 

Sample Flow

The following example Graph shows a UserGems initiated Lead Router graph.

 

Summary

UserGems Tracking trigger nodes allow you to initiate Lead or Contact routing from fields updated by UserGems. The nodes UserGems New Tracking and UserGems Updated Tracking can initiate routing for new records created with specific values in UserGems fields or reroute records that have been updated by UserGems.

For more information on working with router flows please see our Lead Routing Guide:
/articles/Knowledge/RoutingFlowBuilderInterfaceGuide690203d9ef893

 

 

Attachments:
UserGems_Example_Lead_Routing_Graph.txt
UserGems_Example_New_Contact_Graph.txt