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

# Conversion delivery

> Control which business events are sent to connected ad platforms.

Conversion delivery starts with a rule. The rule listens for a source event, creates a Datalyr conversion, enriches it with available first-party context, and sends the mapped event to one destination.

## Create a safe rule

1. Connect the destination under **Sources** and select the intended account asset.
2. Produce a real test source event and inspect it in **Events**.
3. Open **Conversions → Manage rules** and create a rule.
4. Choose the source, exact event name, destination platform, account asset, and platform event.
5. Map value from a numeric event field or use a static value; set the correct currency.
6. Add only destination parameters you can populate reliably.
7. Enable the rule and send one controlled test.

Google, Meta, TikTok, Snapchat, OpenAI, and mobile attribution destinations can expose different assets and fields. The rule editor only shows options supported by the selected destination and active connection.

## Verify both stages

Open the source row in **Events**, then the resulting row in **Conversions**. Finally, use the destination's test events or diagnostics to confirm acceptance. A successful Datalyr conversion does not guarantee the destination accepted or reported it.

## Prevent duplicates

* Do not run a second server-side sender for the same event unless deduplication is configured and tested.
* Use stable transaction or event IDs where the integration supports them.
* Check for two enabled rules with the same source, event, and destination.
* Do not retry by creating a new business event with a new ID.

<Warning>
  Changing an enabled rule changes future delivery. It does not rewrite historical conversions in Datalyr or the destination.
</Warning>