Difference between revisions of "ATC/Current/AdminGuide/ScenarioArchFlows"

From Genesys Documentation
Jump to: navigation, search
(Published)
(Published)
Line 3: Line 3:
 
|DisplayName=Salesforce lead creation and campaign attribution
 
|DisplayName=Salesforce lead creation and campaign attribution
 
|TocName=Salesforce lead creation and campaign attribution
 
|TocName=Salesforce lead creation and campaign attribution
−
|Context=Use {{MINTYDOCSPRODUCT}} to track campaign-related web activity and create leads with their associated campaign attributes in Salesforce. Also provide agents with a script they can use to create and update Salesforce leads.
+
|Context=Use {{MINTYDOCSPRODUCT}} to track campaign-related web activity and create leads with their associated campaign attributes in Salesforce. You can also provide agents with a script that they can use to create and update Salesforce leads.
 
|ComingSoon=No
 
|ComingSoon=No
 
|Platform=PureConnect, GenesysCloud, GenesysEngage-cloud
 
|Platform=PureConnect, GenesysCloud, GenesysEngage-cloud
Line 18: Line 18:
 
**'''Scripter''' > '''Published Script''' > '''Add''', '''View''' (to add agent-facing scripts)
 
**'''Scripter''' > '''Published Script''' > '''Add''', '''View''' (to add agent-facing scripts)
 
**'''Scripter''' > '''Script''' > '''All''' (to create agent-facing scripts)
 
**'''Scripter''' > '''Script''' > '''All''' (to create agent-facing scripts)
−
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=Deploy the {{MINTYDOCSPRODUCT}} tracking snippet}} on the website you want to track. This enables you to trigger the action map based on pageview events.
+
*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Tracking_snippet|display text=Deploy the {{MINTYDOCSPRODUCT}} tracking snippet}} on the website to track so that you can trigger the action map based on pageview events.
−
*To trigger an action map based on other events, use {{Link-AnywhereElse|product=ATC|version=Current|manual=SDK|topic=Record|display text=ac('record')}} to send {{MINTYDOCSPRODUCT}} data about events you want to track.
+
*To trigger an action map based on other events, use {{Link-AnywhereElse|product=ATC|version=Current|manual=SDK|topic=Record|display text=ac('record')}} to send {{MINTYDOCSPRODUCT}} data about the events to track.
 
|Section={{Section
 
|Section={{Section
 
|sectionHeading=Configuration overview
 
|sectionHeading=Configuration overview
Line 30: Line 30:
 
#Prepare the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=PrepIntDataActions|display text=Salesforce data actions integration}}.
 
#Prepare the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=PrepIntDataActions|display text=Salesforce data actions integration}}.
 
#Prepare the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=PrepIntDataActions|display text=Salesforce data actions}}.
 
#Prepare the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=PrepIntDataActions|display text=Salesforce data actions}}.
−
#Get the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=AFSFExampleWorkflow|display text=Salesforce Lead Creation and and Campaign Attribution example workflow}}.
+
#Get the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=AFSFExampleWorkflow|display text=Salesforce Lead Creation and Campaign Attribution example workflow}}.
 
#In Genesys Cloud Architect, prepare {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=BuildArchFlows|anchor=AFWorkflow|display text=a workflow}}.
 
#In Genesys Cloud Architect, prepare {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=BuildArchFlows|anchor=AFWorkflow|display text=a workflow}}.
 
#Prepare an {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=SFAFActionMap|display text=action map to use the Architect flow action}}.
 
#Prepare an {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=SFAFActionMap|display text=action map to use the Architect flow action}}.
 
#Monitor your Architect flow action with a {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=MonitorArchFlows|display text=report}}.
 
#Monitor your Architect flow action with a {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=MonitorArchFlows|display text=report}}.
−
#'''Genesys Cloud users:''' Optionally use scripts to help agents view and create a Salesforce lead:
+
#'''Genesys Cloud users:''' (Optional) Use scripts to help agents view and create a Salesforce lead:
−
#*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=SalesforceScripts|display text=Learn }} about the Salesforce Lead Creation and Campaign Attribution script.
+
#*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=SalesforceScripts|display text=Learn }} about the Salesforce Lead Creation and Campaign Attribution script
−
#*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=AFSFScriptDownload|display text=Download}} theSalesforce Lead Creation and Campaign Attribution script.
+
#*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=AFSFScriptDownload|display text=Download}} the Salesforce Lead Creation and Campaign Attribution script
−
#*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=AFSFScriptConfAgent|display text=Configure}} agent accounts.
+
#*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=AFSFScriptConfAgent|display text=Configure}} agent accounts
−
#*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=AFSFScriptAgentAccess|display text=Communicate}} with agents about how to access and use the Salesforce Lead Creation and Campaign Attribution script.
+
#*{{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=AFSFScriptAgentAccess|display text=Communicate}} with agents about how to access and use the Salesforce Lead Creation and Campaign Attribution script
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 44: Line 44:
 
|anchor=PrepareCampaign
 
|anchor=PrepareCampaign
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=Please use the following UTM parameters to track campaign-related activity on your website:
+
|structuredtext=Use the following UTM parameters to track campaign-related activity on your website:
  
 
*Campaign ID
 
*Campaign ID
Line 51: Line 51:
 
*Email
 
*Email
  
−
For more information on configuring UTM parameters, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Campaign_Attributes}}.
+
For more information about configuring UTM parameters, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Campaign_Attributes}}.
  
 
<br />
 
