Tagging REST API: TrackBrowseCheckout
Overview
Endpoint to register "Checkout" actions during navigation, ie. for products accessed through category views.
Service Name
browseCheckout
Service URL
URL_TAGGING/INSTANCE_ID/browseCheckout?INPUT_PARAMETERS
Input parameters
Please refer to the Browse Product input parameters
Revenue information can be provided with the following optional parameters.
| Parameter | Description | Data Type | Mandatory | Defaults |
|---|---|---|---|---|
| revenue | Numeric value of the product revenue/price | Number | no | – |
| currency | Currency code for the revenue amount. Must be a valid ISO 4217 currency code. | String | no | – |
| transactionId | Arbitrary identifier to link all checkout events that correspond to a unique transaction - typically a UUID, the important thing is for it to be unique and consistent for transactions. | String | no |
Output
This method returns nothing or the wrapper used as jsonCallback.
Related articles
-
EmpathyBroker Tagging REST API (Empathy Knowledge Base)
-
Tagging REST API: TrackQuery (Empathy Knowledge Base)
-
Tagging REST API: TrackClick (Empathy Knowledge Base)
-
Tagging REST API: TrackConversion [DEPRECATED] (Empathy Knowledge Base)
-
Tagging REST API: TrackAdd2cart (Empathy Knowledge Base)
-
Tagging REST API: TrackWishlist (Empathy Knowledge Base)
-
Tagging REST API: TrackAPICall (Empathy Knowledge Base)
-
Tagging REST API: TrackBrowseCategory (Empathy Knowledge Base)
-
Tagging REST API: TrackBrowseProduct (Empathy Knowledge Base)
-
Tagging REST API: TrackBrowseAdd2Cart (Empathy Knowledge Base)
-
Tagging REST API: TrackCheckout (Empathy Knowledge Base)
-
Tagging REST API: TrackBrowseCheckout (Empathy Knowledge Base)