Add a chatbot to the landing pages your ads send traffic to
Written by the Allinaa team · Updated
Someone who clicks an ad lands on your page with one specific question about one specific offer. If the page doesn't answer it in seconds, they hit the back button, and you have paid for the click anyway. A chat on the landing page can answer that question in place and capture the inquiry without sending the visitor anywhere else. Here is how to set it up properly with Allinaa.
Ad visitors arrive with one specific question
Landing-page visitors behave differently from people browsing your homepage. They have seen a promise, such as "spring AC tune-up" or "free consultation for new clients", and they want the catch: "Does it cover two units?", "Is it really free?", "Do you serve my town?". These questions are narrow and predictable, which makes them easy to prepare for.
Before launching a campaign, list the five questions the ad is most likely to raise, and make sure both the page and the knowledge answer them.
Page-aware answers about the offer on that page
The Allinaa assistant reads the public page the visitor is on: its title, description, a short excerpt of its text and its links. "Does this include the filter?" is then understood as a question about this offer, not your whole price list. Your approved knowledge still governs prices and terms, so put the offer's details and end date there too. The mechanics are explained in Page-aware answers.
Keep landing pages on your own website address. Page context is accepted only from the website registered for your assistant (with or without "www"). A landing page on a separate domain, or on a subdomain such as offers.yoursite.com, is not read as page context. Use a path such as yoursite.com/spring-offer/ instead, or ask us first at info@allinaa.com.
Capturing inquiries without sending visitors away
The request form opens inside the chat. The visitor gives an email address or phone number, ticks the consent box, reviews the details and sends. They never leave the landing page. Before offering the form, the assistant may ask up to three short questions about the service, the timing and any requirements, so the lead arrives complete. The full flow is in Lead capture and qualification.
One rule matters for paid traffic: the assistant doesn't ask for contact details in the chat itself. That keeps consent clean and the conversation short.
Installing on a landing page: Webflow, Google Tag Manager, plain HTML
The same embed code works on any page where you can add a script. The install guides in the setup wizard cover the common routes:
- Webflow: add the code in the site or page custom-code settings, as the guide shows.
- Google Tag Manager: create a Custom HTML tag with the code and fire it with the DOM Ready trigger. See Install with Google Tag Manager.
- Plain HTML: paste the snippet just before the closing body tag.
- WordPress, Shopify, Wix, Squarespace and Tilda: each has its own guide, and WordPress also has a small plugin you can download.
The installation check in the cabinet looks at your homepage and up to two pages it links to. A landing page that isn't linked from your homepage may show "not found" even when the code is there. Open the page yourself and check that the chat button appears.
Reading results: inquiries per campaign page
Every inquiry records the page it was sent from, and that page appears in your notification email. One detail matters for ad tracking: query strings are removed from page addresses for privacy, so campaign tags such as utm_source are not kept. To tell campaigns apart, give each campaign its own landing page path, for example /spring-tuneup-search/ and /spring-tuneup-social/.
At the end of a campaign:
- export the inquiry inbox to CSV;
- count inquiries per landing page;
- check the monthly report for questions the assistant couldn't answer about the offer;
- fix the page before the next campaign.
More measurement ideas are in How to measure chatbot results.
Illustrative example, not a real customer conversation.
Page: "Spring AC tune-up: one visit, filter included, offer ends May 31"
Visitor: does this cover 2 units?
Assistant: The spring tune-up covers one system per visit. A second unit can be added at the same visit at the standard rate. Would you like to request a visit before the offer ends on May 31?
Visitor: yes, any weekday morning
Assistant: Great. You can send the request with the form, and the team will confirm a time.
Questions and answers
Will the chat slow down my landing page?
The widget is one small script added to the page. As with any added script, check the page with your usual speed-testing tool after installing it.
Can I see which ad an inquiry came from?
Not directly. Campaign tags in the address are removed for privacy. Use a separate landing page path per campaign, because each inquiry records its page.
Does it work on a landing page builder's own domain?
Page-aware answers work only on pages of the website registered for your assistant. Keep landing pages on your own domain, or contact us before using a separate one.
Can the assistant show a different greeting per campaign?
The greeting is set for the whole assistant. Put the offer details in the knowledge and on the page, and the assistant will answer about the page the visitor is on.