Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Setup Checklist

Insert excerpt
AE:Set-up ChecklistAE:
Set-up Checklist
nopaneltrue

1. POS

GOOGLE ANALYTICS TASKS

POS Task 1

  1. Set Up Google Analytics

    Status
    colourRed
    titleRequired

Expand
titleExample of POS Task
Products that need age ranges assigned are created in POS and have age ranges added to POS
    1. Create a new GA4 Property.

  1. Set Up Google Tag Manager

    Status
    colour

YellowInfrastructure Task 2 -
  1. Red
    title

Prerequisite

2. INFRASTRUCTURE TASKS

  1. required

    1. Create a new GTM Container if needed.

  2. Import Triggers/Tags

    Status
    colourRed
    title

Required Expand
titleExample of Infrastructure Task
​Confirm that the Azure function app is setup and configured to the desired frequency. - Commerce Task 3 -
  1. required

    1. Import the GA Setup Container using the .json file linked below.

  2. Edit Variables

    Status
    colourRed
    title

Required

Status
colourYellow
titlePrerequisite

3. COMMERCE TASKS

  1. required

    1. Add your GA4 Measurement ID.

    2. Preview and Publish your Container.

    3. Verify that tags are reporting in Dashboard.

Status
colour

Red

Green
title

Required
Expand
titleExample of Commerce Task

Confirm that the Aspenware Commerce products that will have inventory assigned to them are fully configured with the correct attributes -

Status
colourRed
titleRequired

Status
colourYellow
titlePrerequisite

Language String, Setting, HTML widget, etc. Task 4 -

Status
colourBlue
titleoptional

Expand
titleExample of Setting Task

​Ensure the setting ‘ecommercesettings.productinventory.cachetime’ is set to your desired cache time -

Status
colourBlue
titleoptional

Status
colourYellow
titlePrerequisite

Configuration Task 5 -

Status
colourRed
titleRequired

Expand
titleExample of Configuration Task

Inventory is mapped to product or product variant in the Inventory Pool plugin

Status
colourRed
titleRequired

Code is entered

Status
colourRed
titleRequired

If using location in RTP, location code is entered

Status
colourRed
titleRequired

If multi day product, number of days is defined

Status
colourRed
titleRequired

If using non default lock time of 900 seconds, the desired lock time is configured.

Status
colourBlue
titleoptional

Status
colourGreen
titleDetailed Setup

Prerequisite Tasks

...

POS Tasks

  • POS Task that must be completed first

Infrastructure Tasks

  • Infrastructure Task that must be completed first. Remove section if not required

Commerce Tasks

  • AW Commerce task that must be completed first

Settings, Language Strings and/or HTML Widgets for this Feature

...

Settings

  • AW Commerce Settings that must first be completed

Language Strings

  • AW Commerce Language Strings that must first be completed

HTML Widgets

  • AW Commerce HTML Widgets that must first be completed

Detailed Setup Guide

  1. Step 1 Header

  2. Step 2 Header

1. Step 1 Header

  • First bullet should provide navigation instructions i.e. Catalog >Attributes >Product attributes

    1. Sub-bullet for step 1. Every step and click should be detailed so that someone could follow with little prior experience.

      1. Sub-bullet for step a. Include screenshots of the step and use skitch to mark up screenshots. It can be downloaded here: https://www.techspot.com/downloads/5705-skitch.html

Expand
titleExample of content within a section
  • From the Aspenware Commerce Plugins>Age Range page in Admin, click View Add Range Types in the upper right corner.

  • Click Add Age Range Type.

  • Enter a name and description for the age range type.

  • To set the date used to compare the customer’s age to the required age range, select:

    1. Calculate from Trip Start (this age range type is likely already configured), or 

    2. Calculate from Today’s Date (age range based on purchase date), or

    3. Specify the Calculation Start Date; the customer’s age on this date will be used to determine if they are eligible for the product based on the age ranges

  • Click Add.

  • Age Range Types can be edited and inactivated, but they cannot be hard deleted without contacting Aspenware. 

  • Age Range types that are set to Calculate from Trip Start or Today’s Date will never need to be edited, unless you would like to edit the name. Age Range Types that are calculated from a fixed date however, will need to be edited each year to adjust for the current year.

Image Removed

 

Hint: Age Range Types should also be adjusted year over year. If age ranges are calculated based on Trip Start, then they will not need to be updated.

Once completed for all required age range types move on to create Age Range.

Info

Note: When possible use notes, warnings, and hints within info panel macros. See https://aspenware.atlassian.net/wiki/pages/resumedraft.action?draftId=781156460 for more details on these.

2. Step 2 Header

  • First bullet should provide navigation instructions i.e. Catalog >Attributes >Product attributes

    1. Sub-bullet for step 1

      1. Sub-bullet for step a

DELETE CONTENT AFTER THIS LINE

go to the Glossary page and add the key terms Excerpt Include that you added for your configuration guide.

