Contents:
Use the export feature to download an offline copy of your report data. Report data will be exported to a. Recurring charges, including monthly or usage-based charges, are billed every 30 days.
Hi there! The app stopped working for me and I have not heard back form support. Would love some help. App was great before it pooped out. Thank you! Learn more on shopify.
Email address. Your store name. Create your store. Search Search.
Discount Coupon Analytics by Jumpstart. Add app. About Discount Coupon Analytics. Discount Code Analytics Track the performance of your discount codes no matter which Shopify plan you are on! Features Overview Quick and easy installation No coding required. Top Performers See which discount codes are most popular by order spend. Forecast and plan your sales Know what discount code works and what doesn't.
Filter and View Reports Use the calendar to select a specific date range or use our pre-built filter options to filter and view reports. Export Reports by Discount Codes Use the export feature to download an offline copy of your report data.
Upon installation, Discount sends its bots to collate your orders and sort it automatically. Show full description.
The average amount of time in seconds to download this page. If the user arrived without a referrer, the value is direct ga: Measuring a Product Click Next, a user expresses interest in this particular product by clicking on the product listing to view more details. A productFieldObject must have a name or id value. The number of screenviews per session reported as a string. To measure this product details view, use ec:
Show less. Media gallery. AdWords is now Google Ads.
Our new name reflects the full range of advertising options we offer across Search, Display, YouTube, and more. Learn more.
I would also Like to see the unique code used within the promo - do we track that as a custom variables? Order level coupon means the total of product revenue wll be different to order total - is there a way around it? Go to Best Answer. Hi again - with regard to your 1 question, I'd suggest that this is something you discuss with your developer and how much flexibility they have in sending variables to your ecommerce hit.
Sending the promo name, or a combination of promo name and coupon code, should be something which your developer can help you with - this could then be . While coupon promotions are immensely popular, achieving take to design more effective coupon-based promotions using data analytics. Choose a scenario that will provide the best ROI: Next, you'll want to narrow down.
At the end of the day, it's your ability to analyse the data which is most important. Sending the promo name, or a combination of promo name and coupon code, should be something which your developer can help you with - this could then be send as a 'coupon' hit. I'm not sure of the consequences to the data of omitting it in the product field, as long as its included in the purchase push then the entire transaction will be labelled with the coupon. The coupon slot in the product field is optional so omitting it should not cause any issues.
If you've the luxury, I'd recommend testing this before you go live. View solution in original post. I would suggest that you are correct in that custom dimensions not custom variables, these were replaced by custom dimensions are the solution here. Ask your developers to capture the value of the coupon and then send it to GA.
The most straightforward way to do this is if you are using Google Tag Manager - you can then send the value to the datalayer and then use it in GA as you wish. If you are not using Google Tag Manager then here is the developer notes for sending a custom dimension with a page or event hit: Developer notes for sending variables to the datalayer a datalayer 'push': Simo has some excellent tips about this here: Addressing your questions specifically: You could, for example, send both the promo code and the coupon code as separate variables.
You and your developer can decide how little, or how much, you wish to send. Depends on how you are already tracking ecommerce in Google Analytics. Again, you can ask your developer to manipulate the values to reflect the correct value. At the very least, if you implement custom dimensions for these coupons, you can label them in Google Analytics. Couple of other points: Consider the scope of the custom dimension. They can bet set at hit, session or user level.
The most important point is that session and user scope custom dimensions are overwritten by the latest value - this is worth considering if your visitors can use more than one coupon. Custom dimensions do not, by default, have a 'null' value. It can improve your data collection, and ability to create reports, that when you set the custom dimension you send a 'noCoupon' value or similar if no coupon is used.
So in the code below, can we remove the 'coupon': And only keep it in the purchase actionFieldObject, but rather than capture the actual code, we will capture the name of the promo "Summer " instead? And tracking of the use of the actual voucher eg, AX we will capture as a custom dimension. And in terms of scope, in the rare occasion where the user might place two transactions with us in the same session using two sepatate voucher codes, is it best practice to set this at hit level? Because the use of of voucher is associated with a transaction, which is also a hit level dimension itself?
That way you can capture those users who use multiple coupons as well as those users who have, at some point, used a coupon; there's other approaches but that would be how I'd address this. I'll get back to you later with regard to the ecommerce code. Thanks again for all your comments, have you had any chance to look at the ecommerce code yet? What are your thoughts? Sorry for the delayed answer, I've been on holiday. Good to hear things are moving forwards; testing is definitely the right thing to prioritise - good luck!
If you agree, your survey will open in a new window.