# Buron > Buron is the agentic marketing platform — SEO, content, ads, analytics, and growth planned and executed by AI agents grounded in your knowledge, code base, and data. ## Marketing - [Home](/index.md) — Product overview - [Blog](/blog.md) — Articles on agentic marketing - [Changelog](/changelog.md) — Product updates - [Guides](/guides.md) — Step-by-step guides - [Glossary](/glossary.md) — Marketing definitions, A–Z ## Product - [Multi-touch attribution](/product/attribution.md) — See which touches earn revenue - [Cross-channel analytics](/product/analytics.md) — Cross-channel dashboards - [Google Ads reporting and optimization](/product/google-ads.md) — Daily checks, drafted fixes - [Meta Ads reporting and optimization](/product/meta-ads.md) — Signal and creative checks - [TikTok Ads reporting and optimization](/product/tiktok-ads.md) — Creative and pacing checks - [First-party tracking pixel](/product/pixel.md) — First-party tracking - [Managed marketing data warehouse](/product/warehouse.md) — Your marketing data, queryable - [The marketing agent](/product/agent.md) — Checks, diagnoses, drafts fixes - [Self-documenting marketing wiki](/product/knowledge.md) — A wiki that writes itself - [Buron over MCP](/product/mcp.md) — Your data in Claude and Cursor - [The Buron CLI](/product/cli.md) — From the terminal and CI ## Docs - [Welcome to Buron](/docs.md) - [Integrations](/docs/integrations.md) - [Connect Google Search Console](/docs/search-console.md) - [Connect your TikTok Ads account](/docs/tiktok-ads.md) - [Use cases](/docs/use-cases.md) - [Connect your YouTube channel](/docs/youtube.md) ### Account - [Manage your plans and billing](/docs/account/billing.md) - [Track credits and AI usage](/docs/account/credits-and-usage.md) ### Agent - [Manage your conversations](/docs/agent/conversations.md) - [Ask your first question](/docs/agent/first-question.md) - [Meet the Agent](/docs/agent/overview.md) - [What the Agent can do](/docs/agent/tools.md) ### Automations - [Build your own automation](/docs/automations/build.md) - [Example automations](/docs/automations/examples.md) - [Manage your automations](/docs/automations/manage.md) - [What are Automations](/docs/automations/overview.md) ### Attribution - [Connect your CRM](/docs/attribution/connect-crm.md) - [Connect Shopify](/docs/attribution/connect-shopify.md) - [Set up first-party tracking](/docs/attribution/first-party-tracking.md) - [Install the Buron pixel](/docs/attribution/install-pixel.md) - [How Buron attribution works](/docs/attribution/overview.md) ### Channels - [Reply to Buron by email](/docs/channels/email.md) - [Reply to the Agent from anywhere](/docs/channels/overview.md) - [Connect Slack and message the Buron agent](/docs/channels/slack.md) - [Connect WhatsApp and reply to Buron in chat](/docs/channels/whatsapp.md) ### Cli - [Run Buron from CI](/docs/cli/ci.md) - [Command reference](/docs/cli/commands.md) - [Configure the CLI](/docs/cli/configuration.md) - [Use Buron in your AI editor](/docs/cli/editor-skills.md) - [Install the Buron CLI](/docs/cli/installation.md) ### Conversion upload - [Google Ads](/docs/conversion-upload/google-ads.md) - [Conversion upload](/docs/conversion-upload/overview.md) ### Google ads - [Audit your account](/docs/google-ads/audit.md) - [Automate your reporting](/docs/google-ads/automate.md) - [Set up a campaign naming convention](/docs/google-ads/campaign-naming.md) - [Connect your Google Ads account](/docs/google-ads/connect.md) - [Set up your conversion tracking](/docs/google-ads/conversion-tracking.md) - [Optimize your campaigns](/docs/google-ads/optimize.md) - [What Buron does for Google Ads](/docs/google-ads/overview.md) - [Review your Google Ads reports](/docs/google-ads/reports.md) - [Configure your Google Ads workspace](/docs/google-ads/settings.md) ### Knowledge - [Add sources to Knowledge](/docs/knowledge/add-sources.md) - [Browse and curate your Knowledge](/docs/knowledge/browse-and-curate.md) - [What is Knowledge](/docs/knowledge/overview.md) - [Sync Knowledge with your codebase](/docs/knowledge/sync-from-codebase.md) ### Mcp - [MCP authentication](/docs/mcp/authentication.md) - [Automate launch filing](/docs/mcp/automate-launch-filing.md) - [Connect Buron to Claude Code](/docs/mcp/connect-claude-code.md) - [Connect Buron to Codex](/docs/mcp/connect-codex.md) - [Connect Buron to Cursor](/docs/mcp/connect-cursor.md) - [Connect Buron to GitHub Copilot](/docs/mcp/connect-github-copilot.md) - [File your first launch](/docs/mcp/file-your-first-launch.md) - [How launches work](/docs/mcp/how-launches-work.md) - [How the Buron MCP server works](/docs/mcp/overview.md) - [Query ad performance from your editor](/docs/mcp/query-ad-performance.md) - [Read and write knowledge files](/docs/mcp/read-write-knowledge.md) - [MCP tools reference](/docs/mcp/tools.md) ### Reports - [Build a custom dashboard](/docs/reports/dashboards.md) - [Build a report from a dataset](/docs/reports/explore.md) - [Save and reuse a report](/docs/reports/saved-queries.md) ## Topic hubs - [Marketing attribution models: what each one is for and how to choose](/topic/attribution.md) — Every attribution model files a different report from the same journey. This article unpacks what each of the seven is for, and how to choose for B2B, self-serve, or ecommerce. - [The complete guide to conversion tracking](/topic/conversion-tracking.md) — The operator's guide to trustworthy conversion data: what conversion tracking is, how signals break, and how to set up, fix, and harden tracking on every platform. ## Glossary - [Click ID (gclid / fbclid / wbraid)](/glossary/click-id.md) — A click ID is a unique URL parameter an ad platform adds at click time (gclid, fbclid, msclkid, ttclid) so a conversion can be matched back to the exact ad click. - [Consent mode (v2)](/glossary/consent-mode-v2.md) — Consent mode is the API that tells Google tags what a visitor consented to. Version 2 added two signals, required for EEA ads measurement since March 2024. - [Conversions API (CAPI)](/glossary/conversions-api.md) — The Conversions API is Meta's server-to-server channel for conversion events: a second delivery route for the same events the pixel sends from the browser. - [Cookie lifetime / ITP](/glossary/cookie-lifetime-itp.md) — Cookie lifetime is how long a cookie actually survives in the browser: Safari's ITP caps script-set cookies at 7 days, sometimes 24 hours, whatever expiry you set. - [Cookieless tracking](/glossary/cookieless-tracking.md) — Cookieless tracking is measurement that doesn't depend on third-party cookies: first-party data, server-side events, hashed-identifier matching, and modeled conversions. - [Cross-domain tracking](/glossary/cross-domain-tracking.md) — Cross-domain tracking keeps a visitor recognized as one session when they move between domains you own, by passing the identifier across the domain boundary. - [Enhanced conversions](/glossary/enhanced-conversions.md) — Enhanced conversions sends hashed first-party data (email, phone, or name plus home address) with your Google Ads conversion tags, recovering matches cookies lose. - [First-party data](/glossary/first-party-data.md) — First-party data is data you collect from your own audience on your own surfaces (site events, CRM records, order history) under your direct consent. - [Identity resolution](/glossary/identity-resolution.md) — Identity resolution (user stitching) connects events and records carrying different identifiers (hashed email, user ID, click ID, device ID) into one person. - [LTV & LTV:CAC ratio](/glossary/ltv.md) — Customer lifetime value (LTV) is the total value a customer generates over the whole relationship; LTV:CAC divides it by the cost to acquire that customer. - [Meta pixel](/glossary/meta-pixel.md) — The Meta pixel is Meta's JavaScript snippet that reports website events (PageView, Purchase, Lead) from the visitor's browser to Meta for measurement and optimization. - [Offline conversions](/glossary/offline-conversions.md) — Offline conversions complete away from your website and are imported back into the ad platform afterward, joined to the original ad click by click ID or hashed email. - [Server-side tagging (sGTM)](/glossary/server-side-tagging.md) — Server-side tagging runs your tag manager on a server you control, so events reach ad and analytics platforms from your infrastructure instead of the visitor's browser. - [Server-side tracking](/glossary/server-side-tracking.md) — Server-side tracking sends conversion and analytics events from a server you control instead of the visitor's browser: a more durable route for the same events. - [Signal quality](/glossary/signal-quality.md) — Signal quality is the fitness of your conversion data as an input to automated bidding: complete, deduplicated, on time, and carrying real values. - [Smart Bidding](/glossary/smart-bidding.md) — Smart Bidding is Google Ads' auction-time automated bidding (tCPA, tROAS, Maximize conversions, Maximize conversion value), setting each bid from the conversion data you feed it. - [The tracking bottleneck](/glossary/the-tracking-bottleneck.md) — The tracking bottleneck is the point where conversion signal quality caps everything downstream: bidding, attribution, and MMM can't be better than the data they're fed. - [Third-party cookies](/glossary/third-party-cookies.md) — Third-party cookies are cookies set by a domain other than the one you're visiting: the basis of cross-site ad targeting, blocked by Safari and Firefox, kept by Chrome. - [Tracking pixel](/glossary/tracking-pixel.md) — A tracking pixel is a tiny image or script that fires an HTTP request on a pageview or event, carrying the URL, referrer, timestamp, and identifiers to a collection server. - [UTM parameters](/glossary/utm-parameters.md) — UTM parameters are the standard URL query parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) that attribute a visit to its campaign. - [Value-based bidding](/glossary/value-based-bidding.md) — Value-based bidding is automated bidding that optimizes toward conversion value instead of conversion count: tROAS and Maximize conversion value on Google Ads. ## Blog - [Which attribution model should you use? Start with the setup, not the model](/blog/which-attribution-model-should-you-use.md) — There is no single best attribution model. Choose the setup your motion needs, build it in the right order, and measure self-serve and sales-led on their own terms. - [Where Buron fits alongside your product analytics](/blog/buron-alongside-product-analytics.md) — Wondering whether Buron and your product-analytics tool do the same job? They don't, and this draws the line: what each one answers, what Buron deliberately is not, and how to decide for your own stack. - [The tracking bottleneck: your bids are only as good as your signal](/blog/the-tracking-bottleneck.md) — Smart Bidding and Advantage+ optimize toward whatever conversion data arrives. Broken, duplicated, late, or value-less signals don't just mis-report; they mis-spend. The four signal defects, why tracking decays after setup, and what running signal quality as an operations discipline looks like. - [Why your Mixpanel attribution doesn't match your ad platforms](/blog/mixpanel-attribution-doesnt-match.md) — Your Mixpanel numbers and your ad platform's numbers will never match, and mostly that's fine. Here's how to tell an expected gap from a real defect, and the one-page memo to bring to the budget review instead of a panic. - [Why your future MMM depends on the data you label today](/blog/mmm-data-labeling.md) — Marketing mix modeling is sold as a modeling problem. It's really a labeling problem, and the campaign names you write this week decide how much of it you'll be able to run in two years. Here's why history can't be re-labeled, and the naming system that fixes it going forward. - [Every platform claims the same conversion: why ad platforms overreport](/blog/why-ad-platforms-overreport-conversions.md) — Sum your Meta, Google, and TikTok dashboards and you'll get more conversions than you have customers. That's not fraud and not a bug: each platform attributes within its own window, independently, view-through included. What each number is actually for, and where the real count lives. - [Smart Bidding is a signals problem: what the algorithm actually runs on](/blog/smart-bidding.md) — Which Smart Bidding strategy you pick matters less than the conversion data you send it. Get the four strategies in one table, then the five inputs that decide whether any of them work: conversion completeness, value variance, freshness, consent-modeled data, and volume. Audit the inputs before you blame the algorithm. - [Value-based bidding needs values you can trust](/blog/value-based-bidding.md) — Cost per conversion treats a $99 signup and a $50,000 deal as the same win, and Smart Bidding believes it. Here's what value-based bidding actually changes, how to build values you can trust, and the honest checklist for when switching will make things worse instead of better. - [Tracking after third-party cookies: what actually still works](/blog/tracking-after-third-party-cookies.md) — Third-party cookies didn't die the way everyone braced for. The exposure that's actually truncating your attribution is first-party cookie lifetime, and it hits every stack, consent banner or not. A per-browser status check, the lifetime table to bookmark, and the three tracking mechanisms that still work. - [Server-side tracking: what it fixes, what it costs, and whether you need it](/blog/server-side-tracking.md) — Server-side tracking recovers the conversions ad blockers and Safari quietly delete, but it costs money and upkeep to run. Here's what it fixes, what it doesn't, and an honest table for whether your account has crossed the line where it pays off. - [First-party data: the definition and the operating model](/blog/first-party-data.md) — What first-party data actually is, versus second-, third-, and zero-party, and the three-move operating model (collect, connect, activate) shown on a real stack: first-party pixel, CRM and order feeds, identity map, warehouse. No CDP required. - [Enhanced conversions: what they fix, what they leak, how to turn them on](/blog/enhanced-conversions.md) — Recover the Google Ads conversions that cookies quietly lose, and know exactly what customer data you're sending Google in exchange. What enhanced conversions fix, what they leak, who should skip them, and the 2026 settings merge most guides predate. - [Google Ads conversion tracking: setup and the 7 ways it silently breaks](/blog/google-ads-conversion-tracking.md) — Set up Google Ads conversion tracking so the numbers stay trustworthy: the counting, value, and attribution decisions that matter more than the tag, both install paths (gtag and GTM), where to find your conversion ID and label, and the seven ways tracking silently breaks, each with a detection step. - [GA4 conversion tracking: setting up key events](/blog/ga4-conversion-tracking.md) — Events, key events, conversions, imported conversions: one table that ends the GA4 naming confusion, then the setup path that actually feeds Google Ads. Define the event, promote it to a key event, import it, and skip the double-counting trap that catches most imports. - [Meta conversion tracking end to end: pixel, CAPI, and events that dedup](/blog/meta-conversion-tracking.md) — Meta conversion tracking is one pipeline, not three products. Install the pixel, add the Conversions API on whichever of three paths fits your stack, and make sure Meta counts each sale once instead of twice. Includes the four reasons that count quietly doubles. - [Conversions API vs the Meta Pixel: what actually changes](/blog/conversions-api-vs-pixel.md) — The Meta pixel and the Conversions API carry the same conversions by different routes, so it's almost never one or the other. Here's what changes in your numbers when you run both, the shared-ID mistake that silently double-counts them, and why Meta's free 2026 setup removed the old reason to skip it. - [Conversion tracking on every ad platform: the reference table](/blog/conversion-tracking-every-platform.md) — Check one maintained table instead of ten platform docs: the click-ID parameter, client and server tracking, value support, offline import, and consent handling for every ad platform, plus a 60-second setup pointer for each, from X and TikTok to Bing, Reddit, and phone calls. - [The conversion tracking QA checklist: test it like you'd test code](/blog/conversion-tracking-qa-checklist.md) — Conversion tracking breaks silently after launch, and month-end is a bad time to find out. Here's a re-runnable checklist you run like a test suite after every site change: what to check, which tool checks it, and what a pass looks like, plus how to fire test conversions without polluting your data. - [Why Amplitude and PostHog attribution doesn't match your ad platforms](/blog/amplitude-posthog-attribution-audit.md) — Your Amplitude or PostHog attribution will never match Google Ads, and most of the gap is by design. Here's how to audit it per tool: which differences to expect, and which ones are real capture defects to fix. - [Click IDs: what gclid, fbclid, and wbraid do](/blog/click-ids-explained.md) — The ?fbclid= and ?gclid= codes in your URLs are how each platform matches an ad click to the conversion it caused. Here's what every click ID (fbclid, gclid, wbraid, msclkid, ttclid, li_fat_id) actually does, where they get lost in transit, and why stripping them quietly breaks your measurement. ## Changelog - [Upload CRM conversions to Google Ads](/changelog/2026-07-31-google-conversion-upload.md) — Send your CRM deals into Google Ads as conversions that climb in value as deals progress, so Smart Bidding learns from pipeline instead of form fills. - [TikTok Ads reporting](/changelog/2026-07-15-tiktok-ads.md) — Connect TikTok Ads and get campaign, ad, and conversion performance next to your other sources, with cost per result you can compare across channels. - [Message your marketing agent from WhatsApp](/changelog/2026-07-01-whatsapp-marketing-agent.md) — Message your marketing agent from WhatsApp and get answers back in the same thread. - [Message your marketing agent from Slack](/changelog/2026-06-30-slack-marketing-agent.md) — Connect Slack and message your marketing agent in a thread, so you get live campaign answers and charts back where your team already works. - [Reply to any Buron email to ask your agent a question](/changelog/2026-06-28-reply-by-email.md) — Reply to any Buron email with a question and the agent answers in the same thread, so a report is no longer a dead end you switch tabs to chase down. - [YouTube channel analytics in one place](/changelog/2026-06-26-youtube-analytics.md) — Connect YouTube and get views, watch time, engagement, and subscriber growth next to your other channels instead of in a tab you forget to open. - [Google Search Console reporting, next to your paid channels](/changelog/2026-06-24-google-search-console.md) — Connect Google Search Console so your organic search sits next to your paid channels, with clicks, impressions, CTR, and position by query and page. - [Build a dashboard for the metrics your team lives in](/changelog/2026-06-21-custom-dashboards.md) — Pin your reports onto one dashboard so your team opens a single page and sees ROAS, spend, and conversions side by side, live. - [Build cross-channel reports without SQL](/changelog/2026-06-18-cross-channel-reports.md) — Slice your marketing data by any metric, dimension, and filter, chart it, and pin it to a dashboard, no SQL required. - [See revenue and ROAS by channel](/changelog/2026-06-15-revenue-by-channel.md) — Tie every deal and lead in your CRM back to the campaign that earned it, then read revenue and ROAS by channel. - [Attribute Shopify orders to the campaign that earned them](/changelog/2026-06-11-shopify-attribution.md) — Connect your store and attribute every Shopify order to the channel and campaign that earned it. - [Attribute pipeline and revenue with HubSpot](/changelog/2026-06-07-hubspot-attribution.md) — Connect HubSpot to Buron for full HubSpot attribution: pipeline, revenue, and ROAS by the channel and campaign that earned each deal. - [Attribute revenue to source with the Attio integration](/changelog/2026-06-03-attio-attribution.md) — The Attio integration ties every won deal and pipeline stage back to the channel and campaign that earned it, so you see revenue and ROAS by source, not just deals in a CRM. - [See which campaign earned every customer with the Buron pixel](/changelog/2026-05-30-tracking-pixel.md) — Add one snippet and the Buron pixel captures the channel, campaign, and landing page behind every visit, so you know which marketing earns each customer. - [Start from a marketing prompt, not a blank chat](/changelog/2026-05-26-agent-skills.md) — Start any task from a library of marketing prompts built into the Agent, so you skip the blank page and hand the work to Buron. - [A marketing knowledge base your agent works from](/changelog/2026-05-21-knowledge-base.md) — Buron gives you a marketing knowledge base the Agent maintains itself, so every answer is grounded in what's true about your team right now. - [Automated Google Ads reports, emailed every Monday](/changelog/2026-05-16-automated-reports.md) — Turn on the weekly report and Buron's Agent scans your accounts and emails a narrative of what changed and what to do about it. - [Google Ads optimizations you approve](/changelog/2026-05-12-google-ads-optimizations.md) — Buron runs a daily Google Ads optimization review, surfaces findings tied to your account, and only changes what you accept. - [Automatic Google Ads audits, every morning](/changelog/2026-05-07-google-ads-audit.md) — Buron runs a full Google Ads audit against your account on a schedule, so wasted spend and misconfigurations surface before they cost you, not after. - [Set up Google Ads conversion tracking from your AI editor](/changelog/2026-05-03-google-ads-conversion-tracking.md) — Set up Google Ads conversion tracking from your AI editor, so Buron can calculate ROAS and surface findings from the conversions that actually matter. ## Optional - [Full content](/llms-full.txt) — All pages concatenated