Deep links | Developer Documentation

Test website and app links in ChatArchitect templates

A deep link takes a recipient to a particular page or app screen. Before a WhatsApp campaign, test the destination from the actual approved message. If your template form and connected sending tool offer a URL button, use an HTTPS destination you control. Check the exact button types available in your account in the template parts guide.

Choose a destination that works on the web

Start with a useful page on your own website, such as https://example.com/offers/october. The page should explain the same offer as the message and remain usable when the recipient does not have your app installed. A website-only campaign can use this destination without an app.

If you have an app, ask its developers to configure the association between the app and your website. Android App Links and Apple universal links can route a website URL to app content and let the website handle it when the app is not installed. Opening the intended app screen depends on your app and domain configuration, the device and the way the link is opened. Confirm the result from WhatsApp on real devices.

Test the approved message before sending a campaign

1. Configure the destination using the URL-button controls available in your template form. Submit the template through wtargeted.com and confirm that it is approved before using it.
2. Send a test message from the CRM, help desk or other connected tool you intend to use for the campaign to a recipient who has agreed to receive it. Tap the button in that message; pasting the address into a browser is a separate test.
3. Check the combinations below. Record the final page or app screen, any error and whether the recipient can complete the intended action.
4. If you use campaign parameters or redirects, check that they reach the intended destination. Follow the campaign link tracking guide and verify visits in your own website analytics where applicable.
5. Resolve a blank page, wrong screen, broken fallback or lost campaign identifier before a larger send. A delivered message does not prove that its destination works.

If you need a special deep-link setting

Ask ChatArchitect support to confirm whether your template form and sending integration support a separate app destination, a custom URL scheme or a platform-specific fallback. These settings have not been confirmed for the ChatArchitect customer workflow. Send the intended HTTPS destination, the affected device and the result of the approved-message test. Your app or website developers can then check the app association and destination routing.

Use the campaign metrics guide to keep available delivery results, website visits and business actions separate. Adding an app link does not by itself confirm that a Meta conversion report is available in ChatArchitect.