Does Make require consent?

No. Make operates primarily as a backend automation service with no client-side scripts, cookies, or browser-side data collection on visitor-facing pages. All workflow processing runs server-side. There is nothing to block from a consent management perspective.

How does Make interact with a website?

Make executes automation scenarios on its cloud infrastructure, triggered by webhooks, scheduled events, or API calls from the website backend. It connects to CRMs, email tools, and payment processors via server-to-server API calls. No JavaScript loads in the visitor browser and no cookies are set.

How does ConsentStack handle Make?

ConsentStack classifies Make as functional with no client-side footprint requiring consent management. If ConsentStack detects Make through webhook URL patterns or infrastructure signatures in page source, it records the integration but applies no consent gate since no browser-side tracking occurs.

What tracker domains does Make use?

ConsentStack has catalogued tracker domains for Make including make.com. These are the network destinations Make's scripts contact, which a consent platform blocks until a visitor agrees.

Make - Workflow Automation & Privacy Consent Profile

Back to Vendor Library

Overview

Make (formerly Integromat) is a visual workflow automation platform that connects web applications through event-driven scenarios. Similar to Zapier and n8n, Make enables businesses to automate processes by linking triggers and actions across hundreds of services. When detected on a website, Make typically appears through webhook endpoints, embedded scenario widgets, or partner integrations. The platform operates primarily as a backend automation service with minimal direct browser-side presence on visitor-facing pages.

What This Script Does

Make operates primarily server-side with minimal client-side footprint on visitor-facing pages.

Backend operation: Make scenarios execute on Make's cloud infrastructure, triggered by webhooks, scheduled intervals, or API events from the website's backend. Workflows connect to external services (CRMs, email tools, databases, payment processors) through server-to-server API calls.
Webhook endpoints: The website may expose Make webhook URLs that receive form submissions, event data, or API callbacks from the frontend. The webhook URL itself does not inject scripts into the visitor's browser.
Embedded widgets: Make provides embeddable scenario templates and integration widgets for partner sites, though these are uncommon on end-user-facing pages.
No client-side scripts: Make does not typically load JavaScript or set cookies in website visitors' browsers. All automation processing happens server-side.
No cookies set: No cookies, localStorage, or sessionStorage entries are created on visitor-facing pages by Make.
Detection context: ConsentStack may detect Make through webhook URL patterns, API references, or infrastructure signatures in the website's source code.

Consent & Compliance

Make falls under the functional consent category.

Under GDPR and ePrivacy, Make has no ePrivacy cookie consent implications as it does not set cookies or store data on the visitor's device. Data processed through Make workflows (form submissions, webhook payloads) is personal data under GDPR, but this processing is managed server-side under the site operator's data processing agreements with Make. Make is headquartered in Prague, Czech Republic, and processes EU data under GDPR.

Under CCPA/CPRA, data routed through Make workflows constitutes personal information governed by the site operator's privacy practices.

Should You Block This Without Consent?

No. Make has no client-side presence on visitor-facing pages — no scripts, no cookies, no browser-side data collection. There is nothing to block from a consent management perspective. Data processing concerns for webhook and workflow data are addressed through the site's backend privacy and data processing practices.

Is Make GDPR compliant?

Make typically loads functional trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Make can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Make, not on Make itself.

Visit website