Skip to main content

New Builder/Studio Variables

  • Updated

Coming soon!

⚠️ The behaviors below represent the current design of the feature and may evolve until the final release. 
 

Index

  1. Overview

  2. New variables planned in Blip

  3. Variables with changed behavior

  4. When to use each variable

  5. Best practices

 

Overview

Studio contact variables will continue to exist and maintain their purpose. However, with the evolution of the identity model, new variables will be added to represent the new IDs in the WhatsApp ecosystem, and some existing variables will have their format updated.

 

New variables planned in Blip

Variable What it returns When to use
contact.whatsAppBsuid User's BSUID Contextual identification of the user with the specific company
contact.whatsAppParentId Parent BSUID (if applicable) Consolidation and/or reference of the same user across BMs
contact.whatsAppUserName User's username (if applicable) Display and/or visual reference
contact.waId Numeric WhatsApp ID, corresponds to the phone number when available (not editable) To reference the user's phone number (if available)

 

 

Variables with changed behavior

The variables contact.identity, tunnel.originator, and tunnel.identity will continue to exist, but they may return a GUID instead of a phone number when the phone number is not available:

Scenario Value returned in contact ID variables
Existing contact with phone number as main ID 5531999999999@wa.gw.msging.net
New contact with shared phone number 5531999999999@wa.gw.msging.net
New contact without shared phone number (username adopted) e4b11bdd-a9bf-46ad-a9b0-34116dece5fe@wa.gw.msging.net

⚠️ Integrations, regex, or rules that assume these fields always contain a phone number may need adjustment. It is recommended to begin removing any dependency on parsing or splitting phone numbers from these variables as soon as possible.

 

When to use each variable

Need Recommended variable Note
Identify the contact in Blip contact.identity (as a generic string) May contain phone number or GUID
Obtain the phone number when available contact.waId May be empty if the user has adopted a username
User ↔ company relationship contact.whatsAppBsuid Only ID available in 100% of interactions
Consolidate identity across BMs (when approved by Meta) contact.whatsAppParentId Available in specific cases (eligibility and Meta check)
Display the user's public name contact.whatsAppUserName Will only be filled for users who adopt a username

 

Best practices

We suggest, after reading this article, to proactively and correctively (when applicable) evaluate your flows in Blip and those integrated with Blip to consume the available variables in the most accurate way possible for your operation.

 

Need more help? Explore our content at the Blip Academy or Blip Community, watch tutorials on our YouTube channel, or get your questions answered in our support channel 😃
 

Related articles