Skip to main content

Messenger user id (the page-scoped user id). We Need to forward it to Meta

Feature Request

Meta conversions adapter (POST /v1/ads/conversions) already sends messaging_channel at the event root when the action source is business_messaging. It supports whatsapp, messenger and instagram_direct, and for Messenger/Instagram it puts the page_id in user_data. The part that's missing is the Messenger user id (the page-scoped user id). We don't forward it to Meta right now, so there's no way to pass it through us today.

Posted by Target Store ·
Status: Completed1 comment

Log in to comment and vote

Comments1

  • Miquel Palet López

    Team•

    Oct 20

    This is live now. On POST /v1/ads/conversions with actionSource business_messaging, the messaging object takes the page-scoped id per channel:

    • messenger: messaging.pageScopedUserId (the PSID from your Messenger webhook) is sent to Meta as user_data.page_scoped_user_id, next to messaging.pageId.
    • instagram_direct: messaging.instagramScopedUserId (the IGSID) is sent as user_data.ig_sid, and the channel goes out as messaging_channel "instagram".
    • whatsapp: unchanged, ctwaClid as before (it's only sent on WhatsApp events).

    Both ids are sent unhashed, as Meta requires. Example:

    {"events":[{"eventName":"Purchase","eventTime":1761000000,"actionSource":"business_messaging","messaging":{"channel":"messenger","pageId":"123","pageScopedUserId":"456"},"value":49,"currency":"EUR"}]}

    The fields are documented on the conversions endpoint in the API reference.