Stay up to date with what's new in Buron.

Your Buron agent can now reach you on WhatsApp, and you can reply. Ask how a campaign did or follow up on a report, and it answers in the same thread, pulling your numbers and drawing a chart when it helps.

Every message Buron sends is a thread you can reply to, so the back-and-forth stays in one place instead of scattered across the dashboard.

Connect WhatsApp to get started. It's one of a few ways to reach your agent, so see the channels overview for email and Slack.

Connect Slack and you can message your Buron agent where your team already works. Reply in a thread, DM the app, or @mention it in a channel, and the agent pulls the live answer and posts it right back in the same thread, grounded in your real data.

Ask it for a chart or a table and it renders one inline by citing a real dashboard panel or report, so it points at your actual campaign data instead of drawing a picture. Charts upload straight into the thread, inside your workspace's access control rather than at a public link, so they stay private to the people who can see the conversation.

Connect Slack to get started. See how the agent works across every channel, then build the dashboards and reports it points at in Reports.

Every email Buron sends now comes from a repliable address. Hit reply, ask "why did cost-per-lead jump on Brand?" in plain language, and the agent pulls the numbers and answers right in the thread you're already reading. No new tool, no login, no copy-paste.

Reply again and it remembers what you asked, so a follow-up like "how does that compare to Search?" builds on the first answer instead of starting over. There's nothing to connect: unlike Slack or WhatsApp there's no OAuth step, and email is members-only, so only active teammates can wake the agent, matched by their address.

There's nothing to install either, it's on the moment your team has a slug. See how replies work, how it fits alongside your other messaging channels, and what the workspace agent can do when you ask.

Connect YouTube and Buron pulls your channel analytics into the same place you analyze everything else: views, watch time, engagement, and subscriber growth you can slice by video, channel, and date.

You get three slices out of the box: per-video performance (views, watch time, likes, comments, shares, subscribers gained), channel growth over time, and an audience-retention curve that shows exactly where viewers leave a video. This is reporting, not attribution: YouTube metrics sit next to your other channels, they don't feed revenue or ROAS.

Connect YouTube to get started. It reuses the same Google sign-in as Google Ads but stands on its own, so you can connect it whether or not you run ads, then slice every metric in Reports.

Connect the app and Buron pulls your Search Console performance, clicks, impressions, CTR, and average position by query and page, into the same place you analyze everything else. Your organic search sits right next to your paid channels instead of off in its own tab.

Already connected Google Ads or YouTube? You won't sign in again. Search Console reuses the same Google sign-in and lands as its own connection you can manage separately. This is reporting, not attribution: Buron won't credit pipeline or ROAS to a search query, so for revenue by channel you'll still lean on the pixel and your CRM.

Connect Search Console to get started. Once a sync has run, build a chart or table on any of the search datasets in Reports and pin it next to the rest of your marketing.

Pin the reports you check every week onto a named page and Buron gives you a custom dashboard: a grid of live tiles, each one a report running against your real data. One page with ROAS, spend, and conversions by channel, side by side.

A shared date range picker sits at the top, so change it once and every tile re-runs together. Don't have the report yet? Start an empty dashboard and build one inline from a dataset, save it, and it drops straight in as a tile. Dashboards are team-scoped, so every member sees the same board and no one sees another team's.

Build a dashboard to get started. Each tile is a saved report, so slice your data in Reports first, then pin the ones worth watching.

Pick a dataset, click the metrics and dimensions you want, and Buron builds the report on the spot: revenue and ROAS by channel, campaign, keyword, or device, charted as a line, bar, donut, or table. No query to write.

Datasets read from what you've already connected. Your Google Ads account reads live through GAQL the moment it's linked, and the warehouse datasets join your pixel and CRM data for attribution. Every report shows the exact GAQL or SQL it generated, so you can see what ran without writing it, then copy the results into Sheets or download a CSV.

Build a report to get started. Save the ones you'll ask again and pin them to a dashboard, and lean on the attribution behind the warehouse datasets so your revenue and ROAS reflect the campaigns that earned them.

Buron ties every deal and lead in your CRM back to the marketing that earned it, so you read revenue and ROAS by channel instead of guessing. Install the pixel, connect your CRM, and Buron joins the visitor journey to your closed deals.

