---
title: 'Conversions API | Plainrouter'
description: 'An interface for sending conversion events from a server to a receiving platform.'
last_updated: 2026-09-10
---

# Conversions API

A conversions API is an interface for sending conversion events, such as purchases or leads, from a server to a receiving platform. It is a transport contract, not a guarantee of attribution or delivery.

## Is Meta Conversions API the same as Plainrouter's API?

No. Meta Conversions API is a destination interface. Plainrouter's versioned Conversion API accepts first-party events and exposes its own ingestion and delivery contracts.

## Does an accepted request prove provider delivery?

No. Acceptance and provider delivery are separate states. Check delivery evidence and any provider response rather than treating ingestion success as completed delivery.

## How do browser and server copies avoid double counting?

Use a consistent event identity for the same logical event and follow the destination's deduplication contract. For Meta, consult the event_id deduplication guide.

## Related reading

- [How Meta event_id deduplication works](/library/meta-event-id-deduplication)
- [All definitions](/definitions)
- [Signals](/product/signals)
- [Actions](/product/actions)
- [Implementation guides](/library)
- [API documentation](https://plainrouter.com/docs/api/conversions)