Webhook Collection June 28, 2024 14:35 Updated Index: How does the Webhook work? Which networks does this collection cover? Relationship with access token Understand how interactions and other data from your proprietary pages are collected by STILINGUE. To successfully monitor publications and interactions on different social networks, STILINGUE uses various collection systems tailored to the specificities of each network and the areas that will be fed by the data (Listening, Smart Care, Proprietary Metrics, Radar). Among the systems used is collection via API ("Application Programming Interface"), an application that enables the connection between our platform and the social network responsible for delivering the data. One of these collection possibilities is through Webhook, which stands out for being specific to proprietary pages and for bringing publications more quickly compared to other processes. You may have come across this term if you have sought information in the guides on Data Collected in Proprietary Metrics - if you haven't seen it, reading is recommended, as these guides show exactly which data and types of collection for each network are performed by the platform. How does the Webhook work? In a "standard" collection, imagine that STILINGUE requests from a particular social network what the publications, comments, and other data published in a given period were, based on the connected proprietary pages. After this initial request, the involved social network will return the request, and the platform will collect the desired data. This flow is done continuously so that the research continues to be fed with the most recent publications. In the case of Webhook, this initiative comes from the social network itself, which informs and sends new interactions to STILINGUE whenever there is updated data. Therefore, the process ends up being faster when compared to the traditional collection model. Currently, data collected via Webhook is brought in every 15 minutes, regardless of the customer's contracted plan. Which networks does this collection cover? Currently, this type of proprietary collection is available for the following networks: Facebook, Instagram, and Twitter. It is important to note that the Webhook does not capture all content formats from these networks. For instance, in the case of Instagram, the collection of Dark Posts is not carried out in this manner. Some collections are also exclusively done via Webhook, such as the collection of mentions on Instagram. The complete list of publications and interactions via Webhook is available in the guides on Data Collected in Proprietary Metrics, segmented for each social network: Facebook Instagram Twitter YouTube Google Play LinkedIn Relationship with access token In general, the operation of the Webhook is not a perceptible process "by the naked eye": the best way to determine if the data retrievals are occurring smoothly is to observe whether the posts are being brought into your search. To ensure the correct operation of data retrieval through the Webhook, it is essential to keep the access token for your proprietary page constantly updated and without authentication failures. The Webhook is directly related to proprietary connections made on the platform, so the functionality is compromised if the token for the page expires after a certain period. For more information on access tokens, refer to the guide. For more information, visit the discussion on the subject at our community or videos on our channel. 😃 Related articles Sending Data for Analysis via Webhooks How to save human service history via Blip Integration with Google Drive How to connect your own application through Advanced Settings Blip media upload policy Sending WhatsApp Active Messages on Blip Desk