Legacy: Pushing Conversions and Revenue Data from Third Party Systems into Convert Experiences

THIS ARTICLE WILL HELP YOU:

• Understand Third-Party Systems

Understand Third-Party Systems

Sometimes the conversion or sale might not occur into the browser where the experiment was presented to the visitor but in some sort of back-end system. In this situation, the default cookie-based tracking does not work and conversions have to be pushed into Convert Experiences by custom scripting. The process works in two steps:

1. after the user is presented with the experiment/variation, the pair of experiment ID-variation ID that was fired has to be stored inside the back-end together with the user profile.
2. when the conversion-sale occurs in the third party system, it has to be pushed into Convert Experiences, together with the experiment ID and variation ID previously stored in the user's profile.

To push a conversion, a GET request needs to be made with the following structure:

//[project_id].track.convertexperiments.com/track/?c=[customer_id]&p=[project_id]&e=[experiment_id]-[variation_id]&g=[goal_id]&ga=1

All the bold elements have to be replaced with actual values as follows:

• [project_id] - this is the project ID that can be found in project settings. In there the field "ID NUMBER"  glues together the account ID and project ID separated by an underscore char. For example, if ID number is 1111_2222 than 1111 represent the account id and 2222 represents the project's ID.
• [customer_id] - account ID found as described above
• [experiment_id] - experiment ID the visitor was presented. This should be stored in the user's profile as explained in step 1)
• [variation_id] - ID of the variation that was presented to the visitor, stored as explained in step 1)
• [goal_id] - the goal ID you want the conversion to be triggered for. You can fire multiple goals at once by providing instead of a single goal ID a list of comma-separated goal IDs and updating the ga parameter to have as a value the count of pushed goals. Example: &g=100,101,102&ga=3. 

To push a transaction (revenue), a GET request needs to be made as follows:

//[project_id].track.convertexperiments.com/track/?c=[customer_id]&p=[project_id]&e=[experiment_id]-[variation_id]&t=[goal_id]|[transaction_value]|[transaction_products_count]

All the bold elements have to be replaced with actual values as follows:

• [project_id] - this is the project ID that can be found in project settings. In there the field "ID NUMBER"  glues together the account ID and project ID separated by an underscore char. For example, if ID number is 1111_2222 than 1111 represent the account id and 2222 represents the project's ID.
• [customer_id] - account ID found as described above
• [experiment_id] - experiment ID the visitor was presented. This should be stored in the user's profile as explained in step 1)
• [variation_id] - ID of the variation that was presented to the visitor, stored as explained in step 1)
• [goal_id] - the goal ID you want the conversion to be triggered for. This can be found in your Convert Experiences account as explained above. Transaction data can be attached to multiple goals as well by providing a dot-separated list of goal ids instead of a single goal id.
• [transaction_id] - The ID of the transaction comes from the external system. It has to be unique for each different transaction *
• [transaction_value] - two decimal value of the transaction
• [transaction_products_count] - number of items ordered in this transaction