Developer

Qualification gate

Set a conversion to hold until it is qualified, then call this endpoint from your CRM or automation when the lead qualifies. DataCops releases the held conversion, with its original ad click IDs, to your connected platforms.

What it does

When you mark an event as "When qualified" in Data Sync, DataCops captures the conversion and its ad click IDs but holds delivery. Your ad platforms only learn from leads that turn into real, qualified business. When your CRM decides a contact qualifies (for example a deal stage moves, or a HubSpot workflow fires), it calls this endpoint, and DataCops releases the held conversion for that person, replaying the original click IDs so attribution is intact.

Get your keys

This endpoint uses two values, both scoped to your app: your api_key and a release secret. You get the secret from Data Sync, in the setup instructions for the Qualified row. Keep the secret server-side.

Release a qualified conversion

POST /api/v1/crm-release/:api_key/:secret

Send the event name and the person's email. DataCops finds the matching held conversion for that email and releases it. You do not send any CRM-specific fields, just the two below.

cURL

curl -X POST \
  https://api.joindatacops.com/api/v1/crm-release/YOUR_API_KEY/YOUR_SECRET \
  -H "Content-Type: application/json" \
  -d '{
    "event_name": "Lead",
    "email": "[email protected]"
  }'

event_name: the conversion that was held, for example Lead or Purchase.
email: the person's email, used to find their held conversion.

The response

200 OK

{ "success": true, "released": 1 }

200: the held conversion was released and delivered.
404: no held conversion found for that email and event.
400: missing event_name or email.
401: invalid api_key or secret.