Konektor

Connect Meta CTWA with a Meta App token

Use this temporary path if your workspace shows the Meta App token method. This path connects a WhatsApp Session to a Click-to-WhatsApp (CTWA) dataset through an App owned by your business.

If the workspace uses Direct Chat, this setup sends CTWA conversion data only. Direct Chat continues to manage conversations, contacts, messages, templates, and your inbox.

Submit the token only through the secure modal

Never send the token through chat, email, support tickets, documentation, or screenshots. Konektor accepts the token only in the Set up CTWA or Manage CTWA modal.

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.

Store the token in your business password manager or secret store. Do not put it in documents, shared notes, or screenshots.

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 WhatsApp > Sessions.
  2. 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 modal.
  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 modal verifies and saves the WABA ID with the connection.

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

Use a saved 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 saved 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.

Check three separate proofs

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 Sync Logs shows a Meta CTWA row with accepted 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.

Read the delivery channel and status

The Sync Logs tab in Conversion 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 fallback: Konektor tried the regular Meta CAPI fallback 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. Only a Meta CTWA row with accepted status proves that Meta accepted the dedicated event.

The Resend as Meta CTWA action follows these rules:

  • A CTWA fallback row with accepted or failed status can be eligible.
  • A Meta CTWA row with terminal failed status can be eligible.
  • A row with queued, sending, or retry status is not eligible.
  • An accepted Meta CTWA row 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 WhatsApp > Sessions, 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 later

A Direct Chat pilot workspace does not show Meta login. Use Meta App token or Use saved token during the pilot.

After 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.

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 fallback

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

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

Need More Help?

Our team is ready to help you maximize ad tracking and business attribution.

support@konektor.idYouTube

Try or continue

Book a DemoOnboardingTechnical Support

© 2026 Konektor. All rights reserved.

Privacy PolicyTerms of Service