Webhook endpoint

Placeholders
When you create a campaign you must define a property webhook_endpoint.
This endpoint in an https url that can contains placeholder
[CAMPAIGN_ID]
[AUDIENCE_ID]
[CAMPAIGN_NAME]
[REFERENCE_ID]
[TIMESTAMP]
All placeholders exists with an ENC_ name for url encoded values.
Example : 
https://endpoint.company.com/api/v1/endpoint_notify/campaign/[CAMPAIGN_ID]

Body notification
You may have to pass some custom data on your network and get them back in your endpoint.
In the UE, the UK, Iceland, Liechtenstein and Norway, unless specifically and by written authorized not to, do not call the tag if you didn't previously collected a valid consent for Purposes 1 & 3 and Vendor 53 under the IAB Europe Transparency & Consent Framework, and add the mandatory gdpr=[gdpr_applies]&gdpr_consent=[tc_string] parameters in the URL.
TAG WILL ACCESS A COOKIE : DO NOT CALL IT UNLESS YOU PREVIOUSLY COLLECTED A VALID CONSENT TO DO SO WHENEVER REQUESTED BY LOCAL LAW
Add this pixel in your network :
 https://js.sddan.com/PMAP.d?pa=[PARTNER_ID]&gdpr=[gdpr_applies]&gdpr_consent=[CONSENT_STRING]&args_myfirstarg=XXXX&args_mysecondarg=YYYYY
(mandatory) [PARTNER_ID] : numerical value - is given by your contact at Sirdata 
(mandatory for EEA/UK users) gdpr : TCF V2 gdpr_applies parameter​
(mandatory for EEA/UK users) gdpr_consent : TCF V2 TC String​
When you create your campaign you must precise filter_partner_audience: true.
In the JSON body notification you will receive this object :
{
    campaign_id: "MY_CAMPAIGN_ID",
    audience_id: "MY_AUDIENCE_ID",
    value: "MD5 OR REFERENCE_ID",
    campaign_name: "MY_CAMPAIGN_NAME",
    arguments: {
        myfirstarg: "XXXX",
        mysecondarg: "YYYYY"
    }
}
​
Notification API - Previous
Campaign
Next - Audience API
About Audience API
Last updated 6 months ago