> For the complete documentation index, see [llms.txt](https://docs.talkfurther.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talkfurther.com/products/analytics/custom-analytics-tracking.md).

# Custom Analytics Tracking

Understanding exactly where your leads come from is critical for optimizing marketing ROI. Standard traffic sources (organic search, paid search, email, etc.) are useful, but often too broad. Many operators want more granular insights—such as which specific campaigns, landing pages, or domains drive the best results.

Further’s **Custom Analytics Tracking** allows you to define your own traffic sources, map them into your CRM, and get deeper visibility into what’s working. This ensures your reporting reflects the true impact of your marketing efforts.

![Custom Rules](/files/JebrAFaykXiIzqXel8mb)

***

## What It Does & How It Works

* **Define custom traffic sources** based on URLs, parameters (like `utm_medium`), or referrers.
* **Group leads into meaningful categories** that match your internal reporting needs (e.g., “Email Campaigns” instead of a generic “Email”).
* **Push the data directly into your CRM** so reporting is consistent across platforms.
* **Retroactively apply rules**—new rules will backdate and apply across historical data within 24 hours.

**Example:**\
If your ads include `utm_medium=email`, you can create a Custom Tracking Rule so that all leads with that parameter show up in Further Analytics as **Email Campaigns**. That value can then be synced into your CRM.

***

## Integrations & Configuration

* **CRM Integration:** Works seamlessly with supported CRMs (Salesforce, Yardi, Aline, Enquire, WelcomeHome, etc.). Custom sources can be mapped to CRM fields for clean attribution.
* **Websites & Landing Pages:** Supports tracking across multiple domains, subdomains, and microsites.
* **Traffic Parameters:** Flexible setup for any `utm_` parameters, referrer rules, or full URLs.

***

## How to Set It Up

1. **Prerequisites**
   * Admin access to Further Dashboard.
   * CRM integration enabled if you want sources mapped into CRM.
2. **Enable Custom Rules**
   * Navigate to **Settings → Customer Traffic Rules**.
   * Click **Add Rule**.
3. **Configure Rule**
   * Select the **condition** (URL, URL parameter, or referrer).
   * Define the **match criteria** (e.g., `utm_medium=email`).
   * Enter the **custom source name** (e.g., “Email Campaigns”).
4. **Map to CRM**
   * (Optional) Choose the corresponding CRM source value to sync seamlessly.

![CRM Mapping](/files/ZSAS1M5tm27Eb5UW9xDm)

5. **Save & Apply**
   * Your rule will be active immediately.
   * Data will **backdate across historical leads within 24 hours**.

***

## Troubleshooting Tips

* **Symptom:** *Custom source not appearing in Analytics.*\
  **Fix:** Confirm the URL/parameter/referrer condition is correctly set (case-sensitive).
* **Symptom:** *Data not showing in CRM.*\
  **Fix:** Check CRM mapping settings in your integration and confirm the CRM field exists.
* **Symptom:** *Backdating taking too long.*\
  **Fix:** Allow up to 24 hours for rules to update historical data.

***

## Frequently Asked Questions

* **Can I create multiple custom rules?**\
  Yes. You can create unlimited rules to capture different campaigns, landing pages, or referral sources.
* **Does this overwrite default source values?**\
  No. Default sources remain, but your custom rules give you additional reporting granularity.
* **Will changes apply to past data?**\
  Yes, rules backdate across historical data within 24 hours.
* **Can I track traffic across different domains?**\
  Yes. Custom rules work across multiple domains and microsites.

***

## Conclusion

Custom Analytics Tracking is a powerful way to align your marketing data with your internal reporting structure. By defining your own rules and mapping them into your CRM, you get **more accurate attribution, cleaner reports, and stronger insights into ROI**—all without relying on one-size-fits-all traffic categories.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.talkfurther.com/products/analytics/custom-analytics-tracking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.