The IAB's Transparency and Consent Framework (TCF) was created in order to help digital advertising ecosystem comply with obligations under the GDPR and ePrivacy Directive. While Sourcepoint supports an implementation for organization's who wish to comply with the TCF v2, we also enable your organization to implement and manage end-user consent without having to sign on to the IAB TCF framework.

In this article, we will cover how to implement a GDPR nonTCF web implementation so that your organization can create a consent experience that complies with your interpretation of GDPR that is not bound by the IAB TCF v2 policy requirements.

• ​GDPR non-TCF Web Implementation Overview​

• ​Optional GDPR non-TCF Web Implementation Parameters​

GDPR non-TCF Web Implementation Overview

The GDPR non-TCF web implementation is comprised of two scripts that is added to a property:

• ​Client Configuration Code Snippet​

• ​URL to Sourcepoint Javascript SDK​

In this section, we will provide an overview and any necessary requirements for each code snippet. In the example below, we combine the two snippets to illustrate a simple GDPR non-TCF web implementation that would be added to a property.

<script>
    window._sp_ = {
        config: {
            accountId: 22,
            baseEndpoint: 'https://cdn.privacy-mgmt.com',
        }
    }
</script>
<script src="https://cdn.privacy-mgmt.com/messagingNoTcfApi.js" async></script>

Client Configuration Code Snippet

The first code snippet that should be added to your implementation contains your organization's specific account configuration parameters. This code snippet includes the necessary and optional parameters for your property to communicate with the Sourcepoint messaging platform and consent service libraries.

<script>
    window._sp_ = {
        config: {
            accountId: 22,
            baseEndpoint: 'https://cdn.privacy-mgmt.com',
        }
    }
</script>

Currently, there are two required parameters to successfully deliver an end-user notification:

• AccountId

• baseEndpoint

In addition to the required parameters (example above), your organization can implement additional parameters in the code snippet to allow for Javascript callbacks that can be triggered for different customization purposes.

URL to Sourcepoint Javascript SDK

The second code snippet is a URL that points to the Sourcepoint Javascript SDK for a GDPR non-TCF web implementation. The URL for a GDPR non-TCF web implementation is as follows:

• https://cdn.privacy-mgmt.com/messagingNoTcfApi.js

<script src="https://cdn.privacy-mgmt.com/messagingNoTcfApi.js" async></script>

Optional GDPR non-TCF Web Implementation Parameters

In the table below are all the parameters that can be included in your client configuration code snippet:

​