> For the complete documentation index, see [llms.txt](https://community.commandersact.com/mixcommander/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.commandersact.com/mixcommander/api/mixcommander-v1-api/untitled.md). # GET Conversion Details ## GET Conversion Details Returns the list of conversion details **Resource URL:**\ GET /**{version}**/measure/conversiondetails/?**site**=XXXX&**token**=YYYY&**date\_start**=YYYY-MM-DD&**date\_end**=YYYY-MM-DD&**format**=ZZZZ **Parameters:** | URI PARAMETER | TYPE | MANDATORY | DESCRIPTION | | ----------------------- | -------- | --------- | ----------------------------------------------------------------------------------------------------------------- | | version | Alphanum | Yes | Call API version | | URL PARAMETER | TYPE | MANDATORY | DESCRIPTION | | site | Integer | Yes | Client site identifier | | token | Alphanum | Yes | Caller security identifier | | date\_start | Date | Yes | Data recovery start date (YYYY-MM-DD format) | | date\_end | Date | Yes | Data recovery end date (YYYY-MM-DD format) | | attrib | Alphanum | No | Attribution models identifier (0 to look through all CJ) | | segment | Alphanum | No | Identifier of the segment that will be used to recover data | | attrib\_operator | String | No | Selection operator for the channel and the source (in, notin) | | channel | Integer | No | Conversion containing this channel id | | source | String | No | Conversion containing this source | | order\_ids | Alphanum | No | Order identifiers’ list, separated by commas | | amount | Numeric | No | Conversion amount | | amount\_operator | String | No | Operator (eq, neq, lt, lte, gt, gte) for the conversion amount selection (Mandatory if amount is a parameter) | | touchpoint | Integer | No | Number of touchpoints | | touchpoint\_operator | String | No | Operator (eq, neq, lt, lte, gt, gte) for the touchpoint amount selection (Mandatory if touchpoint is a parameter) | | fraud | String | No | Required score for fraud detection (any, good, average, bad) | | format | String | No | Response format (XML or JSON) – JSON by default | | page | Integer | No | Requested page – By default 0 | | count | Integer | No | Number of elements per page, cannot exceed 100; 100 by default | | include\_cj | Integer | No | Include or not customer journeys (0 for no, 1 for yes) – 0 by default | | duplicated\_conversions | Integer | No | Include or not duplicated conversions (0 for no, 1 for yes) – 0 by default | | excluded\_conversions | Integer | No | Include or not excluded conversions (0 for no, 1 for yes) – 0 by default | **Return codes:** | HTTP CODE | MESSAGE | DESCRIPTION | | --------- | --------------------- | ------------------------------------------------------------------- | | 200 | OK | The request went through, the result is in the answer’s body | | 400 | Bad Request | The parameters are not ok or mandatory parameters are missing | | 401 | Unauthorized | The security token does not match the site\_id or the container\_id | | 500 | Internal Server Error | Internal server erros | **Response Format**\ The response is in a JSON or XML format. ## Difference between API and conversion details **API** List of fixed dimension in the API * Fixed dimensions * Traffic Dimensions on demand ( Jira ticket) * Conversions Dimensions populated in the conversion hit ( Conversions tags or Server Side tags) List of fixed dimension in the Api : * tc\_id * id\_order * date * amount\_order * score * channel\_winner * source\_winner * click\_number * view\_number * touch\_point * time\_convert * user\_agent * ip **Export Conversion Details** List of fixed dimension in the Export * Fixed dimensions * Traffic Dimensions on demand ( ticket) * "raw" dimensions (= option keep format checked ) * Conversion dimensions List of fixed dimension in the Export: * Identifier ID * Order ID * Date * Amount * Fraud score * Winner Channel (one touch) * Winner Source (one touch) * Click * Impression * Touch points * Time to convert * Browser * IP 3 remarks: 1. API send the dimensions only when the information is available in the hit 2. Export send all the dimensions, when it’s empty it send null as a value in the export 3. Some names of the properties are not the same for the exports and the API ( tc\_id / Identifier ID ; view\_number / Impression ; etc...) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://community.commandersact.com/mixcommander/api/mixcommander-v1-api/untitled.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.