1. Purpose
The Conversion API lets an advertiser's server report a confirmed purchase, lead submission, or app install so Posto can attribute performance to a prior Posto click, deduplicate retries, measure campaign outcomes, and optimize future delivery. No browser pixel is required.
2. Required data
Each event uses a server API key and includes event type, a unique stable event ID, Posto click ID, and event time. Purchases also include value in USD cents. Reuse the same event ID when retrying or correcting the same real-world outcome. Never include names, email, phone, street address, payment-card data, account passwords, health data, or unrelated customer records.
3. Attribution
Posto click ID links the event to an authenticated click and its campaign, ad, app, and placement. Event ID prevents duplicate counting when the advertiser retries. An unknown but well-formed click ID may be recorded as unmatched; a missing click ID is rejected as an integration error. Attribution is limited to the documented window.
4. Security
Server API keys are confidential backend credentials and must never be shipped to a browser or mobile binary. Use TLS, secret management, least privilege, stable idempotency, and key rotation. Posto records authentication and request metadata needed to investigate abuse.
5. Roles and rights
The advertiser is responsible for the legal basis, notices, accuracy, and user-rights handling for conversion data it submits. Posto processes the event to provide attribution and acts independently for security, billing integrity, and legal compliance. The Data Processing Addendum applies where Posto acts as processor.
6. Corrections, deletion, and retention
Advertisers must correct or reverse events when an outcome is cancelled or invalid. Posto keeps immutable financial and fraud-audit records where required, while limiting personal data and pseudonymizing closed accounts. Contact privacy@postoconnect.com for privacy requests or correction assistance.