Consent

Most merchants now have a consent banner on their website. EdgeTag fully supports consent flow both in the browser and on the server. We first verify consent in the browser when the event is triggered, and then on the server as well, to ensure compliance. If your customer is still not using consent, you can skip this step and go to the channel step.

Consent can be set up when you add a website, but it can also be enabled after the fact.

The values that are used are:

• DISABLED

• CUSTOM

In API documentation, you will see that other values are also possible, but that is used for EdgeTag internal setup, and you will not get automatic support for Shopify consent Privacy API if you select SHOPIFY

PUT /tag/{tagId}

JavaScript

fetch('https://api-sandbox.edgetag.io/tag/{tagId}', {
  method: 'PUT',
  headers: {
    'Accept': 'application/json',
    'Authorization': 'Bearer your-token',
    'Team-Id': '{your-team-id}'
  },
  body: JSON.stringify({
    name: 'Domain',
    domain: 'abc.domain.com',
    rootDomain: 'domain.com',
    debug: false,
    currencyConversion: null,
    sameSite: 'LAX',
    managed: true,
    hostId: '',
    allowedEvents: null,
    gpc: false,
    cookieMapKey: '_shopify_y',
    platform: "SHOPIFY",
    idStorageMapping: null,
    consent: 'CUSTOM'
  })
})

cURL

If you don't have tag information, you can also first call the GET API and then update the consent property on the object that is returned.