# Getting Started

{% hint style="info" %}
**IMPORTANT:** This part is the crucial part of our product. If you do this part incorrectly, we will not be able to provide you with our core product features and reports. Of course, we will help you along the way with detailed instructions + live customer support to ensure we have completed this task correctly. Furthermore, it will be important for you to continue doing this the same way when creating new campaigns in all the supported channels.
{% endhint %}

## The basics

There are many different ways you can implement changes. Every marketer usually has their beloved UTM parameters structure for their channels. You don’t need to worry about this part. During the tutorial, we will explain how to maintain most of your channel's current UTM structure so that other tools like Google Analytics reporting are not disturbed.

If you do not know what UTM parameters are, please read [here](https://en.wikipedia.org/wiki/UTM_parameters) or watch this [video](https://www.youtube.com/watch?v=pNRgUq5sDhc). Google has developed a nice handy [page](https://ga-dev-tools.web.app/campaign-url-builder/) to generate yours without making mistakes. You can find this page [here](https://ga-dev-tools.web.app/campaign-url-builder/). This is just information that is handy to know. For Molecule Data to work properly, you must copy and paste the provided code in the necessary field. This information and how to implement it will follow in the next pages.


---

# 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://docs.moleculedata.com/tracking-ad-channels/getting-started.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.