Learning objectives
- Understand what a Connection is within the ActiveProspect platform.
- Learn why Connections matter and how they support collaboration between buyers and sellers.
- See how Connections power related features across the platform.
- Know where to go for feature-specific guides and workflows.
- Understand the reasons for inviting partners to connect and how to use the related features to send invitations.
- Learn how to get started when you are invited to connect, whether you are a lead buyer or a lead seller.
Overview
Summary:
A Connection is a formal relationship between two companies—a buyer and a seller—on the ActiveProspect platform. Once connected, both parties have secure, structured access to shared data and workflows that improve transparency, lead quality, and operational setup.
Why it matters:
Connections serve as the foundation for partner collaboration across ActiveProspect products. They unlock features such as automatic access to Submission Docs, shared lead reporting, streamlined lead delivery, domain ownership visibility, and the ability to link vendors to reporting tools. These relationships help create a transparent ecosystem where buyers and sellers can work more efficiently and with greater trust.
Practical examples
Example 1: A Lead buyer working with a new seller
A buyer invites a seller to connect from the Accounts app. Once the seller accepts, the buyer can add them as an Account Source in LeadConduit. The seller automatically gains access to the buyer’s Submission Docs, and both parties receive shared reporting to align on performance.
Example 2: A buyer requesting domain ownership verification
A buyer notices that when they call the TrustedForm Insights API for a lead’s certificate, the confirmed_owner field returns ‘No Verified ActiveProspect Account Identified,’ indicating the domain isn’t verified. To address this, the buyer goes to the Connections page and sends a domain ownership invitation to the seller. If the seller accepts, the next time the buyer runs the Insights API, the confirmed_owner field will display the verified partner’s account name—improving transparency, compliance, and trust.
Example 3: A vendor relationship in TrustedForm Retain
A buyer uses the Vendor Reports page to link a vendor label to a connected partner. This sets the stage for shared vendor-level reporting and improved insight into lead quality.
Implications & applications
Key takeaways:
- Connections formalize how organizations work together across the platform.
- They unlock shared views, shared data, and simplified configuration.
- Many advanced workflows—Account Sources, Buyer Step, domain ownership permissions, vendor linking—depend on an established connection.
Practical applications
This section outlines the different reasons you may invite partners to connect within the ActiveProspect platform. Each reason links out to a separate article that provides deeper guidance, including step-by-step instructions on how to use the associated features.
-
Receive leads from my vendor to my LeadConduit:
Use a connection so your vendor (seller) can deliver leads directly into your LeadConduit flow. This formalizes the relationship and ensures you both have a shared configuration for submitting and receiving leads. Once connected, you’ll also receive email alerts when new Submission Docs are ready to review and anytime updates are made, helping you stay aligned with your partner’s setup. Learn More -
Send leads to my partner’s LeadConduit:
Establish a connection so you, as the seller, can add a Buyer Step and submit leads to a buyer’s LeadConduit account. Once the connection is accepted, the buyer can configure their destination, and you can enable the Buyer Step to begin sending leads. Learn More -
Request permission for domain ownership visibility:
Invite your vendor specifically to grant permission for their account name to appear in the TrustedForm confirmed_owner field. This allows you to see whether a lead originated from a domain owned by a verified partner rather than a generic “ActiveProspect Verified Account” or “No Verified ActiveProspect Account Identified" label. Learn More -
Confirm domain ownership to improve compliance and transparency:
Send a request to your vendor to confirm ownership of their domains. Upon accepting the connection, the vendor is guided through the domain verification process, improving risk mitigation, compliance alignment, and trust between both parties. Learn More -
Share lead quality reports with my vendor:
Create a connection so vendor labels in TrustedForm Retain can be linked to partner accounts. This prepares both parties for shared vendor-level lead quality reporting and improves transparency. Learn More
This section is for users who have been invited to connect by a partner. It links to separate getting-started guides for lead buyers and lead sellers that explain what happens after you accept an invitation and how to begin working together in the platform.
-
Getting started as a lead buyer invited by a partner:
Get started as a lead buyer by accepting a seller invitation, configuring your lead delivery destination, and testing lead submission end to end. Learn More -
Getting started as a lead seller invited by a partner:
Get started as a lead seller by accepting a buyer invitation, accessing submission docs, submitting a test lead, and transitioning to live lead delivery. Learn More
Frequently Asked Questions (FAQ)
Q: Do both parties need an ActiveProspect account to connect?
A: Yes. If the invited partner doesn’t have an account, they can create one for free during the acceptance process.
Q: Where can I see my current connections?
A: In the Accounts app under Connections, you can view active partnerships, pending invitations, and resend or manage invites.
Q: Does a connection change how I use integrations or standard sources?
A: No. Integrations, such as Facebook lead ads or CRM recipients, work the same. Connections simply add additional partner-specific workflows.
Glossary
| Term | Definition |
|---|---|
| Connection | The formal relationship between two ActiveProspect accounts, enabling shared data and partner workflows. |
| Invitation | An email request sent to a partner to establish a connection. |
| Account Source | A seller added as a source in a LeadConduit flow; requires a connection to unlock shared functionality. |
| Buyer Step | A LeadConduit step that allows a seller to send leads directly to a buyer; it requires a connection. |
| Confirmed Owner | A TrustedForm Insights field that identifies whether a lead’s domain is associated with a verified connected partner. |
| Vendor Label Linking | A TrustedForm Retain feature allowing buyers to associate vendor labels with connected partners. |
Comments
0 comments
Please sign in to leave a comment.