Sending Active Messages with BSUID

Coming soon!

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

Index

1. What DOES NOT change
2. What evolves
   1. Growth - Individual sending
   2. Growth - Bulk sending (CSV)
   3. Desk - Sending messages with BSUID
   4. Evolution of API payloads - Growth
   5. Checking results
   6. GET /accounts
3. Broadcast plugin
4. FAQ

What does NOT change

• Active sends via phone number continue to work normally
• Active message templates continue to work

• The option to send active messages via API (Growth and Blip) remains available

   

What evolves

Blip Portal - Individual Growth

The individual sending interface will offer the option to send by:

• Phone Number (current model)
• BSUID (new)

Blip Portal - Bulk Growth (CSV)

Live!

The first column of the CSV file now accepts both types of values, even mixed in the same dataset:

Example of a sending file

The column name does not need to be changed. Mixed audiences (PN and BSUID interleaved) are supported.

⚠️ Attention! If PN and BSUID of the same user are present simultaneously in the dataset, 2 sends will be made to the same user. Ensuring deduplication is the sender’s responsibility.

Desk - Sending messages by BSUID

Sending active messages via Desk will now allow searching by BSUID (filter "equals to"). The contact display during the sending flow will also start showing username and BSUID.

Evolution of API payloads

Growth (Active Campaign)

Now the Blip Active Campaign extension processes the BSUID (contact identifier without the domain) in the same way it processes phone numbers, accepting both forms.

Impacted endpoints: /campaign/full and /audiences/v2/{{id}}

Scenario 1 — Individual campaign

POST /campaign/full - The same payload is maintained. Just inform the identifier in the recipient field when making the API call:

POST https://{{contract_id}}.http.msging.net/commands HTTP/1.1
Content-Type: application/json
Authorization: Key {YOUR_TOKEN}

{
    "id": "%commandId",
    "to": "postmaster@activecampaign.msging.net",
    "method": "set",
    "uri": "/campaign/full",
    "type": "application/vnd.iris.activecampaign.full-campaign+json",
    "resource": {
        "campaign": {
            "name": "Individual campaign via BSUID",
            "campaignType": "Individual",
            "flowId": "{flowId}",
            "stateId": "{stateId}",
            "channelType": "WhatsApp"
        },
        "audience": {
            "recipient": "BR.1234567890123456",
            "messageParams": {
                "1": "Confirmation of your order"
            }
        },
        "message": {
            "messageTemplate": "order_confirmation",
            "messageParams": ["1"],
            "channelType": "WhatsApp"
        }
    }
}

Scenario 2 — Batch campaign (mixed audience)

POST /campaign/full - Same endpoint, but for batch campaigns. You can combine both identifiers in the same audience array:

"audiences": [
    {
        "recipient": "BR.1234567890123456",
        "messageParams": {
            "name": "Ana",
            "order_number": "1029"
        }
    },
    {
        "recipient": "+55319XXXXXXXX",
        "messageParams": {
            "name": "Carlos",
            "order_number": "1030"
        }
    }
]

Scenario 3 — Adding audience (mixed audience)

SET /audiences/v2/{{created campaign id} -  Maintains the same payload. You can combine both identifiers in the same audience array:

POST https://{{contract_id}}.http.msging.net/commands HTTP/1.1
Content-Type: application/json
Authorization: Key {YOUR_TOKEN}

{
    "id": "{{$guid}}",
    "to": "postmaster@activecampaign.msging.net",
    "method": "set",
    "uri": "/audiences/v2/{{resource.id}}",
    "type": "application/vnd.lime.collection+json",
    "resource": {
        "itemType": "application/vnd.iris.activecampaign.audience+json",
        "items": [
            {"recipient": "+5520900000001"},
            {"recipient": "BR.1234567890123456"}
        ]
    }
}

Checking results

When checking the summary or the campaign report, the field recipientIdentity will display the BSUID for contacts who do not have a linked phone number.

Practical tips:

• Storage: Save the contact’s BSUID as soon as you receive it in webhooks to ensure future communication.

• Validation: Conduct tests with small audiences before mass sends using BSUID.

• Integrity: Never manually edit a BSUID. The value must be used exactly as returned by the Meta API.

Field recipientIdentity —  endpoint /campaigns/summaries

Currently always returns {phone}@wa.gw.msging.net. With the evolution, it will return PN or GUID.

Field validatedAccount — endpoint /audiences

Currently always returns {phonenumber}@wa.gw.msging.net. With the evolution, it will return PN or GUID.

Under consideration for future evolutions: support for Blip ID (GUID) and Parent ID as recipient.

GET /accounts

The endpoint GET /accounts now accepts BSUID as a query parameter (in addition to PN). The to field in the sending payload does not change and will continue to be filled with the identity obtained via GET /accounts.

BEFORE - Sample payload

AFTER: PN as contact ID - Sample payload

AFTER: GUID as contact ID - Sample payload

Broadcast Plugin

⚠️ The Broadcast Plugin does NOT follow the evolution of the WhatsApp identity model and there is no scheduled adaptation to support usernames, BSUIDs, and the new contact creation logic implemented in Blip.

A gradual migration to the Blip Growth API is recommended. Keeping the plugin may result in duplicate contact creation, history fragmentation, and loss of continuity in scenarios with new IDs.

FAQ

Can I mix phone number and BSUID in the same campaign?

Yes, Blip automatically identifies the data type in the recipient field.

What happens if I use an invalid BSUID?

Sending to that recipient will fail but will not affect the rest of the campaign.

Do I need to enable anything in Blip?

No. BSUID support is native in the Active Campaign APIs and in the Builder.

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 😃