Implementation process
All the Web mediation implementation requires consultation with your Account Manager and QA process before going live.
Code Snippet
<div class="OUTBRAIN"
data-ob-contentUrl="DROP_PERMALINK_HERE"
data-widget-id="DROP_WIDGET_ID_HERE"
data-ob-installation-key="DROP_PARTNER_KEY_HERE"></div>
<script type="text/javascript" async="async"
src="https://widgets.outbrain.com/outbrain.js"></script>
Parameters
| Attribute Name | Requirement | Description | Example value |
|---|---|---|---|
data-ob-contentUrl |
Required | The permalink of placement to identify the currently displayed content | “https://www.outbrain.com/blog/123.html” |
data-widget-id |
Required | The widget id that you received from your Account Manager | “AR_1” |
data-ob-installation-key |
Required | The partner key that you received from your Account Manager | “DEMOP1MN24J3E1MGLQ92067LH” |
data-external-id |
Optional | A unique key for report breakdowns. See Engage External Id Report API for details | “123abcXYZ” |
data-click-url |
Optional | An image pixel URL for tracking clicks on paid recommendations | “https://yourdomain.com/click?123” |
data-consent-string |
Optional:Only if TCF API is not available | Base64-encoded consent string, as defined by IAB for TCF v2.0 | “CO4SiGQO4SiGQAGABBENAzCgAP…(omitted)…YAAAAAAAAAAA” |
data-consent-version |
Optional | Version of consent string | “2” |
Parameters in detail
Consent String
Our JS Widget is fully compliant to TCF v2.0 and it will automatically fetch consent string from CMPs, so there’s no need to pass consent string manually. However, if the WebView does not support TCF API, it’s possible to pass consent string directly to widgets by using the data-consent-string attribute.