Cookie IDs can be retrieved through the SDK(refer to the data fetching guide).
The following attribution data must be sent along with the Cookie ID for proper attribution.
User IDs may be sent without Cookie IDs if data fetching is inconvenient.
In such cases, Airbridge processes events based on the Cookie IDs mapped to the provided User ID.
However, if no mapping is found, this may lower the accuracy of reports.
You can send the user’s IP in the X-Forwarded-For header. Without X-Forwarded-For, user behavior is logged with the IP of the server that requested the Server To Server API, not the user’s IP (client request IP).We accept values in the form of ipv4 (123.123.123.123), ipv6 (2001:e60:87e3:81d4:cd57:5d52:ee2e:ff8d).
Random UUID v4 string.Accepts a random string in UUID4 format.The event uuid is used for duplication as a unique ID for the event, and will be generated automatically by the event api if not provided.
The time the event occurred. (default: current timestamp)A Unix timestamp in milliseconds (13 digits in Unixtime).If the eventTimestamp is older than 24 hours from the time the event was sent, it will not be processed by the server.
Attribution campaign parameter Short ID. Provide the value fetched from the Airbridge SDK(AndroidiOS).NOTE: This value must be sent to the Airbridge server without processing or filtering.If data fetching is not an option, sending the User ID(user.externalUserID) will make this field optional.
Attribution campaign channel. Provide the value fetched from the Airbridge SDK(AndroidiOS).NOTE: This value must be sent to the Airbridge server without processing or filtering. (eg. values such as airbridge.websdk must also be sent)If data fetching is not an option, sending the User ID(user.externalUserID) will make this field optional.
Attribution campaign parameters. Accepts data in JSON format.Provide the value fetched from the Airbridge SDK(AndroidiOS).NOTE: This value must be sent to the Airbridge server without processing or filtering.If data fetching is not an option, sending the User ID(user.externalUserID) will make this field optional.
The currency for the payment event. You can use the currency used for the actual payment, as it will be converted to the currency set in your dashboard during event processing.