Set up Meta CTWA with Meta login

Konektor.id sets up CTWA by connecting your WhatsApp number to a Click-to-WhatsApp dataset in Meta. You log in with Meta in the Numbers & CTWA menu, and Konektor.id prepares the dataset for you. Once ready, a Meta CTWA row with the Sent status in the Delivery log proves that Meta received the event.

Use the Inbox to manage conversations and messages.

For the events that Meta receives once CTWA is ready, see Meta ads tracking in Konektor.id. How Konektor.id captures the CTWA click identifier on each WhatsApp path is in CTWA ads tracking software.

How do you set up CTWA with Meta login?

Meta login is the main method. You do not create a token.

1. Open Connection > Numbers & CTWA. After an official or partner connection succeeds, you can also click Set up CTWA for this number.
2. On your number, select Set up CTWA. Select Manage CTWA if the number was previously connected.
3. Enter the numeric WABA ID of that number in WhatsApp Business Account ID.
4. Click Log in with Meta.
5. Log in with the Facebook account that is admin of the business that owns the number. When Meta asks for permissions, tick the WhatsApp Business account of this number.

Konektor prepares the CTWA dataset automatically. The Ready - Meta login status means the local configuration is ready. This status does not prove that Meta accepted an event.

When do you use a Meta App token?

Meta login is available to every workspace. Use a Meta App token only in two cases:

• The Facebook account that logs in has no access to the WABA of that number. Read CTWA setup fails: the Facebook account has no access.
• Your business uses its own System User token.

The sections below describe the Meta App token.

Before you begin

Prepare the following:

• owner or admin access to your Konektor workspace;
• a Meta App owned by your business and connected to the correct Business Portfolio;
• the WhatsApp and Marketing API use cases on that Meta App;
• access to the WhatsApp Business Account (WABA) that contains the Session number;
• the numeric WABA ID for that number;
• a token with whatsapp_business_management and whatsapp_business_manage_events.

Your business must control the WABA and Meta App. The Meta user or System User that creates the token must also have access to that App and WABA.

You do not find or enter a Dataset ID. Konektor asks Meta to select the existing WABA dataset or create one during verification.

Choose a token for testing or production

Use a Graph API Explorer user token only for a limited test. The token can expire or stop working when the user's access changes.

Use a System User token for continued production use. Give the System User access only to the required Meta App and WABA, then create a token with both CTWA permissions.

Prepare the Meta App and WABA access

Meta can change its menu labels. Use the menu with the same function if your interface differs.

1. Open Meta for Developers, then create or use a business App owned by your business.
2. Connect the App to the Business Portfolio that owns or manages the WABA.
3. Add the WhatsApp and Marketing API use cases to the App.
4. Give the user or System User access to the matching App and WABA.
5. Create a token with whatsapp_business_management and whatsapp_business_manage_events.
6. Open WhatsApp Manager, then copy the WABA ID for the WhatsApp number.

Example WABA ID format: 100000000000001. This value is fictional and must not be used in your workspace.

Meta can require more settings for your App type and business assets. Konektor checks both permissions, WABA access, and the dataset before it saves the connection.

Save the Session before CTWA setup

1. Open Connection > Numbers & CTWA.
2. For a QR session, create a Session or complete the Session for the applicable WhatsApp number.
3. Select Save Changes before you open the CTWA setup.

Each Session must use the WABA ID that contains its number. Do not use a Pixel ID, Dataset ID, or WABA ID from another business.

Connect the token in Konektor

1. On the saved Session row, select Set up CTWA. Select Manage CTWA if the Session was previously connected.
2. Enter the numeric WABA ID in WhatsApp Business Account ID in the CTWA panel.
3. Select Meta App token.
4. Paste the token into the Meta App token field.
5. Select Verify and connect.

Konektor checks both permissions, WABA access, and the dataset before it saves the token. If a replacement token fails, Konektor keeps the previous connection.

You do not use Edit Session to save the WABA ID. The CTWA panel verifies and saves the WABA ID with the connection.

The local connection is ready when the Session shows Ready - Manual token. This status does not prove that Meta accepted or attributed an event.

Use a stored token for another Session

Use this method when one connected token can access another WABA in the same workspace.

1. Select Set up CTWA on the next Session.
2. Enter the WhatsApp Business Account ID for that Session number.
3. Select Use stored token.
4. Select Verify and connect.

