Integrations
Zapier integration
Connect DataCops to thousands of apps with no code. Read clean, verified conversions and identified leads out, or send an order in and have it delivered server-side to your ad platforms. You connect with one private API key.
What it is
The DataCops app for Zapier lets you connect DataCops to thousands of other apps without writing code. It gives you two triggers that send clean, verified data out of DataCops, and one action that sends a conversion in and delivers it server-side to your connected ad platforms.Everything runs over the same DataCops API, so the data Zapier reads is the same clean, bot filtered, consented data the rest of the platform produces. Zapier is not a separate pipeline. It is a no-code door onto the one you already have.
What you can build
Because Zapier connects DataCops to almost any app, a few common flows:
- Log every validated conversion to a Google Sheet or a Slack channel, so your team sees real sales as they happen.
- Send every identified lead into a CRM or a spreadsheet with its full journey attached.
- Take a Stripe payment, a Shopify order, or a form submission from any app and send it into DataCops, where it is verified and delivered on to your ad platforms as a clean conversion.
Triggers: read clean data out
A trigger starts a Zap when something happens in DataCops. Both triggers return real, verified data:
| Trigger | When it fires and what to do with it |
|---|---|
| New Validated Conversion | Fires when a clean, verified conversion is delivered. Use it to log real sales to a sheet, notify a channel, or push them into another tool. |
| New Identified Lead | Fires when a real person is identified, with their journey and fraud verdict. Use it to route qualified leads anywhere you like. |
Because the data has already passed the fraud verdict and the consent gate, whatever you connect downstream only ever receives real, consented people.
Action: send a conversion in
An action does something in DataCops as a step in your Zap:
- Send Conversion Event. Push an order or signup into DataCops from any app. DataCops validates it and delivers it server-side to your connected ad platforms, the same clean path as every other conversion. See CAPI delivery for what happens next.
Get your API key and connect
You connect Zapier to DataCops with a private API key. Here is the whole setup:
Open your project
Sign in at app.joindatacops.com and open the project you want to connect. It already holds your validated conversions and identified leads, so there is live data to test with.
Create a Private API key
In the left sidebar go to Settings, then API Keys, and open the Private keys tab. Click New key, name it (for example, "Zapier"), and confirm.
Copy the key
A key starting with
dcp_appears. Copy it now, it is shown only once.Paste it into Zapier
When Zapier asks you to connect your DataCops account, paste the
dcp_key. It authenticates through thex-dc-keyheader, so no password or OAuth pop-up is needed.Test the triggers and action
New Validated Conversion and New Identified Lead return real data from your project, and Send Conversion Event validates a conversion and delivers it server-side. Once they work, turn your Zap on.
Works in Make and n8n too
The same dcp_ key and the same x-dc-key header work anywhere you can
call an API, so Make, n8n, and your own scripts connect to DataCops exactly the same way. There
is one API underneath all of them, which means you never rebuild an integration per tool: pick
whichever automation app you prefer and it reads and writes the same clean data.