Each conversion event sent to the API should map to a single conversion action in Campaign Manager, using consistent event names and parameters so LinkedIn can attribute it correctly and report on it alongside other campaign metrics.
- One conversion action per meaningful event type — for example, separate actions for "Trial Started" and "Purchase"
- Required fields include the conversion action ID, event timestamp, and at least one match key
- Optional value and currency fields let you report on estimated revenue per conversion
- Campaign Manager shows recent events received for a conversion action, which is useful for confirming the mapping is correct
Use cases
Introductory guidance for teams
- Map ecommerce events to LinkedIn Conversions API
- Align CRM events with LinkedIn Conversions API
- Validate event types prior to LinkedIn Conversions API ingestion
- Version control of event schemas for LinkedIn Conversions API
- Coordinate with ad platforms using LinkedIn Conversions API
- Test event payloads in a sandbox with LinkedIn Conversions API
- Document field level purposes for LinkedIn Conversions API
End note on data integrity