PlaysbyMoat8
Back to the library
The workflow guideMarketing

Request a visual marketing update in team chat

A demonstration connected a messaging assistant to an analytics agent, then turned requested metrics into charts delivered back to the conversation.

6 implementation stepsIntermediate

How this works

A demonstration connected a messaging assistant to an analytics agent, then turned requested metrics into charts delivered back to the conversation. A chat request should produce an inspectable answer, not just an attractive image. The metric definition, date window, freshness, and underlying values must travel with the visualization.

Resolve the question into a small query specification, calculate from available authorized data, and render only after validation. Use a CSV or spreadsheet export when a connector is unavailable. Keep chart creation local unless the user has authorized sending the result to the requested conversation.

Before you start

Metric dictionary

Define conversions, revenue, spend, attribution, currency, and the meaning of each requested breakdown.

Authorized data path

Use an existing read-only connector or supplied export; never claim access that is not available.

Rendering option

Use a standard chart tool and retain a table fallback if image generation or delivery fails.

Prepare the inputs

question
Required

Chat text

Extract the requested metric, grouping, comparison, and intended audience.

period
Required

Start/end and timezone

Define inclusive boundaries and mark partial days or weeks.

metric_definitions
Required

Dictionary

Specify numerators, denominators, filters, and attribution window.

data
Required

Rows or connector result

Check freshness, missing values, duplicate keys, and currency.

optional_delivery_target
Optional / conditional

Thread identifier

Use only an explicitly authorized destination and retain delivery state.

Implementation, step by step

  1. Translate the request

    • Write the exact metric, period, grouping, and comparison as a query plan.
    • Resolve material ambiguity such as bookings versus recognized revenue before calculation.

    Checkpoint: The requested answer has a single inspectable definition.

  2. Retrieve a bounded dataset

    • Read only the columns and period needed through the available connector or export.
    • Record extraction time and preserve the unmodified returned dataset.

    Checkpoint: Data access and freshness are known rather than assumed.

  3. Validate and compute

    • Check totals against source summaries and identify incomplete conversions or periods.
    • Calculate rates deterministically from summed numerators and denominators, not averages of row percentages.

    Checkpoint: Reported values reconcile to the retained data.

  4. Choose a useful chart

    • Use bars for category comparisons or lines for time series with consistent intervals.
    • Label units, period, timezone, filters, and any suppressed or missing values.

    Checkpoint: The visual encoding answers the question without hiding uncertainty.

  5. Write a compact interpretation

    • State the main observed difference and its numerical basis.
    • Avoid causal explanations not supported by the data; include a short caveat for conversion delay.

    Checkpoint: The caption adds context without inventing a diagnosis.

  6. Deliver with traceability

    • Provide the chart, accessible data table, and definition note.
    • Send to chat only when authorized, and record an actual receipt or clearly state that files are prepared.

    Checkpoint: The user can inspect both the visual and its source values.

Decisions along the way

The current period is incomplete

Compare equal elapsed periods or label the comparison as provisional.

A requested breakdown lacks reliable mapping

Report an unknown bucket and its size rather than silently dropping rows.

The query returns no rows

Distinguish a valid empty result from an access failure and avoid drawing a zero-valued chart without evidence.

What you will produce

Visual update

PNG or SVG plus text

A compact, labeled performance answer.

Include: chart · caption · period · definitions · freshness

Evidence table

CSV

The deterministic calculations and missing-data state behind the visual.

Include: group · numerator · denominator · value · status

Check the result

  • Rates use compatible cohorts and denominators.
  • Currency and timezone match the request.
  • Unknown values remain distinct from zeros.
  • The caption does not imply that a chart was delivered when only a file exists.

When something goes wrong

Analytics access fails

Use a supplied export or return the exact data requirement without fabricated numbers.

Chart labels are clipped

Adjust layout and inspect a rendered preview before delivery.

Source totals disagree

Show the discrepancy and defer the affected conclusion until filters are reconciled.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Show last week's cost per qualified lead by campaign in a chat-ready chart.

Inputs

Synthetic example. Campaign A spent 600 currency units and had 20 reviewed qualified leads; campaign B spent 450 and had 10. Both cohorts are complete in the same timezone.

Expected result

Synthetic expected result. The bar chart shows 30 and 45 currency units per qualified lead, with the period and reviewed-lead definition. A table preserves spend and counts. The caption reports the difference without claiming one campaign caused higher quality; delivery remains prepared until authorized.

Run a small pilot

Start small

One recurring question covering two campaigns and a complete week.

Record the baseline

Measure analyst time to a reconciled answer using the current process.

Agree success criteria

Track calculation accuracy, time to chart, and successful authorized delivery.

Stop or revise

Stop interpretation when definitions or source totals cannot be reconciled.

Keep the scope clear

  • Do not treat chart-rendering success as validation of the underlying data.
  • A chat message requesting an answer does not grant unrelated account access or broadcast permission.

Check before using

The demonstration used sample data. Check definitions, conversion delays, and missing values; the example did not establish a production reporting system.

Business activities

  • Run advertising and acquisition tests
  • Review business performance

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Marketing metrics and business definitions · Requested period and breakdown

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