Merging & comparing cards

Across Survey Manager, the same thing often exists in more than one place. A pipeline can serve several surveys, a segment can be defined on many questionnaires, a campaign can run across workspaces. Rather than show you a near-identical card for every underlying copy, the app collapses records that share the same settings into a single card, so you manage them in one place.

This page explains why cards merge, why two that look alike sometimes don't, and how the Diff Checker shows you exactly what's different.

Why cards collapse into one

When several underlying records have identical settings, Survey Manager groups them into one card. Edit that card once and your change applies to every member inside it — no copy left behind, nothing to keep in sync by hand.

You can always see what a card contains:

• The "+N" id chips next to a card's name tell you how many underlying records it represents — a card showing "+3" stands in for four copies.
• The member list on the card spells out exactly which surveys, workspaces or questionnaires are inside.

So a single card is really a tidy summary of every place that setup is used.

Why two near-identical things don't merge

Sometimes you expect two cards to be one — they look almost the same — yet they stay separate. That always means at least one field differs. Merging is all-or-nothing on the fields that matter: if even one of them doesn't match, the records can't be treated as the same thing, so they remain two cards.

The tricky part is that the difference can be small or easy to miss — a slightly different cap, one untranslated language, a date window that's a day off. That's exactly what the Diff Checker is for.

The Diff Checker Admin only

The Diff Checker is a tool for organization administrators that answers one question: why didn't these two cards merge? It's reached from the toolbar of each merging page — Pipelines, Campaigns, Segments, Sequences and Data bridges.

The main comparison shows only the fields that actually drive merging — so every highlighted difference is a real reason the two cards stayed separate. There's nothing to second-guess: if a field is highlighted, that's a genuine mismatch keeping them apart.

A separate "Excluded from merge logic" panel lists the fields that never affect merging — things like internal ids and audit timestamps. They're shown for context so you can see the full picture, but a difference there is expected and harmless; it will never keep two cards apart.

What each entity merges on

The fields that count toward merging differ by area. Below, each section lists what's merged on (considered) and what's not merged on (ignored) for that entity.

Pipelines

A messaging pipeline delivers a survey by email, SMS or Viber. Two pipelines merge when everything about what is sent and when matches — including every translation.

Merged on

• The pipeline's title
• The channel (email, SMS or Viber)
• The tracking id
• The default language / locale
• The description
• The delay caps (minutes, hours and days)
• The frequency caps (minutes, hours and days)
• The default message subject and body, and — for Viber — the SMS fallback
• The active date window (start and end)
• The daily dispatch window
• The maximum retry attempts
• Every per-language translation

Not merged on

• The pipeline's internal id
• Which questionnaires it targets — the surveys it delivers to. Spanning many questionnaires from one card is the whole point of a merged pipeline, so this is intentionally not a merge factor.
• The pipeline's conditions — the rules that filter which recipients or queue items it applies to. See the callout below.
• Any template-pipeline link
• Audit timestamps (who created or updated it, and when)

Campaigns

An on-site campaign fires on the thank-you screen. Campaigns merge when their content, behaviour and type-specific settings all line up.

Merged on

• The campaign type
• The title and description
• The priority
• The tracking ID (the campaign's analytics tag)
• Whether a banner image and a mobile image are set
• The background color
• The target URL
• The frequency caps
• The language
• The active flag
• The active date window
• The thank-you content
• The anonymize setting
• The questionnaire
• The type-specific settings (for example, callback time slots, refer-a-friend rewards, or an on-screen incentive)

Not merged on

• The campaign's internal id
• The workspace it belongs to
• The exact image files — only whether a banner or mobile image is set is considered, never which image file you uploaded, so two cards can merge while showing different artwork.
• The attached segments / audience — these are aggregated per workspace and are managed separately, so two campaigns can merge while targeting different audiences in each workspace.
• Audit timestamps

Segments

A segment is a slice of your audience defined by conditions. Segments merge when their conditions describe the same audience.

Merged on

• The title and description
• The active status
• The full set of conditions. Each condition is matched by its target — a question (matched across questionnaires by the shared template question when one exists) or a metadata field — its comparison (such as equals or contains), and its value. The order of the conditions doesn't matter.

Not merged on

• Which questionnaires the segment is defined on. The same segment can back many questionnaires — each backing copy has its own internal id — but as long as the conditions describe the same audience it stays a single card. The questionnaire a copy lives on is managed separately and is never a reason two segments don't merge.
• Display labels
• The workspace

Sequences

A follow-up sequence chains one survey to another. Sequences merge when they lead to the same destination through the same pipeline.

Merged on

• The workspace
• The destination ("to") questionnaire
• The pipeline used
• The sequence type

Not merged on

• The source ("from") questionnaires and their individual flows — these are managed separately and aren't part of the grouping key, so two sequences leading to the same destination can merge even when they start from different surveys.
• Descriptive labels such as the pipeline's title, channel and delay summary — they're shown for context but don't affect grouping.

Data bridges

A data bridge imports recipients from a file on your server. Bridges merge when they connect to the same place and read the same file the same way.

Merged on

• The active flag
• The protocol (FTP or SFTP)
• The passive-mode flag
• The host and port
• The username and password
• The scheduled start time
• The frequency (how often it runs)
• The private-key path
• The file path it reads
• The column mapping
• The column separator

Not merged on

• The pipeline a bridge feeds — managed separately, so two bridges that read the same file the same way still merge even when they hand off to different pipelines.
• The bridge's run history, including the last-processed timestamp — when it last ran never affects whether it merges.
• Audit timestamps

Related articles