> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/setup-and-monitor/plan-and-integrate/set-up-advanced-features.md).

# Set up advanced features

Optional capabilities to enable once the basics run: Edge, predictive data, the standard segment builder, and Cross-CDP.

## Your goal

Decide which optional capabilities your project needs, and enable them deliberately - after the environment and the data model are in place, not instead of them.

## Expected outcome

You know which of these features you want, what each one requires, and which ones need to be activated for your organisation by mediarithmics before you can configure anything.

## What is in here

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Edge</strong></td><td>Compute segments in the browser for near real-time on-site targeting.</td><td><a href="/setup-and-monitor/plan-and-integrate/set-up-advanced-features/edge.md">Edge</a></td></tr><tr><td><strong>Affinity &#x26; Intention</strong></td><td>Add computed and predictive data to your user graph.</td><td><a href="/setup-and-monitor/plan-and-integrate/set-up-advanced-features/affinity-and-intention-ml-algorithm.md">Affinity &amp; Intention</a></td></tr><tr><td><strong>Standard segment builder</strong></td><td>Give business users a guided way to build segments.</td><td><a href="/setup-and-monitor/plan-and-integrate/set-up-advanced-features/standard-segment-builder.md">Standard segment builder</a></td></tr><tr><td><strong>Cross-CDP</strong></td><td>Aggregate data from several organisations into a parent organisation.</td><td><a href="/setup-and-monitor/plan-and-integrate/set-up-advanced-features/cross-cdp.md">Cross-CDP</a></td></tr></tbody></table>

## What they have in common

| Feature                      | Requires                                                                         | Activated by                                                                |
| ---------------------------- | -------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| Edge                         | Latest tag snippet, schema properties flagged for Edge, an ad server integration | Your account manager, per channel                                           |
| Predictive and computed data | A schema that declares the computed field or score, and a plugin behind it       | You, once the plugin type is available to your organisation                 |
| Standard segment builder     | At least one builder and one audience feature configured per datamart            | You, in datamart settings                                                   |
| Cross-CDP                    | A community and organisation hierarchy that matches how you want data aggregated | Discussed with mediarithmics, because it shapes your organisation structure |

{% hint style="info" %}
Each of these features changes what your teams can do day to day, but none of them changes how data is collected. Get [Set up the environment](/setup-and-monitor/plan-and-integrate/set-up-the-environment.md) and [Design your data model & schema](/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema.md) right first - Edge and computed data both depend directly on the schema.
{% endhint %}

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Set up the environment</strong></td><td>The setup work these features build on.</td><td><a href="/setup-and-monitor/plan-and-integrate/set-up-the-environment.md">Set up the environment</a></td></tr><tr><td><strong>Design your data model &#x26; schema</strong></td><td>Where Edge flags and computed fields are declared.</td><td><a href="/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema.md">Design your data model &amp; schema</a></td></tr><tr><td><strong>Plugin architecture</strong></td><td>How custom logic is hosted and run.</td><td><a href="/setup-and-monitor/extend-the-platform/plugin-architecture.md">Plugin architecture</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mediarithmics.io/setup-and-monitor/plan-and-integrate/set-up-advanced-features.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.