Modify payload to Vipps to precisely track transactions in GA4 and ad networks

  • I’m working as a consultant in a performance marketing agency and together with the client we are working on a solution to more precisely track where transactions done with Vipps are coming from. To illustrate the issue, let’s picture a scenario where a user is navigating through the Facebook feed on an iPhone. While browsing, the user sees an ad and decides to click it. The user is then redirected to the advertisers’s website that opens in an in-app browser within the Facebook application, thereby launching a session in Google Analytics 4. The user then decides to buy something with Vipps. As the user clicks “Pay with Vipps”, the Vipps application opens up on the iPhone. The user then completes the transaction and is sent to the websites thank you page which is opened in the Safari browser, thereby launching a new session.?

    In this case the transaction/conversion will be attributed to direct traffic in GA4 as the connection to the original session is lost when the user moves from the in-app browser to Vipps.?Ideally, the conversion should have been attributed to the ad the user clicked on Facebook.

    In order to attribute the transaction / conversion to the correct session and source, we need to include some GA4 parameters that identifies the user in the GET request payload from api.vipps. These are session_id (used to identify the session in GA4), client_id (used to identify the user in GA4) and a timestamp indicating when the event happened. These parameters must then be processed in Vipps until the payment is completed and then sent to GA4 in a Post request through GA4s API connection named Measurement Protocol. 

    We have successfully implemented this solution for another service offered by the client where payments can be done with Vipps. However, this service does not use the Vipps WooCommerce plugin. 

    The flexibility in terms of modifying the payload that goes to Vipps is according to the developers limited with the the WooCommerce plugin. 

    Any response / potential solution would be much appreciated.?

    /Hans

Viewing 1 replies (of 1 total)
  • Plugin Author Marcus

    (@marcuz2k2k)

    Hey!

    I must say I’m not entirely sure how you could solve this with the Vipps Recurring plugin alone, but a good tip is to save the GA4 values as metadata on the order that is created by WooCommerce on the checkout page.

    That way you can run some server side GA4 code when the woocommerce_payment_complete?hook is fired, or on the thank you page via the woocommerce_thankyou?hook.

    If you believe you can solve it via setting a field on the agreement itself then you should be able to add the externalId field from Vipps via the filter defined here: vipps-recurring-woocommerce/includes/wc-vipps-recurring-api.php at master · vippsas/vipps-recurring-woocommerce (github.com)

    If you think something is missing, or we could accommodate your use case by adding another filter or action then please let me know ??

Viewing 1 replies (of 1 total)
  • The topic ‘Modify payload to Vipps to precisely track transactions in GA4 and ad networks’ is closed to new replies.