> ## Documentation Index
> Fetch the complete documentation index at: https://soran.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Forwarded conversions

> Send goal conversions back to the ad platforms that caused them.

Ad platforms optimize against what you tell them. If they only see what their own
pixel caught, they are optimizing on a partial picture. Forwarding sends your
conversions back so their bidding has better data to work with.

This is what **Destinations** does, and it is a separate top-level section of the
app from Data sources: sources bring data in, destinations send it out.

## How a goal connects to it

The goal's **category** is the join. A destination forwards conversions by
category rather than by naming individual goals, so what gets sent is defined by
your goals rather than configured again per platform.

That means changing a goal's category changes what is forwarded. It is not just a
grouping label.

## Setting one up

Destinations are chosen from a catalog grouped by what kind of tool each platform
is — Marketing, Analytics, Email & SMS. Meta is the first supported platform.
Platforms marked **coming soon** in the picker are visible but not yet
selectable.

Each destination has its own screen for configuration, delivery logs, and match
quality once it is running.

> [!NOTE]
>
> Forwarding sends conversions you have already recorded. It does not change
> your own reports — the numbers in Soran are the same whether you forward or
> not.

## Related

> **[Destinations](/docs/integrations/destinations)**
>
> Setting up and monitoring a destination.

> **[Create a goal](/docs/goals/create-a-goal)**
>
> Where the category is set.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.