The Connections Report

Feature Snapshot

Summary: The Connections Report (previously known as the Partner Buyer Report) gives you and your partner one shared view of how your connection is performing: what happened to every lead the seller sent, from acceptance all the way to the buyer’s conversion stages. It’s the easiest way to talk about performance with a partner, because both sides look at exactly the same numbers.

LeadConduit creates one automatically for every buyer and seller connection, with no setup on either side. Connection reports live in their own group in the Reports sidebar, separate from the reports you create yourself, so they’re always easy to find.

Key Benefits:

• Both partners see the same report and the same numbers, so there is nothing to send and nothing to reconcile.
• Sellers can see not only whether a lead was accepted, but also whether it generated any opportunities along the way (assuming the buyer is sending conversion feedback events back to LeadConduit).
• Buyers can share performance feedback with partners without building spreadsheets.
• The report covers up to 270 days, so leads with a long buying cycle stay visible.
• Personal contact details are always removed, from both the screen and the export.

Typical Use Cases:

• A seller reviews rejection reasons to improve traffic quality.
• A seller checks how many of their leads reached each stage of the buyer’s process.
• A buyer shares CRM outcome data with partners automatically.
• Either partner exports the lead-level drilldown, outcomes, stage dates, and lead fields included, for spreadsheet analysis.

How the Connections Report Works

Connections Reports are a special kind of report: LeadConduit creates and manages them, they exist in both partners’ accounts at once, and they behave differently from the reports you create yourself.

When a buyer and a seller connect, LeadConduit generates the report for that pair and names it after the two partners. A connection is created in one of two ways:

• through an Invite to Connect;
• by linking a custom source to the partner’s account.

Each connection has exactly one report, and both partners see it from their own account. This way, there is nothing to manually share: the report already sits in each partner’s Reports sidebar.

Depending on which side of the partnership you sit on, different permissions are available:

What the Report Shows

When LeadConduit creates a Connections Report, it adds the following columns by default:

• Source Submitted: how many leads the seller submitted through the connection.
• Source Success: how many of those leads were accepted.
• Source Failure: how many were rejected because they didn’t meet the acceptance criteria.
• Source Error: how many ran into a processing error instead of a clean accept or reject.
• Conversion counters: how many conversion feedback events the buyer sent back for those leads, and how many of them succeeded or failed.

It also applies groupings. Two of them lead the table, and they’re the default pair:

• Outcome: whether the submission succeeded or failed.
• Reason: the reason attached to that outcome, for example the rejection reason.

The report carries more groupings than the two on display: Lead ID (the identifier LeadConduit assigned to the lead), Submission Timestamp (when the lead was submitted), and Flow Name (the buyer’s flow that processed it). Whichever groupings aren’t selected as first or second automatically become additional columns of the report, displayed at the end of the table.

You choose the order with the two Group by selects above the table: rows group by the first grouping and expand into the second, so the same report can be read outcome-first, reason-first, or by any other pair that fits the question you’re asking. Columns can always be rearranged too: see Reordering Report Columns.

When conversion feedback has been received for the connection, the report also includes one column per lifecycle stage, named exactly as the buyer’s CRM integration shares them: Appointment Set, Quoted, Sale Closed, or whatever the buyer’s stages are called. Each column carries the aggregate conversions for that stage. Two buyers on different systems will name similar stages differently, so the columns describe performance with that buyer, not a scorecard across buyers. Feedback is set up on the buyer’s side: see Enabling a Recipient to Send Conversion Feedback to LeadConduit, or Sending Feedback to LeadConduit for systems without a built-in integration.

The report covers up to the last 270 days, about nine months, while other reports keep the standard date range for your account. The longer window makes conversions visible for leads with a long buying cycle: a lead submitted in January may only become a sale months later.

Exporting to CSV

Anyone who can see the report can export it, partner accounts included. The export is not a copy of the on-screen table: it drills the data down to lead level, so every number on the report can be traced back through individual leads. It contains:

