ePrivacy and GPDR Cookie Consent by Cookie Consent Skip to main content

Netcore webhook

This article gives you knowledge of how webhooks send information from Netcore CEE to Meiro Events. Netcore CEE enables brands to listen, analyze, converse and improve conversions across mobile apps and websites through sending email broadcasts, opt-in-based SMS content, web push notifications and messages, app push notifications and in-app messages. 


Requirements

You need to follow these key requirements to properly set up the Netcore webhook:

  1. User has to white-list IP addresses to accept webhook requests;

  2. Assure receiving of the data in the required format (i.e a small script that will receive the data from the webhook call and log it so that the user can validate what was received);

  3. It is recommended to build a queuing system since the Netcore webhook shares the data continuously in batches, which will result in 500 error if the script gets busy processing the received data.

Feature

The Netcore webhook sends data in URL-encoded format, where the key is data and the value is the actual JSON.


Examples of events in Netcore include:

  • Action performed by a user (triggers when a user launches the app, adds a product to the cart, searched for the product, adds to wishlist);

  • Action performed by the user without any other action within a certain time (triggers when user clicks on a specific link in email and visits website but does not buy a product)

Example data

Endpoint: the Web Activity (e.g. ‘product search’).

As soon as the Netcore webhook receives a callback for product search from the Meiro Events, the curl call and the data returned will be as shown below:

data = {
    {
    "<panel_name>": [
        {
        "channel": "custom_activity",
        "custom_params": {
          // custom param will be added here. From Journey you can select custome paramater which you want to pass.
        },
        "att_params": { // attribute will be added here with key:value combination
            "CITY": "Thane&Kalyan",
            "STATE": "Maharashtra11"
        },
        "msgid": "103",
        "webhook_name": "Test Webhook URL for Automation",
        "payload_params": { // these are the payload parameter which you are passing with activity.
            "items": [
            {
                "dateofpurchase_sm": "2018-12-06 17:11:30",
                "category_s": "lifestyle",
                "prqt_s": 1,
                "prid_s": 157,
                "name_s": "sarvesh12345",
                "bydemand_s": "sarvesh",
                "price_s": 9990.91
            },
            {
                "dateofpurchase_sm": "2018-12-06 17:11:30",
                "category_s": "lifestyle",
                "prqt_s": 2,
                "prid_s": 157,
                "name_s": "sarvesh",
                "bydemand_s": "sarvesh",
                "price_s": 9990.91
            }
            ]
        },
        "event_params": {
            "activity_source": "web",
            "ts": 181212120708,
            "activity_id": 103,
            "foreignkey": "<foreignkey>",
            "identity": "<identity>",
            "asset_name": "<name_of_asset_from_smartech>", // name of asset while creating webhook
            "asset_id": "b001207f68c6e40519b5b2c7fb055930", // id os asset which creating webhook
            "guid": "2a867f6d-cb7f-4fb7-8da4-02a5d5dd1bd8"
        },
        "journey_name": "act on webhook trigger test1" // name of journey.
        }
    ]
    }
}

Use cases

Here are practical use cases on how to generate Netcore webhooks with the Meiro Events:

  • Users who looked up for an international flight in business class may be contacted by the call center if their booking is not completed within 30 minutes.

  • The call center may contact the users who abandon the cart in order to solve any issues and complete the purchase.