Frequently Asked Questions (FAQ)
What is the LeadPerfection integration?
It is a LeadConduit recipient integration that enables you to post leads directly into a LeadPerfection account, using a standard pre‑configured integration.
Why is the LeadPerfection integration important?
It ensures that leads are delivered accurately into a LeadPerfection CRM system with all critical identifiers intact, facilitating proper follow‑up and comprehensive lead attribution.
How do I use the LeadPerfection integration?
To use it, add a Recipient Step in your LeadConduit flow, select the LeadPerfection integration, and then configure it by ensuring you provide the correct Client ID and credentials. The Client ID is effectively the database name for the brand, and it’s unique to each brand. The username and password should be for the company’s use only (not for an existing user), and the username must have API access checked.
How can I verify that the integration is working correctly?
Send a test lead through your LeadConduit flow and check the LeadConduit Events screen as well as the LeadPerfection account to ensure all fields are mapped properly and that the lead is received without errors.
What is the endpoint used to deliver leads to LeadPerfection?
The endpoint is formatted as https://lppost.leadperfection.com/{{client_id}}/{{action}}
{{client_id}} is your LeadPerfection Client ID (effectively the database name for the brand) and is unique to each brand.
{{action}} is set to addlead by default; you can change this from the Field Mappings step if needed.
How often is conversion feedback retrieved from LeadPerfection?
Unlike Salesforce, which allows for the retrieval of conversion feedback in real-time, LeadPerfection conversion feedback will be initially retrieved approximately every hour.
Can I use LeadPerfection conversion feedback with my Custom Delivery Step to LeadPerfection?
LeadPerfection conversion feedback can only be retrieved with the standard LeadPerfection - Add Lead integration.
Are there any required fields for conversion feedback?
Yes, the LeadConduit’s Event ID is required for retrieving conversion feedback. LeadConduit automatically maps this field for you, but in case you have overridden the default mapping, LeadConduit won’t be able to retrieve conversion feedback from the leads that are missing this information.
Can I enable conversion feedback after creating my LeadPerfection recipient?
Yes, if you created your LeadConduit recipient using the Add Lead integration, you can enable conversion feedback by navigating to your step, opening the Feedback Settings section, and enabling the Receive Lead Conversions toggle.
How can I see the conversion feedback received from LeadPerfection?
To see any conversion feedback received from LeadPerfection, you can check your Flow dashboard, create a Report, or go into the lead event details:
Is there a report for LeadPerfection conversion feedback created by default?
Currently a Conversion Feedback report for LeadPerfection is not created by default, but you can easily create a report like the following:
With the configurations listed below:
- Columns: Enable Conversion Received Submitted, Conversion Received Success, Conversion Received Failure and Conversion Received Error
- Groupings: Add Source Name and Feedback Reason
Which LeadPerfection fields are automatically mapped by LeadConduit?
LeadConduit maps the following LeadPerfection fields by default:
| LeadConduit field | LeadPerfection field | Description |
|---|---|---|
| First Name | firstname | Lead first name |
| Last Name | lastname | Lead surname |
| Address 1 | address1 | Lead address |
| City | city | Lead city |
| State | state | Lead state |
| Postal Code | zip | Lead postal code (ZIP) |
| Phone 1 | phone1 | Lead phone 1 |
| Phone 2 | phone2 | Lead phone 2 |
| Phone 3 | phone3 | Lead phone 3 |
| Product | productid | ProductID - the lead’s primary product interest |
| Lead email | ||
| Source Name | sender | The name of the source that submitted the lead into your Flow |
| SRS ID | srs_id | ID of the source and sub source |
| TrustedForm Cert URL | TrustedForm | TrustedForm certificate URL |
| Universal Id | Jornaya | Jornaya universal lead token |
| LeadConduit Event ID | EventID | Event ID; defaults to LeadConduit event ID |
| TrustedForm Age In Seconds | LeadAge | Age of lead (defaults to value of TrustedForm age_in_seconds, if available) |
| TrustedForm Page URL | WebsiteOrigin | Website origin (defaults to value of TrustedForm page_url, if available) |
| TrustedForm Verify Languages | ConsentLanguage | Consent Language (defaults to concatenated values of TrustedForm Verify languages, if available) |
| Comments | Comments | Comments |
| LeadPerfection Username | username | LeadPerfection Username |
| LeadPerfection Password | password | LeadPerfection Password |
If you want to override any of these, simply add them to the Fields Mapping of your LeadPerfection step.
Which fields are available in the LeadPerfection integration?
Besides the fields listed above, you can map the following fields from the Fields Mapping section of your LeadPerfection step:
| LeadPerfection field | Description |
|---|---|
| Client Id | LeadPerfection client ID (unique to each brand—effectively the database name), used in posting URL |
| Action | Action to perform in LeadPerfection, defaults to “addlead” |
| Phone2type | LeadPerfection code for lead phone 2 |
| Phone3type | LeadPerfection code for lead phone 3 |
| Proddescr | Product description, if other than ProductID |
| LogNumber | Vendor’s unique lead ID |
| Sender | Vendor’s company name, defaults to flow source name |
| Sentto | |
| Notes | Information that does not have a field in LeadPerfection, such as user-entered data |
| Pro Id | The employee ID of the promoter who generated the lead |
| Appointment Date | The appointment date |
| Appointment Time | The appointment time |
| Rnk Id | The rank or “grade” of the lead |
| Waiver | True when a DNC waiver is associated with the submitted lead |
| User1 | User field 1 (character field) |
| User2 | User field 2 (character field) |
| User3 | User field 3 (character field) |
| User4 | User field 4 (character field) |
| User5 | User field 5 (character field) |
| User6 | User field 6 (date-time field) |
| User7 | User field 7 (date-time field) |
| User8 | User field 8 (date-time field) |
| User9 | User field 9 (date-time field) |
| User10 | User field 10 (date-time field) |
| User11 | User field 11 (money field) |
| User12 | User field 12 (money field) |
| User13 | User field 13 (money field) |
| User14 | User field 14 (money field) |
| User15 | User field 15 (money field) |
| User16 | User field 16 (integer field) |
| User17 | User field 17 (integer field) |
| User18 | User field 18 (integer field) |
| User19 | User field 19 (integer field) |
| User20 | User field 20 (integer field) |
| HasConsent | True if the vendor has consent |
| ConsentDate | Date of consent |
| ConsentCapturedID | ID of captured consent |
| ConsentMethod | Consent method |
| CallOptIn | Call opt-in |
| CallOptInDate | Call opt-in date |
| TextOptIn | Text opt-in |
| TextOptInDate | Text opt-in date |
| EmailOptIn | Email opt-in |
| EmailOptInDate | Email opt-in date |
| ContactPreference | Contact preference |
How to migrate from the “Create Lead” (deprecated) integration?
-
Follow the Step‑by‑Step Instructions listed in the top of this article.
-
Considering the LeadPerfection fields that LeadConduit automatically maps (you can find them in the previous FAQ from this article), copy any additional mappings that the Create Lead step might have into the LeadPerfection Add Lead step created in the previous step.
-
For instance, if you have a mapping for user11 in your Create Lead recipient, like the following:
-
You should map it with the corresponding field in your new Add Lead step:
-
-
You should also copy any additional configurations you may have in your Create Lead step, such as Step Criteria or Volume Caps.
-
Finally, submit a test lead to ensure your new LeadPerfection recipient is working correctly, and disable your LeadPerfection Create Lead step to avoid submitting duplicate leads into your LeadPerfection account.
How to migrate from a Custom Step?
-
Follow the Step‑by‑Step Instructions listed in the top of this article.
-
Considering the LeadPerfection fields that LeadConduit automatically maps (you can find them in the previous FAQ from this article), copy any additional mappings that the Custom Step might have into the LeadPerfection step created in the previous step.
-
For instance, if you have a mapping for pro_id, like the following:
-
You should map it with the corresponding field in your new LeadPerfection step
-
-
You should also copy any additional configurations you may have in your Custom Step step, such as Step Criteria or Volume Caps.
-
Finally, submit a test lead to ensure your new LeadPerfection recipient is working correctly, and disable your LeadPerfection Custom Step to avoid submitting duplicate leads into your LeadPerfection account.
What do I need to use conversion feedback?
LeadPerfection feedback must be enabled/approved per account by LeadPerfection.
Reach out to LeadPerfection to confirm:
- Your account is using the correct endpoint:
https://lppost.leadperfection.com/{{client_id}}/addlead - Any account-specific changes required by LeadPerfection are complete before you enable conversion feedback in ActiveProspect.
Which fields are returned with LeadPerfection feedback?
LeadPerfection feedback returns the following set of fixed fields (unlike Salesforce, which allows selectable feedback fields):
| Field | Description |
|---|---|
| Type | Set to conversion by default. |
| Reason | The lead’s current disposition (may change as the lead is worked), e.g., Data, Set, or customer-defined values. |
| CallsCount | Number of calls made since the lead was received. |
| ApptDate | Current appointment date on the lead. |
| EverSet | Whether the lead ever had an appointment set. |
| EverGrossIssue | Whether the lead ever issued. |
| EverDemo | Whether the lead ever demo’d. |
| Sold | Whether the lead ever sold. |
| Method | Indicates how the inbound lead was handled: X = deleted; A = added; M = merged. |
| ikr_id | Internal reason ID for why the inbound lead was deleted/killed (e.g., 10). |
| ikrdescr | Description for the ikr_id value (e.g., Duplicate). |
Should we expect responses and disposition reasons to be consistent across LeadPerfection accounts, or does each account define their own?
Dispositions can be customized per LeadPerfection account, so you should not assume dispositions are consistent across accounts.
Examples:
-
Datais standard in LeadPerfection and typically indicates a lead without an appointment (often meaning “fresh” or “untouched”). -
Setis standard in LeadPerfection and typically indicates the lead has an appointment set. - Customers can also create custom dispositions (for example:
ABC-WN), based on how they configure their LeadPerfection system.
Do I need to reach out to LeadPerfection to create my API username and password to use conversion feedback?
No. You can enable this directly within your LeadPerfection account.
Just make sure:
- The username and password you use are dedicated for your company (not for an existing user).
- The username has API access checked.
- The credentials have access to the
Get ActiveProspect Leadsendpoint.
Can I store in LeadPerfection the TrustedForm Cert URL submitted with my leads?
Yes. A TrustedForm Cert URL field is included by default in the newer endpoint and is stored in LeadPerfection’s database (it may be hidden in the UI); if you want it visible in the LeadPerfection UI, you can request that LeadPerfection enable it. Example request to LP support:
“Hi LeadPerfection Support, I am reaching out to request that the inbound consent lead sub table be made visible in my account, so I can access the TrustedForm Certificate URL when viewing a lead.”
Where can I find my LeadPerfection Source IDs?
You can find Source IDs (srs_id) in your LeadPerfection account under: Setup → Customer → Source Subs. Each source will display its srs_id as a numeric value.
How does the LeadPerfection feedback feature compare to the Salesforce feedback feature?
LeadPerfection feedback differs from Salesforce feedback in a few key ways:
-
Enablement: Salesforce feedback is available out of the box, while LeadPerfection feedback must be enabled/approved per LeadPerfection account. Contact LeadPerfection to confirm your account has access to the feedback feature.
-
Fields: LeadPerfection feedback returns a set of fixed fields, unlike Salesforce, which allows selectable feedback fields.
-
Timing: Salesforce can retrieve conversion feedback in real time. LeadPerfection conversion feedback is initially retrieved about once per hour, and the retrieval frequency may increase over time as adoption grows.
-
API access: ActiveProspect is the only party with access to the API used to retrieve feedback from LeadPerfection.
- leadperfection-action.png7 KB
- leadperfection-conversion.png60 KB
- leadperfection-feedback_event.png400 KB
- leadperfection-report_preview.png100 KB
- leadperfection-createlead.png20 KB
- leadperfection-report_configuration.png200 KB
- leadperfection-custom.png20 KB
- leadperfection-addlead.png10 KB
- leadperfection-pro.png20 KB
Comments
0 comments
Please sign in to leave a comment.