canonical: https://jentic.com/apis/adrails.ai/adrails # Adrails Tracking API The Adrails Tracking API provides first-party visitor and conversion tracking for your own site and server. A tracking script records visits along with the campaign, ad, and click id each visitor arrived with, and a collect endpoint records events such as purchases and leads. Events your server signs with the server key are forwarded to Meta and Google Ads for conversion reporting. ## For AI agents Record first-party visits and conversion events, capture the campaign and click id a visitor arrived with, and forward signed events to ad platforms. ## Scope Does not handle ad buying, audience targeting, or campaign reporting dashboards. Use for first-party visit and conversion event tracking only. ## Capabilities - Load a first-party tracking script for a site - Record visitor events such as purchases and leads - Capture the campaign, ad, and click id a visitor arrived with - Forward server-signed conversion events to Meta and Google Ads ## Use cases ### Agent-Managed Conversion Tracking A marketer wants purchases and leads reported back to the ad platforms without hand-wiring pixels. The Adrails API records a conversion event and, when the server signs it with the server key, forwards it to Meta and Google Ads, so an agent can wire first-party conversion tracking for a site from one endpoint. Example prompt: Record a purchase conversion event signed with the server key so it is forwarded to Meta and Google Ads ### First-Party Visit Attribution An analytics team needs to know which campaign, ad, and click brought each visitor. The Adrails tracking script records visits along with the campaign, ad, and click id they arrived with, so an agent can set up first-party attribution that survives third-party cookie loss. Example prompt: Load the tracking script on a site and record visits with the campaign, ad, and click id each visitor arrived with ### Server-Side Conversion Forwarding A team moving to server-side tagging wants conversions sent from their own backend. The Adrails collect endpoint records events, and only server-signed events are forwarded onward, so an agent can send purchases and leads from the server with the integrity the ad platforms expect. Example prompt: Send a lead event from the server, signed with the server key, so it is forwarded to the ad platforms ## Key resources - **Tracking script** — Load the first-party tracking script that records visits - **Event collection** — Record purchase and lead events and forward signed ones onward ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 67 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 66 / 100 - Developer Experience & Jentic Compatibility: 67 / 100 - AI-Readiness & Agent Experience: 56 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 75 / 100 - **View full report:** https://jentic.com/apis/adrails.ai/adrails/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring Adrails by hand means loading the tracking script and signing each event with your server key before it reaches Meta or Google Ads. Through Jentic you install once, import it from the API Directory, store the server key once, and your agent calls it. - **Permission scoping:** You choose which Adrails operations your agent may call, so it can load the script and record events while nothing beyond the tracking surface is reachable unless you add it. - **Credential handling:** Your Adrails server key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'record a conversion event' or 'load the tracking script', and Jentic returns the matching Adrails operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Plausible Analytics** — Plausible is privacy-friendly site analytics; Adrails focuses on first-party conversion tracking forwarded to ad platforms. - **Mixpanel** — Mixpanel tracks in-product events and funnels; Adrails tracks site visits and ad-platform conversions with campaign and click ids. - **Segment** — Segment is a customer data pipeline that fans events to many tools; Adrails is the first-party source that records and signs conversions. ## FAQ ### What authentication does the Adrails Tracking API use? The Adrails API signs event collection with a server key sent as a bearer token in the Authorization header, per its OpenAPI spec. Loading the tracking script needs no credential, and only server-signed events are forwarded to Meta and Google Ads. Through Jentic the server key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context. ### Can I record a conversion event through an agent? Yes. The collect endpoint records events such as purchases and leads, and when the event is signed with your server key it is forwarded to Meta and Google Ads. An agent can record conversions from your server so the ad platforms receive them. ### What are the rate limits for the Adrails Tracking API? The OpenAPI spec does not define rate limits, and it notes that every field, limit, and error is checked against the serving code. Check the Adrails documentation at https://adrails.ai/docs for the current limits. ### How do I set up conversion tracking through Jentic? Import the Adrails Tracking API from the Jentic directory and give your agent an intent such as 'record a conversion event'. Jentic returns the collect operation with its input schema, your agent sends the signed event, and your stored server key is injected at execution time. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the Adrails Tracking API? Yes. Write a rule that allows only the script-load and event-collect operations, so your agent can set up tracking and record conversions but nothing beyond that surface, and every call it makes is logged. ### Is there an Adrails MCP server? You don't need an MCP server to give your agent the Adrails Tracking API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, so no extra server's tool definitions sit in the agent's context.