It captures the full path to each conversion, not just the last click, and credits it under first-touch and last-touch models, so you can see where demand starts and where it closes. It reads your CRM stage dates too, so a deal counts the moment it reaches a stage like Lead or MQL, which powers cost per lead and cost per MQL alongside your ad spend.

Install the pixel and connect your CRM to get started, then slice everything in Reports.

Connect your Shopify store and Buron attributes every order to the channel, campaign, and landing page that drove it. Your revenue and ROAS by channel now include Shopify sales, not just orders by day.

Because Shopify records the customer journey on each order, Buron can backfill and attribute your existing orders on the first sync. Your reports are full from the start instead of trickling in with new sales, and store currency is detected automatically so ROAS lines up with your ad spend.

Connect your store, pair it with the Buron pixel for the full cross-site journey, and slice revenue in Reports.

Connect HubSpot over OAuth and Buron matches the contacts on your deals to tracked visitors by hashed email, turning traffic by channel into pipeline, revenue, and ROAS by channel, campaign, and landing page.

It isn't just won deals. Buron reads your lifecycle stage dates too, so it credits a deal the moment it became a lead, MQL, or SQL, not only when it closed, and gives you down-funnel rates like cost per lead and cost per MQL. Standard HubSpot source fields work out of the box, so most portals connect without touching a mapping.

Connect your CRM to get started. Pair it with the Buron pixel so every deal joins to the full visitor journey, then slice pipeline and revenue in Reports.

Connect your Attio workspace and Buron matches the people on your deals to tracked visitors, then credits the channels and campaigns that earned each one. Traffic by channel becomes pipeline and revenue by channel, campaign, and landing page.

It reads down the funnel, not just the finish line: a deal gets credited the moment it reaches a stage you map, so you can track cost per lead and cost per MQL, not only cost per won deal. Standard Attio attributes come preselected, so most workspaces just skim the mapping and sync.

Connect your CRM to get started. Pair it with the Buron pixel so deals join to the touchpoints that drove them, then slice pipeline, revenue, and ROAS in Reports.

Add the Buron pixel, one snippet in your site's head, and Buron starts capturing where every lead and customer comes from: the channel, campaign, and landing page behind every visit, tied to the person the moment they identify themselves by email.

It records the full path, every touch with its UTMs, referrer, and click IDs like gclid, not just the last click. When someone submits a form or checks out, Buron links that path to them, so first-touch and last-touch attribution both trace back to real marketing.

Install the pixel to get started, then connect your CRM so each touch ties to deals and revenue, and slice pipeline and ROAS by channel in Reports.

The Agent now opens with a library of marketing prompts built in, so you pick a starting point instead of facing a blank chat. Choose one and Buron picks up the task and runs with it.

Ask it to review your spend, do a deep dive on a topic, or run a health check, then watch the work stream in as it pulls a Google Ads report, searches the web, or saves a document back to your workspace. Some actions still get your approval before they run, like pushing a change to Google Ads, so you stay in control of anything that touches your accounts.

Meet the Agent to get started. Give it context to work from by loading up your Knowledge, and every prompt comes back grounded in how your marketing actually runs.

Buron gives you a marketing knowledge base the Agent maintains itself, holding your products, competitors, positioning, brand voice, ads work, and priorities. You curate the sources and ask the questions, the Agent does the writing, and every chat starts by reading from it.

Because everything is cross-referenced, a single update can touch 10 to 15 pages. Paste a competitor announcement and the Agent files it and propagates it across every page it affects. The structure exists from day one, so there's nothing to set up, and you keep the final say on every page.

Add sources to Knowledge to get started. See what Knowledge holds and how it grounds every answer your Agent gives.

Connect a Google Ads account, turn on the weekly report, and the Buron Agent emails you a narrative every Monday: what changed across your campaigns, what it means, and where to look next. No dashboard to open, no numbers to export.

It's the same engine behind the daily optimization review that starts the moment you connect. The Agent scans your accounts every morning and writes findings for whatever it turns up, so the weekly email is a summary of work already done, not a raw data dump. Reports are emailed and saved, so you can open any past run to see exactly what it flagged.

Turn on automated reports to get started, and see what the daily review catches between emails in Optimize your Google Ads.

