Plugin funnel sources

Open the funnel and the Edit tab. The plugin must be installed in the project. Configuring a source requires analytics management permission. Plugin metrics are not added to lead counts and do not move leads between stages.

Adding a source

1. In Add source, choose Plugin.
2. In source settings, choose an installed plugin.
3. Choose an element.
4. Choose a metric.
5. Set the source name.
6. Set its placement relative to stages.

If the plugin requires configuration, its embedded form opens here. Complete it.

Click Save to add the source to the funnel.

Configuring a source

To edit an existing source:

1. Click the pencil on its card.
2. Change its title or placement.
3. Save the general settings.

“Application settings” opens a separate form for application settings and lead matching; saving returns to the general settings. This form requires permission to use applications. If the application or element is unavailable, the title, placement, and source deletion remain available.

Changing the counter, account, or external ID scope opens the “Replace the data source?” confirmation. Click “Replace” to create a new connection with the same title and position among neighboring sources. Saved matches from the previous connection are not transferred. “Cancel” returns to the form without replacement.

Source metrics

The source card appears between stages in the editor. Click the pencil on the card to open its settings.

The source appears in the same sequence in View mode. Source values are not added to stage lead counts. The common funnel scale applies to metrics measured in leads with matching aggregation: unique leads in Current mode and summed passages in Period mode. Other metrics appear as separate cards on the same diagram. This view does not calculate person-level end-to-end conversion.

If the stage that the source precedes is deleted, the connection remains after the other stages and can be repositioned in settings.

Current / Period applies to sources. Unsupported modes show a dash with an explanation. A measured zero is shown as 0. UTM filtering applies to lead stages: selecting a filter hides external values to avoid mixing filtered and overall data.

If a refresh fails, the last received value remains on the card and in the funnel width calculation. “Could not refresh” appears beside it: hover to see when the data was current, or click the retry icon. If no successful response has been received, a dash and an error are shown.

Matching leads

If the source supplies external identifiers:

1. Enable lead matching.
2. Select a lead variable.
3. Enter the counter or account ID.

The variable must contain a scope:ID string or an array of these strings. The counter or account ID belongs in the variable value; its name does not need to change. For example, metrika_client_ids can contain ["counter-111:abc123", "counter-222:xyz456"]. Identifiers from another project or account do not match; multiple matching leads remain unattributed.

Details

Click the source value to open details. This requires lead view permission and access to all project channels: the report may contain external records not yet linked to a lead and its channel.

Save matches on this page additionally requires analytics management permission. It saves the matched identities and original dates. A weekly total stays weekly: no daily events are created from it. Saving again does not add duplicates. Reading a report alone does not save new matches, invoke an agent, or change lead stages.

In Current mode, a source may return people without event dates. Matched leads remain accessible in the details; the date column is hidden when the entire page has no dates. Save matches on this page is not shown for pages containing undated records. The report freshness timestamp is not an event date.