Facebook Ads

Prerequisites

• An active Facebook Ads account (Ads Manager).
• The Facebook Page used in the ad must be connected to your Messenger channel inside NicoChat.
• The ad account and the Facebook Page must belong to the same Business Manager used when connecting the channel.
• The Page must be verified and free of active restrictions in Business Manager — accounts with pending verification may have their Messenger ads rejected or paused by Meta.

Setting up the ad's welcome message

• In your Messenger channel, go to the flows section and create (or choose) the SubFlow you want to trigger when the user clicks the ad.
• In Meta's Ads Manager, create a "Messages" campaign with "Messenger" as the destination.
• In the ad creation step, in the welcome message section ("Message template"), select the option to use a custom/JSON template generated by an external tool (chatbot).
• Paste the Flow ID (Ref/Flow Ns) or the reference JSON generated by NicoChat for that SubFlow — this ensures that clicking the ad takes the user exactly to the configured SubFlow instead of the channel's default flow.
• Publish the ad as usual. You can test the click using Ads Manager's own preview before publishing to production.

Tracking the results

Conversations started by an ad click arrive in Live Chat and in automations just like those of any other contact on the Messenger channel. They can be marked with a specific tag at the beginning of the flow (for example, origem_ads), which makes later segmentation and analysis easier in the Contacts and Conversations reports.

Common problems

• Ad approved, but the flow does not trigger: check that the Facebook Page is correctly linked to the channel in NicoChat and that the flow reference ID was pasted correctly in the ad settings.
• Ad rejected or paused by Meta: the reason is usually related to Page/Business Manager verification or to Meta's advertising policies for Messenger — check the Page status in Business Manager.
• Contact arrives without a tag/source: check that the action that applies the source tag is actually in the first step of the SubFlow the ad points to.