Partner-Hosted Embedded Signup

This page describes how partners can host Embedded Signup

For advanced personalization, approved Meta Tech Providers can host a custom Embedded Signup flow.

Requirements

Tech Provider registration and approved Solution

Enabling this option requires status as a Meta-approved Tech Provider with a live solution integrated with 360dialog. The solution must be in Meta's ACTIVE status. More details.

Technical Capacity

Hosting and managing an independent Embedded Signup script requires technical implementation knowledge. Technical support from 360dialog is not available for troubleshooting custom Embedded Signup scripts.

Request Advanced Access for public_profile permission

An additional permission is required for the onboarding process to function correctly. In the Meta for Developers App dashboard > navigate to your App Review > Permissions > Find the ‘public_profile’ permission and request advanced access.

Ensure advanced access is granted before configuring the ES.

Set Partner Hub Webhook URL and listen to Webhook Events

See instructions here.

Build Self-Hosted Embedded Signup

Important: The Meta documentation linked below includes steps for registering a phone number.

Do not follow those steps. Phone number registration is handled entirely by 360Dialog.

1. Implement Embedded Signup.

2. Check the signup flow for Cloud API. Note that if you have information about your customer's business, you can inject this data, which can significantly reduce the number of screens that your customers have to interact with. We recommend using Embedded Signup version 4. In this case you can enable the Marketing Messages API (MM API) for the client during the onboarding process. This allows your clients to skip an additional step of enabling the MM API after they are onboarded. Here is how to enable Embedded Signup version 4.

Connect Self-Hosted Embedded Signup to 360dialog

Step 1: Create or retrieve a Client Account

In order to later submit the number, you need to either retrieve an existing client_id or create a new client instance through our Partner API using the endpoint below. Make sure to store the Client ID of each client within your database, since it will be required afterwards. Alternatively, you can also retrieve it with this endpoint.

Create client account

This endpoint must be used to create the client account.

Step 2: Surface Embedded Signup to client and fetch information

Important: The Meta documentation linked below includes steps for registering a phone number.

Do not follow those steps. Phone number registration is handled entirely by 360Dialog.

When the Embedded Signup is completed by the client, you can use the code received in the payload to fetch detailed WABA information. See more here and here.

Step 3: Connect Client account to the registered Phone Number

Use the endpoint below to submit the phone number/channel to 360Dialog records. If the number was successfully onboarded via self-hosted Embedded Signup and the attached client_id matches the user data in 360dialog records, the onboarding flow ends by redirecting the Client to the Partner Redirect URL set.

Submit channel/number created via self-hosted Embedded Signup

Please use this endpoint.

channel_external_id should be filled in with the phone number ID. Once it is filled in, we connect the particular number. If the value is sent as null we will connect all numbers associated with the particular waba waba_external_id

Step 4: Create API key to start messaging

When the number is fully live, you will receive the Channel Live Webhook Event.

You should be able to generate an API Key and connect it to your integration to start messaging with this phone number by default.

See Partner Permissions for details.