Versions Compared

Version Old Version 9 New Version Current
Changes made by

Sarah Holst

Sarah Holst

Saved on

Key

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

Setup Checklist

...

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

...

  • Log in to the Google Tag Manager Account

  • In the sidebar, select Tags

  • 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).

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

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

  • 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.

  • 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.

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: Which file should I import?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.

See NEW DOCUMENTATION FOR Events and

 

File Date

JSON File

2/4/25

ADD FILE FOR 3.7Coming Soon!

Edit Variables

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

...