Hi! I'm wondering if anyone has ideas for sending Pardot form submissions to Salesforce in an easy/comprehensive way for the Sales team to easily view the form submitted data? Currently, we're using default/consistent fields on a Prospect to capture data to limit the need for customization, but each form may require 1, 2, 3, etc. unique fields depending on the form type. This can lead to 1) a lot of custom fields to manage 2) Sales needs to view a lot of fields to find the correct data. I've seen ideas for using the 'Comments' field to append the entire form submitted data and have a running list of these submissions, but this can also get very messy. The goal would be to have a similar form submission data capture as the 'Notify User' email that gets sent from Pardot, but this would be in Salesforce. Am I maybe missing something? Thoughts? Just looking to improve on what we're currently doing! Thanks!
@Adam Erstelle makes sense! I tried rewording this post/question to make more sense 😅 Few other questions...
- I assume I can use the "Assign to queue" Completion Action instead of "Assign to user"?
- Can I set up two conditional completion actions (can I even set up conditional completion actions or will this impact the external action being related to a new Lead that wasn't assigned/in the system before the form submission?) on the form? Any concerns here as I know Completion actions execute randomly (not in order)? An Engagement Studio Program is recommended and I've done that in the past, but due to needing to assign new Leads to a User on the form Completion Actions for the External Action to relate the form submission detials to the record (Contact or Lead), that's not a possibility.
- Reason/Goal: I want to assign new Leads (not assigned) to a Queue and not create a SF Task (the external action will relate the form submission details to the Lead record). I want to create SF Tasks for existing records (Lead or Contact) and route them to a Queue (the external action will relate the form submission details to the existing Lead or Contact record). Similar to this set up here as far as new Leads vs. Re-Engagements. Creating a Task for every new Lead, like in that example, duplicates effort and makes it harder to tell re-engagements apart from new Leads.
- Here are the Queue's:
- Not yet assigned → "Assign to Queue"
- Already assigned → "Create a SF Task"
- Note: we’ll only have one Lead Queue to start + the SF Task Queue (a Flow is created to route SF Tasks from a dummy User to the Queue).
- Testing Findings: I tested the conditional completion actions listed above and here is what I found:
- New Lead: if it's a new Lead (not assigned) and they submit the form, then they are assigned to the Queue and no SF Task is created.
- Existing Record (Lead or Contact): If they're an existing record and assigned, then a SF Task is created.
- The form submission detail external action would fire in each scenario.
I'm also considering adding logic in the form submission detail autolaunched Flow to create a Task for records older than a specific timeframe (day, hour, minutes, etc).
End Goal:- New Leads (not assigned in Pardot before form submission): added to a Lead Queue in Salesforce with the form submission details related.
- Existing Records (Leads or Contacts assigned in Pardot/Syncing prior to the form submission): create a SF Task and assign it to the SF Task Queue. Form Submissions details related to the Contact or Lead record.
Thoughts?
Thanks!