• everything the report counts: outcomes, reasons, and the conversion columns;
• the Lead ID: the identifier LeadConduit assigned to the lead at submission. It’s LeadConduit’s own reference, not one of the lead’s submitted fields, and it carries no personal information;
• the submission timestamp of each lead;
• one date column per lifecycle stage: the stages a lead moves through in the buyer’s CRM (its statuses there, reported through conversion feedback) become “Stage Date” columns, such as Appointment Set Date or Sale Closed Date. The cell holds the date the lead reached that stage, and stays blank if it never did; when a lead reached the same stage more than once, the most recent date is kept.
• the lead’s own submitted fields, when they’re configured for the connection: non-personal details such as the product the lead asked about or their region. The set of fields is fixed by configuration, and every field passes a personal-data filter before it can appear.

The stage date and lead field columns exist only in the export, which keeps the on-screen table a readable summary.

The export always contains the full drilldown: the grouping order and column order you picked on screen don’t change what lands in the file, and a lead can span more than one row when its events split across the groupings.

Data Privacy

Personal contact details are removed before anything is shown on screen or downloaded:

• email addresses, in any form
• phone numbers, in any form
• first and last names
• TrustedForm data

The filtering happens when the data is served, not when the report is set up. There is no setting that turns it off, and a configuration mistake can’t put contact details into a download: even the export’s configured lead fields pass through the same personal-data filter, so a field like an email address is dropped no matter what was configured.

Editing and Duplicating

Nobody can edit a Connections Report, buyer included. The reason is that both partners look at the same report: a change by one side would quietly change what the other side sees.

• Buyers who click Edit get a short dialog explaining this, with Duplicate as the next step.
• Sellers see Edit greyed out.

A duplicate is an ordinary report on the buyer’s own account: editable like any other, private by default, and shareable manually if needed (see Sharing a Report). It does not keep the Connections Report extras: the 270-day range, the export’s stage date columns, and the lead field columns are gone from the copy, so to customize the export, export from the Connections Report itself. The copy’s columns and groupings are fully yours to change though, including per-stage conversion columns through the Conversion outcomes section: see Adding Columns to a Report.

Best Practices

• Search the sidebar by partner name to find a report quickly: Connections Reports are named for the two partners.
• Keep the columns you check most often on the left by reordering them. Reordering only changes your screen, never the CSV export.
• Buyers: set up conversion feedback early, because partners can’t tell the difference between “no data” and “bad leads”. Systems without a built-in integration can send feedback over HTTP.
• Export from the Connections Report itself when you need the lead-level drilldown; a duplicated copy doesn’t keep it.
• Use the feedback button on the Reports screen to tell the product team what would make these reports better: see Sharing Feedback About Reports.

Troubleshooting

Frequently Asked Questions (FAQ)

Why doesn’t my report say “Partner Buyer Report” anymore?

Partner Buyer Report was the older name for the same report. It’s called the Connections Report now, everywhere in the product.

My buyer doesn’t use Salesforce. Can they still send conversion data?

Yes. Where there’s no built-in integration, any system that can send a web request can report conversions. If your account is managed by Customer Success, your CSM can help you choose the right route; otherwise contact ActiveProspect Support.

Can I change which of the lead’s fields are in the export?

No. The set of fields is configured for the connection and isn’t something either partner can change from the report. Personal fields are filtered out regardless of what’s configured.

Can my partner see my customers’ contact details?

No. Email addresses, phone numbers, names, and TrustedForm data are removed before anything is displayed or downloaded, and there is no setting that turns that off.

For anything else, contact ActiveProspect Support, or your Customer Success manager if your account has one. And for ideas about the reports themselves, the feedback button is the fastest way to reach the team that builds them.

• connections-report-full.png100 KB
• connections-expanded-row.png100 KB
• connections-conversion-columns.png50 KB
• connections-edit-dialog.png100 KB