Every row in the Bridges list has a Test button. It runs a dry run, which is a full simulation of the bridge that writes nothing to any destination.
Where the sample contact comes from:
WP Sync tries to pull a recent real contact from the source so the preview reflects your actual data. If the source cannot provide one, for example because it is a push source that has not fired yet, a synthetic sample is used instead.
What the dry run shows you:
- Whether the contact passes the bridge's filters, and if not, which condition stopped it.
- The mapped email, first name and last name exactly as the destination would receive them.
- The custom fields and tags after tokens have been substituted, so a mistyped token is visible immediately.
- The target list, channel or board for each destination.
Why to use it before going live:
A dry run catches the three mistakes that cause most support tickets: a filter that is stricter than you thought, a name mapping that produces an empty value on a destination that rejects blanks, and a token that never resolves because the source does not send that field.
What a dry run will not tell you:
It cannot prove the destination's API will accept the write, because it deliberately does not write. For that, add a real contact to the source and check the Activity Log.
The full confidence check:
- Run Test and confirm the preview looks right.
- Add a genuine test contact in the source app.
- For polled sources click Run Sync Now rather than waiting five minutes.
- Open the Activity Log and read the per destination result.
- Confirm the contact actually landed in the destination app.