To add the feature terms to the Glossary, navigate to the glossary and add a header for your feature using an H2. Select the + and then select …view more. Search for Excerpt Include and in the Page Containing the Excerpt search for “Configuration: [FEATURE]” select to hide panel, preview and add.

How-to Guide of this page can be found here: [Internal] Configuration page Setup Guide

...

detailed status

Detailed Setup Guide

Info

NOTE: Aspenware Commerce has added the ability to load Adobe Analytics credentials for resort customers who use both reporting platforms. Including these credentials will enable Adobe Analytics to connect and pull data from the same tags that GA4 will leverage. In essence, users of both platforms will have access to two reporting interfaces.

1. Set Up Google Analytics

2. Set Up Google Tag Manager

Note

IMPORTANT: Aspenware recommends individual tags rather than using the “Send Ecommerce data” checkbox.

We don’t recommend using the "Send Ecommerce data" option for a couple of reasons:

  1. Limited Customization – The checkbox sends only the standard eCommerce data, which doesn’t meet the needs of our complex ski resort business. Custom event parameters or additional data points may be left out. Our data layer has several of those, and more are coming.

  2. Potential Data Inconsistencies—If the data layer contains inconsistencies or follows a non-standard format, enabling this checkbox might result in missing or incomplete ecommerce events. Our data layer has some known inconsistencies, most of which will be resolved in the next release.   

Setting up the tags manually will enable you to obtain all the standard and custom events and dimensions, and it will allow for better accuracy, flexibility, and customization in the long run.

3. Hardcode Currency in Google Tag Manager

Google Analytics 4 requires a defined currency to report revenue accurately. Currency can be defined in multiple places, but hardcoding the currency in the GTM container is the best way to ensure that your revenue is reported correctly.

Note

IMPORTANT: This task must be completed by an admin or user with publish permissions in Google Tag Manager, and should take less than 2 minutes to complete. Be sure to complete this for every container (every site) you monitor, in both test and production.

The requirement references how currency is defined and reported in your site, and requires a 3-digit code to be entered. The most common codes for Aspenware resorts are:

  • US Dollar: USD

  • Canadian Dollar: CAD

  • Australian Dollar: AUD

  • New Zealand Dollar: NZD

Please make a note of the currency for your site(s), and follow the instruction below to configure:

  • Log in to the Google Tag Manager Account

  • In the sidebar, select Tags

    Image Added
  • Locate the Purchase Event in the tag list, and select.

  • Identify the variable you are using for the currency parameter and make a note of it (e.g. {{GA4-Ecommerce Currency}} in the example below).

  • Image Added

    Close the tag and select Variables in the sidebar. Select the ecommerce variable you identified in the previous step.

    Image Added
  • Change the Variable Type from Data Layer Variable to Constant.

    Image Added
  • Enter your currency code in the Value field. Currency code entries are 3 characters:

    • USD (US Dollar)

    • CAD (Canadian Dollar)

    • AUD (Australian Dollar)

    • NZD (New Zealand Dollar)

  • If your Variable is already defined as Constant, simply update the Value from 000 to the correct currency code.

    Image Added
  • Save your changes and click Submit in the upper right.

  • Publish the container. We suggest including “Hardcode Currency…” or some other identifier in the version name field.

    Image Added

4. Import Triggers/Tags

Info

NOTE: For details about what is available in the Aspenware data layer, please see Google Analytics Reference Guide.

  • Import the GA4 Setup Container, which contains tags, triggers and variables. See Container export and import.

  • In the article (above), scroll down to and follow the “Import” instructions using the Aspenware GA4 Import Tags File.json below.

Note

IMPORTANT: Considerations for Importing the Aspenware Tags and Triggers File

  • If you are configuring your GTM account for the first time, select the most current version of our tags and triggers file to import.

  • If you already imported a previous tags and triggers file, and have not added any customization, import the most current version of our Tags and Triggers json file.

  • If you have customized your tags and triggers file, importing our latest json file will overwrite your customization. Instead, use the most current file to compare your existing json to our new file, and add any new events/tags manually, using the same process you did when you customized the file.

  • The GA4 Configuration & Page View tag may vary depending on setup. Use preview mode in GTM to test the integration and make sure you are collecting the correct page view data.

  • The GA4 Configuration & Page View tag may not be needed if you already have the tag in your GTM container. Multiple GA4 Configuration & Page View tags could cause duplicate page views and events.

 

File Date

JSON File

2/4/25

Coming Soon!

Edit Variables

  • After the import is complete, go to Variables (left nav).

...

  • Select GA4 Measurement ID from the list.

...

  • Edit Value. Replace with your GA4 Measurement ID.

...

...

Info

NOTE: For support on creating reports, funnels, and understanding the data reported in Google Analytics, Aspenware recommends Jay Pompar (jay@vickeryhill.com) at vickeryhill.com, who was instrumental in implementing GA4 in Aspenware Commmerce, and has deep knowledge and expertise in leveraging analytics. (eCommerce tracking, goal conversions | VickeryHill )

...