🏷️ Tags, Custom Fields And Tokens

Tags and custom fields are part of each destination's field mapping, so they are set per destination inside the bridge builder. With tokens, one bridge can stamp every contact with exactly what they bought, where they came from or when they booked.

Where to find them:

1. Open the bridge with Edit, or start a new one.
2. Open a destination step and click Field mapping for this app.
3. Custom fields sit under the name rows. The tags box sits below them.

Custom fields:

Click Add custom field to add a row with a field and a value.

• For apps that share their own fields, such as ActiveCampaign, the field is a dropdown of that app's real fields. Choose Other to type a name yourself. The list is kept for a day, and Refresh fields re-reads it now.
• For other apps the field is a plain box you type into.
• The value can be fixed text, such as Stripe, a token, such as {amount}, or several together, such as {amount} {currency}.
• The red cross on a row removes it.

The classic use is recording where a contact came from: a field Lead Source with the value Calendly booking, so your email app can segment on it later.

Tags:

Type one or more tag names in the tags box, separated by commas, for example Customer, From WordPress. Before sending, tags are trimmed and repeats are removed, ignoring capital letters, so Customer and customer never become two tags.

Tokens:

A token is a field name in curly braces. Before sending, it is replaced with the contact's real value.

• {first_name}, {last_name} and {email} always work.
• Any field the source has actually sent works too, such as {amount} and {currency} from Stripe, {product_name} from ResultsAiX Payments, or {quiz_result} from a quiz webhook.
• Field names may contain dots and hyphens, which is how fields nested inside a webhook payload are reached, for example {customer.country}.
• Token names ignore capital letters, so {Currency} finds currency.
• A token that does not match any field is left exactly as typed, so a typo shows up the first time you test.

Finding the field names:

After a source has delivered at least once, WP Sync remembers the field names it sent. They appear as token chips under the tags box. Click a box first, then click a chip, and the token is typed in at the cursor. If you have not clicked a box, the chip goes into the tags box. Until a source has sent something, the chip area says its fields will appear there.

A real example:

yoursite.com's Stripe buyers to Customers bridge sends each buyer to ActiveCampaign with:

• the tag Customer, and the tag Paid in {currency}, so a buyer paying in US dollars gets Paid in USD,
• the custom field Lead Source set to Stripe,
• the custom field Order Total set to {amount} {currency}, such as 49.00 USD.

ActiveCampaign can then follow up differently by currency and order size, all from one bridge.

Which destinations use tags and custom fields:

Any app whose platform supports them. Where an app has no tags, the contact is still delivered and the tags are simply not applied. Google Sheets and outbound webhooks receive all source fields anyway.

Checking the result:

Click Test on the bridge row. The drawer shows the custom fields and tags each destination would receive. The sample contact has no payment, so you will see {amount} {currency} left as typed, which is how the dry run shows a token waiting for real data. Send a real test with custom fields named amount and currency to see them filled in.

Tokens from common sources:

• Stripe: {amount}, {currency}, {description}, {transaction}, {customer_id}, {phone}, {city} and {country}, where the payment has them.
• WarriorPlus and JVZoo: the fields of the marketplace's own notification, under the marketplace's own names.
• ResultsAiX Payments: {amount}, {currency}, {product_name}, {gateway}, {txn_id}.
• Webhook Connect: whatever field names your sender uses.

These are the fields the source sends. The token chips in the builder always show the exact names for your site.

Tips:

• Keep tag names short and consistent across bridges, so segments stay tidy.
• Use the Add tag action when a destination should only tag, not subscribe. See Destination Actions Beyond Adding To A List.