Lead Events in Marketplace Analytics

Learn how we define lead events for your AppExchange listing and how they differ from the leads that appear in your Salesforce org.

Marketplace Analytics records a lead event when a customer visits your listing and:

Watches a demo.
Takes a test drive.
Clicks Get It Now and installs your solution.

If you’ve 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 that you set up can cause the number of leads in your org to differ from the number of lead events shown in Marketplace Analytics. Typically, these rules are designed to prevent duplicate or unwanted leads from reaching your sales team. Here are some common examples.

Lead Routing Rule	Example
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 AppExchange asks for contact information. In this scenario, Marketplace Analytics records a lead event, but the lead routing rule filters the lead in your org.
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.

Lead Routing Rule

Example

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 AppExchange asks for contact information.

In this scenario, Marketplace Analytics records a lead event, but the lead routing rule filters the lead in your org.

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.

ISVforce Guide

Lead Events in Marketplace Analytics