# Track channel attribution (/use-cases/gtm-growth/channel-attribution)



Copy this prompt to start your first task:

<Prompt>
  Set up a channel attribution automation for me. First, audit our UTMs and links for naming chaos, duplicate channels, and tracking gaps, and propose a clean convention. Then report daily on new traffic, conversions, and channel anomalies that need my attention.
</Prompt>

<LivePreview component="NewThread" scenario="{ draft: &#x22;Set up a channel attribution automation for me. First, audit our UTMs and links for naming chaos, duplicate channels, and tracking gaps, and propose a clean convention. Then report daily on new traffic, conversions, and channel anomalies that need my attention.&#x22; }" />

## What is this workflow? [#what-is-this-workflow]

"Track channel attribution" is the recurring job of turning "which marketing channel is actually working" from a quarterly guessing exercise into a daily habit. A teammate pulls visitor and signup data tagged by UTM source and reports conversion channel-by-channel instead of one blended number, flagging any channel that spikes or drops to zero. Layered on top, a weekly automation compares each channel's performance against what it costs and calls out the standout worth more budget and the laggard worth reviewing, with reasoning for each.

## How to use this workflow [#how-to-use-this-workflow]

<Steps>
  <Step>
    ### Hire a growth-focused teammate [#hire-a-growth-focused-teammate]

    Open **AI Teammates** in the sidebar, click **Hire AI Teammate**, and pick the **Growth Hacker** template, or your existing sales/growth teammate. The default bio is generic campaign planning. Replace it on the Profile step so it knows this job is daily channel-attribution reporting, not campaign strategy:

    <Prompt>
      You're a channel-attribution AI, skilled at turning scattered links, UTMs, sources, and conversions into an explainable growth report. Set up a "channel attribution daily quality check" automation for me for these channels: [channel list, landing pages, current UTMs/links, conversion goal, data source]. On day one, run an attribution baseline: find naming chaos, missing tags, duplicate channels, unexplainable data, and tracking gaps; output a unified naming convention, a channel performance table, anomalies, and fix suggestions. After that, roll up new traffic, leads, conversions, anomalous channels, and attribution issues that need my attention every day — only report changes that affect judgment or spend decisions. Prefer public links and whatever data I provide; proactively offer to connect official tools like Bitly when a direct connection is available; and guide me through the browser when a login is required.
    </Prompt>

    Confirm the name and click **Create teammate**. They land in their own channel, which is where you'll send everything below. [More on hiring →](/ai-teammates/hire-an-ai-teammate)

    <LivePreview component="CreateAssistantPage" scenario="{ focus: &#x22;profile&#x22;, initialState: { start: &#x22;template&#x22;, templateRef: &#x22;@helio/growth-strategist&#x22;, name: &#x22;Growth Hacker&#x22;, bio: &#x22;You're our channel attribution teammate. Pull visitor and signup data tagged by UTM source and report conversion by channel separately, never one blended number. Flag any channel spiking or dropping to zero. Weekly, compare channel performance against what each one costs and call out the standout worth more budget and the laggard worth reviewing, with your reasoning for each.&#x22; } }" />
  </Step>

  <Step>
    ### Connect your analytics [#connect-your-analytics]

    Add your team's analytics tool as a skill so the teammate can pull real visit and signup data by UTM source. [Skills & Plugins →](/connect/skills-and-plugins)

    <LivePreview component="AssistantSkills" />
  </Step>

  <Step>
    ### Turn it into a daily automation [#turn-it-into-a-daily-automation]

    Open **Automations** in the sidebar, click **Create via Chat**, and pick this teammate in the New Thread composer that opens:

    <Prompt>
      Every day at 9am, pull visitor and signup data tagged by UTM source. Report conversion by channel separately, not one blended number, and flag any channel spiking or dropping to zero.
    </Prompt>

    <LivePreview
      component="AssistantChat"
      scenario="{ assistantName: &#x22;Growth Hacker&#x22;, messages: [
    { author: &#x22;user&#x22;, text: &#x22;Every day at 9am, pull visitor and signup data tagged by UTM source. Report conversion by channel separately, not one blended number, and flag any channel spiking or dropping to zero.&#x22; },
    { author: &#x22;assistant&#x22;, text: &#x22;I'll pull UTM-tagged visitor and signup data every day at 9am, break conversion out by channel instead of blending it, and flag anything spiking or dropping to zero.&#x22; },
  ] }"
    />
  </Step>

  <Step>
    ### Ask for the budget call weekly [#ask-for-the-budget-call-weekly]

    A daily conversion number is useful. A weekly recommendation on where to shift spend is more useful. Layer a second automation on top:

    <Prompt>
      Every Monday, compare channel performance to what each one costs (from the spend figures you provide). Identify the standout worth increasing investment in and the laggard worth reviewing, with your reasoning for each.
    </Prompt>

    <LivePreview component="AutomationView" scenario="{ manualCreateOpen: true, manualCreateDraft: { instructions: &#x22;Every Monday, compare channel performance to what each one costs (from the spend figures you provide). Identify the standout worth increasing investment in and the laggard worth reviewing, with your reasoning for each.&#x22; } }" />
  </Step>
</Steps>

**Nothing here needs your approval:** this teammate reads analytics data and posts reports — it never touches infrastructure or sends anything externally, so this flow runs on its own. See [Control](/ai-teammates/control) for what does pause for sign-off.

## Tips for Better Results [#tips-for-better-results]

| Tip                                               | Description                                                                                                                        |
| ------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| Keep channels separate, never blended             | A single conversion number hides which channel is actually working. Have the teammate report each channel on its own.              |
| Connect your real analytics tool first            | The teammate needs a skill wired up to your actual analytics platform before it can pull real UTM-tagged visitor and signup data.  |
| Give it spend figures for the budget call         | The weekly cost comparison only works if you provide what each channel actually costs — the teammate doesn't have that on its own. |
| Layer the weekly budget check on the daily report | The daily conversion number tells you what's happening; the weekly comparison against spend tells you what to do about it.         |

## Common Questions [#common-questions]

<Accordions type="single">
  <Accordion title="What data does this pull?">
    Visitor and signup data tagged by UTM source, pulled from whichever analytics tool you connect as a skill.
  </Accordion>

  <Accordion title="Does it report one blended conversion number?">
    No. It reports conversion channel-by-channel, never blended into a single figure, and flags any channel spiking or dropping to zero.
  </Accordion>

  <Accordion title="Does it tell me where to shift budget?">
    Weekly, yes — it compares each channel's performance to what it costs and calls out the standout worth more investment and the laggard worth reviewing, with its reasoning.
  </Accordion>

  <Accordion title="Do I need to give it spend data?">
    Yes. The weekly cost comparison runs on the spend figures you provide — the teammate doesn't have access to that on its own.
  </Accordion>

  <Accordion title="Does this need my approval to run daily?">
    No. Reading analytics data and posting a report doesn't touch anything irreversible, so this flow runs on its own.
  </Accordion>
</Accordions>

<Cards>
  <Card title="GTM & Growth" href="/use-cases/gtm-growth" description="Back to the GTM & Growth use case overview." />

  <Card title="Outreach and follow-up tracking" href="/use-cases/gtm-growth/outreach-and-follow-up" description="Batch-draft personalized outreach and track replies." />
</Cards>