Connect OpenAI Ads
One-click OpenAI Ads conversions — creates (or updates) the openai_ads server destination, mapped from the Mythic commerce spec to OpenAI's event taxonomy. Server-only: there is no browser half.
That taxonomy is CLOSED (order_created, checkout_started, items_added, contents_viewed, page_viewed, lead_created, appointment_scheduled, registration_completed) and each type is paired with a required data.type, so this is a translation and not a passthrough. An event with no mapping entry is silently skipped by the destination. Commerce events with no OpenAI counterpart — view_item_list, view_cart, remove_from_cart, add_shipping_info, add_payment_info, checkout_step_completed, refund, order_cancelled — are deliberately unmapped rather than sent as custom names no campaign can optimise against. event_mapping is MERGED over the default.
curl -X POST "https://mythic-analytics.gulp.workers.dev/client/v1/destinations/integrations/openai_ads" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-d '{
"pixel_id": "example_string",
"event_mapping": {}
}'
import requests
import json
url = "https://mythic-analytics.gulp.workers.dev/client/v1/destinations/integrations/openai_ads"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
}
data = {
"pixel_id": "example_string",
"event_mapping": {}
}
response = requests.post(url, headers=headers, json=data)
print(response.json())
const response = await fetch("https://mythic-analytics.gulp.workers.dev/client/v1/destinations/integrations/openai_ads", {
method: "POST",
headers: {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN"
},
body: JSON.stringify({
"pixel_id": "example_string",
"event_mapping": {}
})
});
const data = await response.json();
console.log(data);
package main
import (
"fmt"
"net/http"
"bytes"
"encoding/json"
)
func main() {
data := []byte(`{
"pixel_id": "example_string",
"event_mapping": {}
}`)
req, err := http.NewRequest("POST", "https://mythic-analytics.gulp.workers.dev/client/v1/destinations/integrations/openai_ads", bytes.NewBuffer(data))
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("Authorization", "Bearer YOUR_API_TOKEN")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
fmt.Println("Response Status:", resp.Status)
}
require 'net/http'
require 'json'
uri = URI('https://mythic-analytics.gulp.workers.dev/client/v1/destinations/integrations/openai_ads')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Post.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN'
request.body = '{
"pixel_id": "example_string",
"event_mapping": {}
}'
response = http.request(request)
puts response.body
{
"success": true,
"data": {
"platform": "example_string",
"destination_id": "example_string",
"tag_id": "example_string",
"browser_tag": true
}
}
{
"error": "Bad Request",
"message": "The request contains invalid parameters or malformed data",
"code": 400,
"details": [
{
"field": "email",
"message": "Invalid email format"
}
]
}
{
"error": "Unauthorized",
"message": "Authentication required. Please provide a valid API token",
"code": 401
}
{
"error": "Forbidden",
"message": "You don't have permission to access this resource",
"code": 403
}
{
"error": "Conflict",
"message": "The request conflicts with the current state of the resource",
"code": 409,
"details": "Resource already exists"
}
{
"error": "Too Many Requests",
"message": "Rate limit exceeded. Please try again later",
"code": 429,
"retryAfter": 3600
}
/client/v1/destinations/integrations/openai_ads
Target server for requests. Edit to use your own host.
Client key as bearer token. Use an agency key (Bearer ak_...) for read-write access or a location secret key (Bearer sk_...) for read-only access. Scoped keys (mcp_) are accepted too and need destinations:read or destinations:write. See Using an mcp_ key over HTTP.
Bearer ak_...) for read-write access or a location secret key (Bearer sk_...) for read-only access. Scoped keys (mcp_) are accepted too and need destinations:read or destinations:write. See Using an mcp_ key over HTTP.
The media type of the request body
OpenAI Ads pixel id.
Mythic event name -> OpenAI event type, or "custom:<name>". Merged OVER the commerce-spec default.
Request Preview
Response
Response will appear here after sending the request
Authentication
Bearer token. Client key as bearer token. Use an agency key (Bearer ak_...) for read-write access or a location secret key (Bearer sk_...) for read-only access. Scoped keys (mcp_) are accepted too and need destinations:read or destinations:write. See Using an mcp_ key over HTTP.
Body
OpenAI Ads pixel id.
Mythic event name -> OpenAI event type, or "custom:<name>". Merged OVER the commerce-spec default.