GTM Change for purchaseRevenue Variable

Recently, you may have noticed that the revenue variable within GTM is not pulling data across to your 3rd party apps like Facebook, Google AdWords etc.. This is due to a change that was made to the datalayer within Ticketsolve. It may all sound complicated, but it’s really easy to fix. Let’s walk you through it.

You’ll be glad to know that we have done all the hard work and that’s all you will have to do is download the container template below and that’s it. Once you upload the new container, the data layer will be fixed and the purchase revenue will automatically be pushed to your apps so that you can calculate your ROI again. 

Upload the GTM Container 

We have built a new container that includes the new variable which includes the change to the datalayer. Follow the steps below in order to update your GTM container.

  1. Download the container template at the bottom of this article 
  2. Login to your Google Tag Manager account 
  3. Go the the Admin section within your container 
  4. Click on Import Container within your container options 
  5. Choose the container template file that you downloaded in step 1
  6. Choose Existing workspace 
  7. Click on Merge
  8. Select Overwrite conflicting tags, triggers and variables

Screenshot_2022-11-15_at_12.39.31.png

Once you have uploaded the new container it’s very important that you Publish the changes so that the new changes take effect. Click on the Publish button in the top right corner and go through the steps to publish. 

How to Check the Changes have taken effect

To check if these changes have taken effect:

  1. Go back into your main Workspace 
  2. Click on Variables on the left hand side of the screen
  3. Scroll down until you find the purchaseRevenue variable and click on it 
  4. This will open up the dialog box that shows the variable set up. You should see the below code in the dialog box. 
  5. You will also see that the variable is also linked to your Facebook Conversion pixel

Screenshot_2022-11-15_at_12.49.39.png

Was this article helpful?

Comments

0 comments

Please sign in to leave a comment.