<br />
Line 59: Line 59:
 
|anchor=SFUserAcct
 
|anchor=SFUserAcct
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=In Salesforce, create a [https://help.mypurecloud.com/articles/?p=177867 dedicated user account] with the appropriate rights to use the Salesforce data action integration on behalf of {{MINTYDOCSPRODUCT}}. This user account will act on behalf of your entire organization to perform the data actions that are needed for the Salesforce integration.
+
|structuredtext=In Salesforce, create a [https://help.mypurecloud.com/articles/?p=177867 dedicated user account] with the appropriate rights to use the Salesforce data action integration on behalf of {{MINTYDOCSPRODUCT}}. This user account acts on behalf of your entire organization to perform the data actions needed for the Salesforce integration.
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 78: Line 78:
 
#Download the required Salesforce data actions. For download links and descriptions, see the table that follows these instructions.
 
#Download the required Salesforce data actions. For download links and descriptions, see the table that follows these instructions.
 
#[https://help.mypurecloud.com/articles/?p=161024 Import the data actions] and associate them with the Salesforce data actions integration.
 
#[https://help.mypurecloud.com/articles/?p=161024 Import the data actions] and associate them with the Salesforce data actions integration.
−
#Optionally [https://help.mypurecloud.com/articles/?p=141929 test the setup of your contract.]
+
#(Optional) [https://help.mypurecloud.com/articles/?p=141929 test the setup of your contract.]
 
#Save and publish the data actions.
 
#Save and publish the data actions.
  
−
{{NoteFormat|You need all of the following data actions.
+
{{NoteFormat|You need all the data actions in the following table.
  
−
These data actions are specifically designed to work with the Architect workflow. Do not modify them in any way.|}}
+
These data actions work with the Architect workflow specifically. Do not modify them in any way.|}}
 
|structuredtextwide====Salesforce data actions download links===
 
|structuredtextwide====Salesforce data actions download links===
 
{{{!}} class="wikitable"
 
{{{!}} class="wikitable"
Line 89: Line 89:
 
!Download link
 
!Download link
 
!When you pass this information to the data action...
 
!When you pass this information to the data action...
−
!The data action does this...
+
!The data action...
 
{{!}}-
 
{{!}}-
 
{{!}}{{Repository|Salesforce-Associate-With-Campaign.json||Salesforce-Associate-With-Campaign.json}}
 
{{!}}{{Repository|Salesforce-Associate-With-Campaign.json||Salesforce-Associate-With-Campaign.json}}
−
{{!}}Campaign Id and a lead Id
+
{{!}}Campaign ID and a lead ID
−
{{!}}Calls the salesforce API to include the lead in the campaign
+
{{!}}Calls the Salesforce API to include the lead in the campaign.
 
{{!}}-
 
{{!}}-
 
{{!}}{{Repository|Salesforce-Check-if-Lead-is-Associated-With-Campaign.json||Salesforce-Check-if-Lead-is-Associated-With-Campaign.json}}
 
{{!}}{{Repository|Salesforce-Check-if-Lead-is-Associated-With-Campaign.json||Salesforce-Check-if-Lead-is-Associated-With-Campaign.json}}
−
{{!}}Campaign Id and an email
+
{{!}}Campaign ID and an email
−
{{!}}Returns a lead Id if the member is part of the campaign
+
{{!}}If the member is part of the campaign, returns a lead ID.
 
{{!}}-
 
{{!}}-
 
{{!}}{{Repository|Salesforce-Create-Lead-By-Email.json||Salesforce-Create-Lead-By-Email.json}}
 
{{!}}{{Repository|Salesforce-Create-Lead-By-Email.json||Salesforce-Create-Lead-By-Email.json}}
 
{{!}}Lead information
 
{{!}}Lead information
−
{{!}}Creates a lead in Salesforce with the attributes you specify
+
{{!}}Creates a lead in Salesforce with the attributes that you specify.
 
{{!}}-
 
{{!}}-
 
{{!}}{{Repository|Salesforce-Get-Campaign-Id-From-Campaign-Name.json||Salesforce-Get-Campaign-Id-From-Campaign-Name.json}}
 
{{!}}{{Repository|Salesforce-Get-Campaign-Id-From-Campaign-Name.json||Salesforce-Get-Campaign-Id-From-Campaign-Name.json}}
 
{{!}}Campaign name
 
{{!}}Campaign name
−
{{!}}Returns the campaign Id that matches the name
+
{{!}}Returns the campaign ID that matches the name.
 
{{!}}-
 
{{!}}-
 
{{!}}{{Repository|Salesforce-Get-Lead-By-Email.json||Salesforce-Get-Lead-By-Email.json}}
 
{{!}}{{Repository|Salesforce-Get-Lead-By-Email.json||Salesforce-Get-Lead-By-Email.json}}
 
{{!}}Email address
 
{{!}}Email address
−
{{!}}Retrieves the lead attributes associated with the email address
+
{{!}}Retrieves the lead attributes associated with the email address.
 
{{!}}}
 
{{!}}}
 
|Status=No
 
|Status=No
Line 120: Line 120:
 
|structuredtext=The Salesforce Lead Generation example workflow associates a lead with a specified campaign in Salesforce.  
 
|structuredtext=The Salesforce Lead Generation example workflow associates a lead with a specified campaign in Salesforce.  
  
−
*If the lead exists, then the workflow associates it with the campaign.
+
*If the lead exists, the workflow associates it with the campaign.
−
*If the lead does not exist, then the workflow creates the lead and associates it with the campaign.
+
*If the lead does not exist, the workflow creates the lead and associates it with the campaign.
  
−
You can provide the campaign ID directly to the workflow. If you do not provide the campaign ID, the workflow attempts to extract the UTM campaign from the session Id to complete the association.
+
You can provide the campaign ID to the workflow directly. If you do not provide the campaign ID, the workflow attempts to extract the UTM campaign from the session ID to complete the association.
  
 
#{{Repository|Salesforce-Lead-Creation-And-Campaign-Attribution.i3WorkFlow||Click here to download the Salesforce-Lead-Creation-And-Campaign-Attribution.i3WorkFlow}}
 
#{{Repository|Salesforce-Lead-Creation-And-Campaign-Attribution.i3WorkFlow||Click here to download the Salesforce-Lead-Creation-And-Campaign-Attribution.i3WorkFlow}}
Line 136: Line 136:
 
|Media=Video
 
|Media=Video
 
|image=408878976
 
|image=408878976
−
|structuredtext====Build the action map===
+
|structuredtext====Create the action map===
−
Follow {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Use_the_Architect_flow_with_an_action_map|anchor=ArchFlowActionMap|display text=these instructions}} to build an action map that uses the Architect flow action.{{NoteFormat|You can use the Journey JavaScript SDK to track custom events and trigger action maps when they occur. To do this, start by tracking custom events with the ac(record') method. Then, select user activity as the trigger for the action map and select the specific custom event you want.|2}}
+
Follow {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Use_the_Architect_flow_with_an_action_map|anchor=ArchFlowActionMap|display text=these instructions}} to create an action map that uses the Architect flow action.{{NoteFormat|You can use the Journey JavaScript SDK to track custom events and trigger action maps when they occur. Start by tracking custom events with the ac(record') method. Then, select user activity as the trigger for the action map and select the custom event that you want.|2}}
  
 
===Override the default variable values===
 
===Override the default variable values===
−
To create the new Salesforce lead with a richer set of journey data, you must override the default settings of these variables and tell {{MINTYDOCSPRODUCT}} where to obtain the user-specific values.
+
To create the new Salesforce lead with a richer set of journey data, override the default settings of these variables and tell {{MINTYDOCSPRODUCT}} where to obtain the user-specific values.
  
−
#Next to the variable you want to override, under '''Action''' click '''Edit'''.
+
#Next to the variable to override, under '''Action''' click '''Edit'''.
 
#Select the '''Override the initial value for this action map''' check box.
 
#Select the '''Override the initial value for this action map''' check box.
−
#From the '''New value''' list, select the value you want to send to the data action.
+
#From the '''New value''' list, select the value to send to the data action.
−
#*'''Static value''': This is a unique identifier that {{MINTYDOCSPRODUCT}} creates for every user.
+
#*'''Static value''': Unique identifier that {{MINTYDOCSPRODUCT}} creates for every user.
−
#*'''Session''': This is a unique identifier that helps track user activity over time. For more information on how the session ID is used with Architect, see [https://help.mypurecloud.com/articles/?p=215371 Get Journey Session action].
+
#*'''Session''': Unique identifier that helps track user activity over time. For more information about using the session ID with Architect, see [https://help.mypurecloud.com/articles/?p=215371 Get Journey Session action].
−
#*'''External Contact ID''': This is a unique identifier that maps a user across the Genesys suite of products.
+
#*'''External Contact ID''': Unique identifier that maps a user across the Genesys suite of products.
 
#*'''Other values''':
 
#*'''Other values''':
−
#**Event attribute: If you use trigger the action map based on a form_submitted event, the form fields appear here.
+
#**'''Event attribute:''' If you trigger the action map based on a form_submitted event, the form fields appear here.
 
#If a second list appears, select the source of the value.
 
#If a second list appears, select the source of the value.
 
#Click '''Override'''.
 
#Click '''Override'''.
−
#Repeat these steps for all of the variables you want to override.
+
#Repeat these steps for all the variables to override.
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 160: Line 160:
 
|Media=Image
 
|Media=Image
 
|image=gpe_salesforce_agent_script_lead_diagram.png
 
|image=gpe_salesforce_agent_script_lead_diagram.png
−
|structuredtext={{NoteFormat|Scripting is available for Genesys Cloud users only.|}}A script is a set of instructions that helps agents as they interact with users. {{MINTYDOCSPRODUCT}} provides a script template that shares existing lead-related information about a user from Salesforce. If no Salesforce record exists for the user, the script helps the agent create a lead record in Salesforce, if appropriate. Salesforce lead information for a user is displayed and collected in a widget. To make this work, download both the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=AFSFScriptDownload|display text=script template and data actions}}.  
+
|structuredtext={{NoteFormat|Scripting is available for Genesys Cloud customers only.|}}A script is a set of instructions that helps agents as they interact with users. {{MINTYDOCSPRODUCT}} provides a script template that shares existing lead-related information about a user from Salesforce. If no Salesforce record exists for the user, the script helps the agent create a lead record in Salesforce, if appropriate. Salesforce lead information for a user displays and collects in a widget. To make this work, download both the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=AFSFScriptDownload|display text=script template and data actions}}.  
  
−
For general information about scripts, see:
+
For more information about scripts, see:
  
 
*[https://help.mypurecloud.com/articles/?p=54284 About scripting]
 
*[https://help.mypurecloud.com/articles/?p=54284 About scripting]
−
*[https://help.mypurecloud.com/articles/?p=194115 About widgets for webchat]
+
*[https://help.mypurecloud.com/articles/?p=194115 About widgets for web chat]
 
*[https://help.mypurecloud.com/articles/?p=63968 Use scripts]
 
*[https://help.mypurecloud.com/articles/?p=63968 Use scripts]
 
|Status=No
 
|Status=No
Line 179: Line 179:
 
!Download link
 
!Download link
 
!When you pass this information to the data action...
 
!When you pass this information to the data action...
−
!The data action does this...
+
!The data action...
 
{{!}}-
 
{{!}}-
 
{{!}}{{Repository|Salesforce-Create-Lead-By-Email.json||Salesforce-Create-Lead-By-Email.json}}
 
{{!}}{{Repository|Salesforce-Create-Lead-By-Email.json||Salesforce-Create-Lead-By-Email.json}}
 
{{!}}Lead information
 
{{!}}Lead information
−
{{!}}Creates a lead in Salesforce with the attributes you specify
+
{{!}}Creates a lead in Salesforce with the attributes that you specify.
 
{{!}}-
 
{{!}}-
 
{{!}}{{Repository|Salesforce-Get-Lead-By-Email.json||Salesforce-Get-Lead-By-Email.json}}
 
{{!}}{{Repository|Salesforce-Get-Lead-By-Email.json||Salesforce-Get-Lead-By-Email.json}}
 
{{!}}Email address
 
{{!}}Email address
−
{{!}}Retrieves the lead attributes associated with the email address
+
{{!}}Retrieves the lead attributes associated with the email address.
 
{{!}}-
 
{{!}}-
 
{{!}}{{Repository|Salesforce-Update-Lead-By-Id.json||Salesforce-Update-Lead-By-Id.json}}
 
{{!}}{{Repository|Salesforce-Update-Lead-By-Id.json||Salesforce-Update-Lead-By-Id.json}}
 
{{!}}Lead information
 
{{!}}Lead information
−
{{!}}Updates an existing lead in Salesforce with the specified attributes
+
{{!}}Updates an existing lead in Salesforce with the specified attributes.
 
{{!}}}<br />
 
{{!}}}<br />
 
|Status=No
 
|Status=No
Line 198: Line 198:
 
|anchor=AFSFScriptConfAgent
 
|anchor=AFSFScriptConfAgent
 
|alignment=Vertical
 
|alignment=Vertical
−
|structuredtext=In order for an agent to use the Salesforce script, you must configure the agent's account with the following permissions:
+
|structuredtext=To allow an agent to use the Salesforce script, configure the agent's account with the following permissions:
  
 
*'''Integrations'''> '''Action '''> '''Execute''' permission
 
*'''Integrations'''> '''Action '''> '''Execute''' permission
 
*'''Scripter''' > '''Published Script''' > '''View''' (to view agent-facing scripts)
 
*'''Scripter''' > '''Published Script''' > '''View''' (to view agent-facing scripts)
  
−
Agents will use the same dedicated {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=SFUserAcct|display text=Salesforce user account}} that {{MINTYDOCSPRODUCT}} uses to view and update leads in Salesforce.
+
Agents use the same dedicated {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=ScenarioArchFlows|anchor=SFUserAcct|display text=Salesforce user account}} that {{MINTYDOCSPRODUCT}} uses to view and update leads in Salesforce.
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 211: Line 211:
 
|Media=Image
 
|Media=Image
 
|image=AgentScriptNew1.png
 
|image=AgentScriptNew1.png
−
|structuredtext=Scripts automatically appear in the [https://help.mypurecloud.com/?p=700 Interaction panel] for voice interactions.  
+
|structuredtext=Scripts appear in the [https://help.mypurecloud.com/?p=700 Interaction panel] for voice interactions.  
  
−
To access a script, an agent clicks this icon:
+
To access a script, an agent clicks the following icon:
  
 
[[File:Scripticon.png|full|46x46px|link=https://all.docs.genesys.com/File:Scripticon.png]]
 
[[File:Scripticon.png|full|46x46px|link=https://all.docs.genesys.com/File:Scripticon.png]]
−
|structuredtextwide=When the script opens, the agent can see whether the user is an existing lead or not. The agent can then complete the form to create or update the lead as necessary.
+
|structuredtextwide=When the script opens, the agent can see whether the user is an existing lead. The agent can then complete the form to create or update the lead as necessary.
  
 
[[File:JourneyLeadScriptEx.png|alt=Agent script with Salesforce ID|full|link=https://all.docs.genesys.com/File:JourneyLeadScriptEx.png]]
 
[[File:JourneyLeadScriptEx.png|alt=Agent script with Salesforce ID|full|link=https://all.docs.genesys.com/File:JourneyLeadScriptEx.png]]

Revision as of 16:22, December 17, 2020

This topic is part of the manual Genesys Predictive Engagement Administrator's Guide for version Current of Genesys Predictive Engagement.

Use Genesys Predictive Engagement to track campaign-related web activity and create leads with their associated campaign attributes in Salesforce. You can also provide agents with a script that they can use to create and update Salesforce leads.

Prerequisites

  • Configure the following permissions in Genesys Cloud:
    • Architect > Flow > All
    • Architect > UI > All
    • Integrations > Integration > All
    • Integrations > Action > All
    • Journey > Action Map > All
    • Journey > Event Type > View (to configure an action map with an event trigger)
    • Journey > Report > View
    • Scripter > Published Script > Add, View (to add agent-facing scripts)
    • Scripter > Script > All (to create agent-facing scripts)
  • Deploy the Genesys Predictive Engagement tracking snippet on the website to track so that you can trigger the action map based on pageview events.
  • To trigger an action map based on other events, use ac('record') to send Genesys Predictive Engagement data about the events to track.

Configuration overview

  1. Prepare your web campaign.
  2. Create a dedicated Salesforce user.
  3. Prepare the Salesforce data actions integration.
  4. Prepare the Salesforce data actions.
  5. Get the Salesforce Lead Creation and Campaign Attribution example workflow.
  6. In Genesys Cloud Architect, prepare a workflow.
  7. Prepare an action map to use the Architect flow action.
  8. Monitor your Architect flow action with a report.
  9. Genesys Cloud users: (Optional) Use scripts to help agents view and create a Salesforce lead:
    • Learn about the Salesforce Lead Creation and Campaign Attribution script
    • Download the Salesforce Lead Creation and Campaign Attribution script
    • Configure agent accounts
    • Communicate with agents about how to access and use the Salesforce Lead Creation and Campaign Attribution script

Prepare your web campaign with UTM parameters

Use the following UTM parameters to track campaign-related activity on your website:

  • Campaign ID
  • Last name
  • First name
  • Email

For more information about configuring UTM parameters, see Campaign attributes.


Create a dedicated Salesforce user

In Salesforce, create a dedicated user account with the appropriate rights to use the Salesforce data action integration on behalf of Genesys Predictive Engagement. This user account acts on behalf of your entire organization to perform the data actions needed for the Salesforce integration.

Prepare the Salesforce integration and data actions

Prepare the Salesforce data actions integration

  1. In Genesys Cloud, go to Admin > Integrations > Integrations.
  2. Click + Integrations.
  3. Install a Salesforce data actions integration.
  4. On the Configuration tab, configure the credentials to use the dedicated Salesforce user account that you created in your Salesforce organization.

Prepare the Salesforce data actions

  1. Download the required Salesforce data actions. For download links and descriptions, see the table that follows these instructions.
  2. Import the data actions and associate them with the Salesforce data actions integration.
  3. (Optional) test the setup of your contract.
  4. Save and publish the data actions.
Important
You need all the data actions in the following table. These data actions work with the Architect workflow specifically. Do not modify them in any way.

Salesforce data actions download links

Download link When you pass this information to the data action... The data action...
Salesforce-Associate-With-Campaign.json Campaign ID and a lead ID Calls the Salesforce API to include the lead in the campaign.
Salesforce-Check-if-Lead-is-Associated-With-Campaign.json Campaign ID and an email If the member is part of the campaign, returns a lead ID.
Salesforce-Create-Lead-By-Email.json Lead information Creates a lead in Salesforce with the attributes that you specify.
Salesforce-Get-Campaign-Id-From-Campaign-Name.json Campaign name Returns the campaign ID that matches the name.
Salesforce-Get-Lead-By-Email.json Email address Retrieves the lead attributes associated with the email address.

Prepare the Salesforce Lead Creation and Campaign Attribution example workflow

The Salesforce Lead Generation example workflow associates a lead with a specified campaign in Salesforce.

  • If the lead exists, the workflow associates it with the campaign.
  • If the lead does not exist, the workflow creates the lead and associates it with the campaign.

You can provide the campaign ID to the workflow directly. If you do not provide the campaign ID, the workflow attempts to extract the UTM campaign from the session ID to complete the association.

  1. Click here to download the Salesforce-Lead-Creation-And-Campaign-Attribution.i3WorkFlow
  2. Associate the data actions.
  3. Publish the workflow.
  4. Switch to Architect to prepare the workflow.

Prepare an action map to use an Architect flow action

Create the action map

Follow these instructions to create an action map that uses the Architect flow action.
Tip
You can use the Journey JavaScript SDK to track custom events and trigger action maps when they occur. Start by tracking custom events with the ac(record') method. Then, select user activity as the trigger for the action map and select the custom event that you want.

Override the default variable values

To create the new Salesforce lead with a richer set of journey data, override the default settings of these variables and tell Genesys Predictive Engagement where to obtain the user-specific values.

  1. Next to the variable to override, under Action click Edit.
  2. Select the Override the initial value for this action map check box.
  3. From the New value list, select the value to send to the data action.
    • Static value: Unique identifier that Genesys Predictive Engagement creates for every user.
    • Session: Unique identifier that helps track user activity over time. For more information about using the session ID with Architect, see Get Journey Session action.
    • External Contact ID: Unique identifier that maps a user across the Genesys suite of products.
    • Other values:
      • Event attribute: If you trigger the action map based on a form_submitted event, the form fields appear here.
  4. If a second list appears, select the source of the value.
  5. Click Override.
  6. Repeat these steps for all the variables to override.

Scripting: Use a script to help agents view, create, and update a Salesforce lead

Important
Scripting is available for Genesys Cloud customers only.
A script is a set of instructions that helps agents as they interact with users. Genesys Predictive Engagement provides a script template that shares existing lead-related information about a user from Salesforce. If no Salesforce record exists for the user, the script helps the agent create a lead record in Salesforce, if appropriate. Salesforce lead information for a user displays and collects in a widget. To make this work, download both the script template and data actions.

For more information about scripts, see:

Download the Salesforce Lead Generation script template and data actions

  1. Click here to download the Genesys Predictive Engagement-Salesforce-View-Create-Update-Lead-Script.script
  2. Download the required data actions. For more information, see the following table.
Download link When you pass this information to the data action... The data action...
Salesforce-Create-Lead-By-Email.json Lead information Creates a lead in Salesforce with the attributes that you specify.
Salesforce-Get-Lead-By-Email.json Email address Retrieves the lead attributes associated with the email address.
Salesforce-Update-Lead-By-Id.json Lead information Updates an existing lead in Salesforce with the specified attributes.

Configure agent accounts

To allow an agent to use the Salesforce script, configure the agent's account with the following permissions:

  • Integrations> Action > Execute permission
  • Scripter > Published Script > View (to view agent-facing scripts)

Agents use the same dedicated Salesforce user account that Genesys Predictive Engagement uses to view and update leads in Salesforce.

How agents access and use the Salesforce Lead Generation script

Scripts appear in the Interaction panel for voice interactions.

To access a script, an agent clicks the following icon:

full

When the script opens, the agent can see whether the user is an existing lead. The agent can then complete the form to create or update the lead as necessary.

Agent script with Salesforce ID

Retrieved from "https://all.docs.genesys.com/ATC/Current/AdminGuide/ScenarioArchFlows (2025-06-19 18:57:33)"
Comments or questions about this documentation? Contact us for support!