Modified Conversion Callback Schema
Added fields to the payload scheme
Name | Type | Sample | Notes |
conversion.TrackSysEventId | string? | "TrackSysEventId": "evt_12345" | Optional ID from the external tracking system. |
conversion.TrackSysConversionId | string? | "TrackSysConversionId": "conv_67890" | Optional conversion identifier in the tracking system. |
conversion.TrackSysConversionAmount | string? | "TrackSysConversionAmount": "49.99" | Optional monetary amount associated with the conversion, as recorded by the tracking system. |
conversion.TrackSysConversionIpAddress | string? | "TrackSysConversionIpAddress": "203.0.113.42" | Optional IP address from which the conversion was recorded. |
conversion.TrackSysConversionEmail | string? | "TrackSysConversionEmail": "[email protected]" | Optional email address associated with the conversion in the tracking system. |
conversion.TrackSysConversionUserId | string? | "TrackSysConversionUserId": "user_abc" | Optional user ID in the tracking system. |
conversion.TrackSysConversionSub1 | string? | "TrackSysConversionSub1": "sub_value_1" | Optional sub-parameter 1 for tracking system segmentation. |
conversion.TrackSysConversionSub2 | string? | "TrackSysConversionSub2": "sub_value_2" | Optional sub-parameter 2 for tracking system segmentation. |
conversion.TrackSysConversionSub3 | string? | "TrackSysConversionSub3": "sub_value_3" | Optional sub-parameter 3 for tracking system segmentation. |
conversion.TrackSysConversionSub4 | string? | "TrackSysConversionSub4": "sub_value_4" | Optional sub-parameter 4 for tracking system segmentation. |
conversion.TrackSysConversionSub5 | string? | "TrackSysConversionSub5": "sub_value_5" | Optional sub-parameter 5 for tracking system segmentation. |
conversion.SequenceNumber | int? | "SequenceNumber": null | Ordering index for dependent events in multi-event offers. • Always null for single-event offers. • For multi-event offers: – null if the event is independent. – A positive integer if the event depends on a prior event. |
Remarks:
Backwards compatibility: All new fields are optional and default to null when not provided, ensuring existing integrations continue to operate without modification.
SequenceNumber semantics:
Single-event offers: SequenceNumber will always be null.
Multi-event offers:
For Independent events, SequenceNumber remains null.
Dependent events receive a numeric SequenceNumber indicating their execution order relative to other events in the offer.