Konektor verifies the token against the new WABA. It also verifies other WABAs that use the connector before it saves changes.

This method does not display or send the token to the browser. The previous connection remains available if the token cannot access the new WABA.

How do you prove that Meta received a CTWA event?

Do not combine these three results:

1. Local configuration is ready. The Session shows Ready - Manual token. Konektor validated and saved the connection.
2. Meta accepted a dedicated CTWA event. The Session shows Meta accepted a CTWA event, and the Delivery log shows a Meta CTWA row with Sent status.
3. Ads Manager reported or attributed the conversion. Check this result separately in Meta Ads Manager.

Konektor can prove the first and second results. Meta Graph acceptance does not guarantee that Ads Manager will report or attribute a conversion.

What do the channel badge and status mean in the Delivery log?

The Delivery log tab in Tracking & Ads > Conversions shows the channel and status separately. A badge identifies the path. The badge is not acceptance proof:

• Meta CTWA: Konektor tried the dedicated CTWA path to the WABA dataset.
• CTWA backup: Konektor tried the backup route through Meta CAPI for a CTWA event.
• Meta CAPI: Konektor tried a regular Meta event that was not a dedicated CTWA delivery.

Check the status on the same row: Sent, Failed, Skipped, or Queued. Only a Meta CTWA row with Sent status proves that Meta received the dedicated event.

The Resend as Meta CTWA action follows these rules:

• A CTWA backup row with Sent or Failed status can be eligible.
• A Meta CTWA row with a final Failed status can be eligible.
• A row with Queued status is not eligible.
• A Meta CTWA row with Sent status blocks a duplicate dedicated resend for the same event and dataset.
• A regular Meta CAPI row does not offer CTWA resend.

Check, replace, or disconnect the connection

Open Connection > Numbers & CTWA, then select Manage CTWA.

• Select Check connection to validate the permissions and assets again. This action does not send a test Purchase event.
• Select Replace token to verify a new token before replacing the active token.
• Select Disconnect CTWA to remove the connection from that Session.

Disconnecting CTWA in Konektor does not revoke the token in Meta. Revoke the token in Meta business settings when it must no longer work.

Migrate to Meta login

Available methods depend on your workspace features. If the panel does not show Meta login, use Meta App token or Use stored token.

If you already use a token and Meta login becomes available for your business, open Manage CTWA and select Replace token. Select Meta login, then continue with Log in with Meta.

Konektor keeps the manual token until the new OAuth connection passes validation. If migration fails, the previous manual connection remains active. After migration succeeds, the Session shows Ready - Meta login.

How do you report events that Meta detects?

Meta can spot a lead or a purchase in a WhatsApp chat that came from an ad. Konektor can report these events for you. Konektor reports an event only when your team did not already report it for the same lead.

This works only for a number connected with Login with Meta. Only the workspace owner can turn it on.

1. Open Tracking & Ads > Conversions > Conversion Settings.
2. Find Meta automatic events.
3. Turn on Report events Meta detects. If the switch is off and gray, read the reason under it.
4. Open WhatsApp Manager in Meta, then turn on automatic events. Follow the step-by-step guide with screenshots.

Do both steps. See the full guide. Without the Meta step, Meta sends nothing. Without the Konektor switch, Konektor ignores what Meta sends.

Check the result in the Delivery log. Meta does not offer this in the EU, the UK, and Japan. Menu names in Meta can change.

Troubleshooting

The token is invalid or expired

Create a new token from the correct business App. Confirm that the user or System User still has access to the WABA.

The token lacks both CTWA permissions

Create the token again with whatsapp_business_management and whatsapp_business_manage_events. Confirm that the App has the WhatsApp and Marketing API use cases.

The WABA is unavailable

Confirm that the WABA ID contains digits only. Confirm that the WABA contains the Session number and is accessible to the token owner.

The event shows CTWA backup

Select Manage CTWA, then run Check connection. Create one new conversion after the connection is ready before you retry an eligible older backup event.

Support needs to inspect a failure

Send the Session name, attempt time, and safe message shown by Konektor. Do not send the token, complete WABA ID, Dataset ID, private URL, or a screenshot that contains a secret.

Related guides

• Monitor delivery on the Conversion Dashboard
• Set up Meta Conversions API for regular events
• Connect HaloAI and set up CTWA
• Understand Click-to-WhatsApp conversion tracking