Tags and custom fields are part of a destination's field mapping, so they are set per destination inside the bridge builder.
Custom fields:
Add key and value pairs that are forwarded to destinations able to accept custom fields. The classic use is stamping where a contact came from, for example a key of Lead Source with a value of Calendly Booking, so your autoresponder can segment on it later.
Tags:
Add one or more tag names to apply on the destination. Tags are de-duplicated and trimmed before sending, so accidental repeats and stray spaces do not create near duplicate tags in your autoresponder.
Tokens:
Both custom field values and tag names accept tokens written in curly braces. A token is replaced with the real value from the contact before sending. The always available tokens are the first name, last name and email. On top of those, any field the source actually delivered can be used as a token, for example a product title, an order total, an affiliate or a country.
Token behaviour worth knowing:
- Token lookup is case insensitive, so a token written with capitals still resolves a lower case key.
- Token names may contain dots and hyphens, which is how nested or flattened keys from webhook payloads are addressed.
- An unknown token is left in place rather than replaced with an empty string, which makes a typo obvious the first time you look at a dry run.
How to find the field names available:
Run the bridge once, or use the dry run, then look at the sample contact. WP Sync remembers the field keys each source sends and offers them in the builder afterwards.
Which destinations honour tags and custom fields:
Any connection whose platform supports them. Where a destination has no concept of a tag, the tag is simply not applied and the contact is still delivered.