Every morning the Buron Agent runs a Google Ads optimization review across your enabled accounts and writes findings to your queue. It catches budget concentrated in sub-scale campaigns, ad group underperformance, keyword cannibalization, weak Responsive Search Ad and Performance Max assets, and conversion rate drops. Each finding names the exact campaigns or ad groups it affects, the action it recommends, and the metrics that flagged it, and nothing changes until you accept it.

Findings are tagged by category, bids, keywords, budget, creative, structure, and tracking, so you can filter to what matters this week. Accept one and Buron queues the change, refine it and the Agent revises its suggestion, reject it and it won't come back. Anything that runs gets logged in Automations with its status, so you always have the audit trail.

Optimize your campaigns to get started. Every accepted change is tracked in Automations, and you can always ask the Agent in chat to investigate something it didn't flag.

Point Buron at your Google Ads account and it runs a full audit for you: more than 30 health checks that each report pass, warn, or fail, rolled up into a single account health score you can read at a glance. Set it on a schedule and the audit runs on its own, so problems surface before they cost you.

The checks cover what actually moves performance: conversions flowing, spend fragmentation, campaigns not spending, Responsive Search Ad and Performance Max asset strength, keyword cannibalization, negative keyword coverage, disapproved ads, and landing page reachability. Every check that warns or fails links straight to a finding, so you can accept, refine, or reject the Agent's recommended fix instead of just reading a red flag.

Audit your account to get started, then let the findings turn into action in Optimize your campaigns.

Run /setup-google-ads-tracking from your AI editor with your product repo open, and Buron sets up your Google Ads conversion tracking end to end. It walks you through picking your primary conversion, secondary events, and a value model, then your editor's agent writes the tracking code for any gaps it finds. It audits what already fires, checks that gclid and UTMs survive the journey to the conversion, and compares your codebase against what's configured in your Google Ads account.

Once you confirm it works in GA4 DebugView and your conversions report, the skill saves the spec back to Buron as the source of truth. The Agent reads it when surfacing findings, and your reports use it to calculate ROAS, so the conversions you tracked line up with the campaigns you're spending on. It can even write regression tests that run on every PR, so tracking drift gets caught before it costs you.

Set up conversion tracking to get started. To capture the full journey behind those conversions, pair it with the Buron pixel.

Connect your Google Ads account and Buron imports your campaign data so the Agent can work with it directly, reviewing reports, surfacing findings, and proposing the changes you'd otherwise dig for by hand.

Running multiple brands or clients? Connect a Manager Account (MCC) and enable every account under it in one pass, or pick a subset of standalone accounts. Buron refreshes your access automatically as long as the connection stays healthy.

Connect Google Ads to get started. Then set up conversion tracking so the Agent works against real outcomes, and see everything the Agent can do once your account is live.

Connect Buron's MCP server to your editor and its agent gets direct access to your Google Ads data, knowledge files, dashboards, and launch workflow, all from the conversation you're already in. Ask it to run a GAQL query, pull up a named dashboard for a date range, or search your team's knowledge, and it answers inline.

It works with any editor that speaks the Model Context Protocol: Claude Code, Cursor, GitHub Copilot, and others. You connect once and sign in through the browser, and because every request is stateless, you can close and reopen your editor without losing anything.

Connect the MCP server to get started, or follow Connect to Claude Code for a step-by-step first query.

Install the Buron CLI, link a project, and Buron drops slash commands into your AI editor, giving its agent a direct line to your team's marketing docs without leaving the conversation. It auto-detects the editor, Claude Code, Cursor, or Codex, and installs the skills where it reads from.

You set this up once. From there, /launch snapshots a code change, its diff, PR thread, and screenshots into Buron so the next person who asks has the full story, and /setup-google-ads-tracking walks the agent through wiring up conversion tracking. Run buron skills update to pull in new commands as they land.

Install the CLI to get started, see what your agent can do in Use Buron in your AI editor, and read up on the Agent it's talking to.

Buron is an agentic marketing platform built around a chat. Describe what you want, and the Agent picks up the task and runs with it, showing the work as it streams in.

Ask it to review last week's spend, draft a launch plan, or run a health check, and it pulls a Google Ads report or searches the web as the task calls for it. Anything that changes data outside Buron waits on your approval first, and you can read the Agent's reasoning before you say yes, so pushing an update to your ad accounts stays your decision.

Start a conversation with the Agent, bring Buron into your terminal with the CLI, or wire it into your own tools over MCP.