What’s the Difference Between Lead Events and Leads in AgentExchange Marketplace Analytics?
Learn how lead events are defined in AgentExchange Marketplace Analytics and how they differ from the lead records that appear in your Salesforce org.
Marketplace Analytics records a lead event when a customer visits your listing and performs one of these actions.
-
Watches a demo
-
Takes a test drive
-
Interacts with AgentExchange Chat
-
Clicks Get It Now
-
Clicks Learn More (applies only to consultant listings).
-
Installs your solution
AgentExchange Chat is required to view chat data in Marketplace Analytics. Learn about AgentExchange Chat in the Salesforce Partner Community.
If you configured Web-to-Lead and enabled lead collection for the listing, each of these activities also creates a lead in your org. However, custom lead routing rules, customer contact preferences, and Web-to-Lead reCAPTCHA can cause the number of leads in your org to differ from the number of lead events shown in Marketplace Analytics.
Typically, you set up custom lead routing rules to prevent duplicate or unwanted leads from reaching your sales team. Here are some common examples of routing rules where Marketplace Analytics lead events aren’t recorded as leads in your org.
| Lead Routing Rule | Example | Marketplace Analytics | Your Org |
|---|---|---|---|
| Domain Restriction: You filter leads from customers whose email address includes your company’s domain. | An employee at your company watches your listing’s demo video and uses a company email address when AgentExchange asks for contact information.In this scenario, Marketplace Analytics records a lead event, but the lead routing rule filters the lead in your org. | A lead event is recorded. | A lead isn’t recorded. The lead routing rule filters out the lead. |
| Duplicate Email Addresses: You filter leads associated with an email address that’s been captured in an existing lead. | A new customer goes to your listing and watches a video, takes a test drive, and installs your solution. For each activity, the customer provides the same email address.In this scenario, Marketplace Analytics records three lead events: one for each activity. In your org, the lead routing rule creates a lead for the first activity. The others are marked as duplicates because they’re associated with the same email address. | Three lead events are recorded, one for each activity. | A lead is created for the first activity only. The others are marked as duplicates because they’re associated with the same email address. |
In a customer’s Trailblazer settings, the customer can choose to share their contact info with, and allow contact from, AgentExchange providers. Their choices impact lead creation in your org. For customers who allow provider contact, AgentExchange lead events are recorded in Marketplace Analytics and propagate to your org as leads. Here are common examples of how contact preferences impact lead creation.
| Trailblazer.me Contact Preference | Example | Marketplace Analytics | Your Org |
|---|---|---|---|
| Allow | A prospect who allows provider contact watches your listing’s demo video. | A lead event is recorded. | If custom lead routing rules don’t filter out the lead, then a lead is created in your org. |
| Prohibit | A prospect who prohibits provider contact takes a test drive of your solution. | A lead event is recorded. | If custom lead routing rules don’t filter out the lead, then a lead is created in your org. The lead is flagged as contact prohibited. |
Customers can override their default Trailblazer contact preferences when interacting with AgentExchange listings. AgentExchange recognizes when a customer interacts with your listing in a way that you chose to collect leads for. These customers are prompted to fill out the AgentExchange lead sign-up form.
The form prepopulates with the customer’s contact info and preferences from their Trailblazer profile settings. On the form, the customer can choose to allow or prohibit provider contact, effectively overriding the contact preference that they set in their Trailblazer profile.
To receive AgentExchange leads, disable Require reCAPTCHA Verification in your org’s Web-to-Lead settings.
See Also