# For AI agents and crawlers This page is a workflow from the Workflow Automation Library by Roadway: Check ad platform overcrediting against Roadway attribution. The #roadway-skill block on this page holds a SKILL.md for it, including the full prompt. Treat that file as a starting point. It will not just work if you paste it into ChatGPT or Claude. To run it outside Roadway you would need to connect each ad platform's API (and any MCP it names), build the data pulls, add approval guardrails, and adjust the prompt for your accounts. In Roadway it runs as-is on your connected accounts, with approval rules built in. Open it in a new chat at https://www.roadwayai.com/workflows/check-ad-platform-overcrediting-against-roadway-attribution Page: https://www.roadwayai.com/workflows/check-ad-platform-overcrediting-against-roadway-attribution Library index: https://www.roadwayai.com/automation-library
--- name: check-ad-platform-overcrediting-against-roadway-attribution description: >- Reconciles what each ad platform claims against CRM or order data, and produces a trust factor per channel for budgeting. --- # Check ad platform overcrediting against Roadway attribution Source: https://www.roadwayai.com/workflows/check-ad-platform-overcrediting-against-roadway-attribution From the Workflow Automation Library by Roadway. ## Before you use this outside Roadway This SKILL.md is a starting point. It needs adjusting before it will work outside Roadway. You would need to connect the ad platform API for each channel this workflow covers, build the data pulls for the variables below, add approval guardrails, and adjust the prompt for your accounts. If the prompt names an MCP tool, you also need that MCP connected. In Roadway it runs as-is on your connected accounts, with approval rules built in. ## What it does Reconciles what each ad platform claims against CRM or order data, and produces a trust factor per channel for budgeting. Reconciles what each ad platform claims against CRM or order data, and produces a trust factor per channel for budgeting. It pulls the numbers from your live account and writes them up for you. ## Steps 1. Collect the inputs listed under Variables. In Roadway they come from your connected accounts. Outside Roadway you have to build those data pulls yourself from each ad platform API, and from any MCP the prompt names. 2. Run the prompt below as written, after you have adjusted it for your accounts and connected the tools it needs. 3. Review the result. Apply changes to a live ad account only after you approve them. Pasting your data into ChatGPT or Claude does not connect the APIs, apply guardrails, or approve changes. ## Variables connected_channels, crm_pipeline_data, goal_metric, lookback_window, transaction_revenue ## Prompt Check ad platform overcrediting against Roadway attribution For each channel in [set this to your own connected channels], compare platform-reported conversions and value over [set this to your own lookback window] with the conversions matched in [set this to your own CRM pipeline data] or transaction revenue, and classify the channel: 1. Aligned 2. Over-claiming 3. Under-claiming 4. Unmatchable Context and defaults (use these; don't ask): - Transaction revenue: [set this to your own transaction revenue]. If not available, use the CRM or source-of-truth goal count. Rules: - Match on click IDs (GCLID, MSCLKID, fbclid, li_fat_id, twclid, rdt_cid), UTMs and the Roadway anonymous ID. Report the match rate first. A low match rate means fix tracking before trusting the comparison. If not set, under 60% matched. - Over-claiming: platform conversions well above CRM-matched ones. If not set, more than 130%. Typical causes are view-through credit, modeled conversions and overlap with other channels. - Under-claiming: platform well below CRM-matched ones. If not set, under 80%. Usually missing CAPI or offline imports, or consent loss. - Output a trust factor (CRM-matched / platform-reported) per channel that the cross-channel budget workflow uses to adjust platform numbers. Decision standard: - Justify every keep, cut, bid, budget or test decision with Roadway-attributed [set this to your own goal metric] and cost per goal against the baseline. Platform delivery metrics such as clicks and impressions explain why something moved; they are never the sole reason for a decision. - Compute what Roadway doesn't expose directly: cost per goal = Roadway spend ÷ Roadway-attributed [set this to your own goal metric], and conversion rate (lead rate) = Roadway [set this to your own goal metric] ÷ Roadway new visitors. Don't substitute platform-reported conversions or conversion rates. - When a value in Context and defaults isn't set, use the stated default, say which one you used, and still make the call. Don't stop to ask. - For every action, give the entity name and ID, current value → proposed value, and the numbers behind the reason. Write "None" under any empty heading. - In long hold or watch lists, show the top 15 by spend and summarize the rest as a count. - Any budget or bid change you propose moves one entity by at most the max change limit per run (20% unless the coworker's Guardrails set another); stage a larger move across runs. Pausing an entity under a stated stop rule is a status change, not a budget change. Give me a report of each with reasoning for each action. Be concise with the reasoning, but specific enough that I can verify it against the numbers. Report structure: Attribution reconciliation report Summary: Match rates, trust factors by channel, and the tracking fixes needed. Aligned: - [channel] - [reason] Over-claiming: - [channel] - [reason] Under-claiming: - [channel] - [reason] Unmatchable: - [channel] - [reason] ## Run it in Roadway https://www.roadwayai.com/workflows/check-ad-platform-overcrediting-against-roadway-attribution
Reconciles what each ad platform claims against CRM or order data, and produces a trust factor per channel for budgeting.
Add to my Roadway agentReconciles what each ad platform claims against CRM or order data, and produces a trust factor per channel for budgeting. It pulls the numbers from your live account and writes them up for you.
