Resolving Meta Permissions for Click-to-Messenger Attribution in n8n
Extracting ad attribution from Click-to-Messenger conversations requires correct Meta app permissions, webhook subscriptions, and Business Manager configuration. The core issues are permission scope, app review, and mapping webhook referral fields to Marketing API identifiers.
Executive takeaway: To reliably capture campaign, adset, and ad IDs for Click-to-Messenger leads you must configure your Meta app, page access, and webhooks correctly-then pass the referral payload through to your downstream systems (e.g., Google Sheets). App review and Business Manager access are frequent blockers.
Practically, ensure your Meta App is in Live mode with the required permissions (pages_messaging, ads_management, business_management where applicable) and that the Page Access Token you use has the right scopes and is generated under the business that owns the ad account. Subscribe to webhook fields messaging, messaging_referrals, and message_deliveries on the Page. The messaging_referrals payload typically includes ad_id, adset_id, and campaign_id for Click-to-Messenger, but you must validate this in your Graph API version and ad account configuration.
From an integration perspective inside n8n: test the webhook flow using a Page Admin account and the Graph API Explorer to confirm that the referral fields are present. Ensure the app has the right roles (admin/testers) or that the Page and ad account are linked to the same Business Manager. If data is missing, check whether Instant Experiences, deep-links, or third-party redirecting layers are stripping referral parameters.
For leaders: factor in time for Meta app review and business verification into project plans. Create standard operating procedures-maintain a dedicated developer app per business unit, document required permissions and webhook subscriptions, and centralize tokens and roles in Business Manager to avoid permission drift and deployment failures.
Original Source
n8n Community