# Tagging your campaigns for Google Analytics

This is a guide to help with the number of **Direct** traffic in Google Analytics. This is the traffic of which Google does not know the source.

{% hint style="success" %}
If you don’t tell Google the specifics of your campaigns, then they will be rolled into existing buckets without the ability to identify them. This most commonly happens with emails and social posts that by default get classified as referrals.
{% endhint %}

{% embed url="<https://www.youtube.com/watch?v=YVxi0sQmro0>" %}

There is a set format for doing this in Google Analytics and it is called **UTM tagging**. What you will do is add a **campaign source**, **campaign medium**, and **campaign name** to the end of your URL.

![](https://downloads.intercomcdn.com/i/o/62586035/c570b8495ff0e4892f8ba7f1/Screen+Shot+2018-06-08+at+16.33.52.png)

Google makes it really easy to do this with their free tool [Campaign URL Builder](https://ga-dev-tools.appspot.com/campaign-url-builder). You do have to be very careful of spelling, as you should stick to one format. We recommend you use **email,** instead of Email or e-mail, as that will appear as different line items in reports.

![](https://downloads.intercomcdn.com/i/o/62614777/87af3be569652a4ec94c7023/url.png)

Now you can see that campaigns under the **Acquisition report > Campaigns > All.**

![](https://downloads.intercomcdn.com/i/o/62586854/e5eaaf972abf3d79321cac49/Screen+Shot+2018-06-08+at+16.41.31.png)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.littledata.io/google-analytics/acquisition/tagging-your-campaigns-for-google-analytics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.